Open viperfx opened 7 years ago
I'm not at a computer right now, and I don't have links for ya, but I may be able to set you on the right path: this library interfaces with Infusionsoft's XML-RPC API, which is becoming their legacy API. I believe you can create keys for it in the admin section of your app. It will be one single hex token, maybe 32 chars.
Infusionsoft is pursuing a REST API, using OAuth for authentication. It uses a client ID and a secret key. At time of writing, a lot of functionality exists in the XML-RPC API which is not yet available through the REST API. However, the REST API does support webhooks, so you can get notified on certain events, such as contact creation or update. (Though, in my experience, it batches updates and only shoots them out every few minutes.)
Cheers!
On Fri, Sep 22, 2017, 17:17 Tharshan Muthulingam notifications@github.com wrote:
Hi,
I am a bit confused as to where the API KEY is obtained from for a particular infusionsoft portal such as fd1212.infusionsoft.com
I created an app at https://keys.developer.infusionsoft.com/apps/ and that has a App name and a client id and secret associated with it.
When I tried the fd1212 and the client ID of the app I created in the developer portal, I got the message
xmlrpc.client.Fault: <Fault 2: '[InvalidKey]Invalid Key'>
So I am not sure if I am missing something here?
Any help would be appreciated.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/theY4Kman/infusionsoft-client/issues/10, or mute the thread https://github.com/notifications/unsubscribe-auth/AACEMCxK9rbzJjKkW7C2ObfyapkKdzMWks5slCPagaJpZM4PhQBA .
The infusionsoft XML RPC uses OAuth2 as well, according to the docs
https://developer.infusionsoft.com/docs/xml-rpc/#authentication
Oh, I guess I'm not up on the times! Well, to be candid, I won't be working with Infusionsoft professionally for much longer, so I doubt I'll start writing the code for OAuth.
I'd be happy to review and accept pull requests ;) Or if you're a bribing man, I might be swayed if you hand draw yourself riding on a unicorn and post a picture of it.
Cordially, Yakko
On Sat, Sep 23, 2017, 15:18 Tharshan Muthulingam notifications@github.com wrote:
The infusionsoft XML RPC uses OAuth2 as well, according to the docs
https://developer.infusionsoft.com/docs/xml-rpc/#authentication
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/theY4Kman/infusionsoft-client/issues/10#issuecomment-331664147, or mute the thread https://github.com/notifications/unsubscribe-auth/AACEMCErVN-A0tUC4TDUOtumufIBoA2oks5slVmAgaJpZM4PhQBA .
That's fair enough, I am doing the OAuth token process in my app already. I just wanted to point out that the XML RPC requires an access token as far as I know.
To
https://api.infusionsoft.com/crm/xmlrpc/v1?access_token=123abc
I think if this can be provided then the rest of your library would work.
Hi,
I am a bit confused as to where the API KEY is obtained from for a particular infusionsoft portal such as fd1212.infusionsoft.com
I created an app at https://keys.developer.infusionsoft.com/apps/ and that has a App name and a client id and secret associated with it.
When I tried the
fd1212
and the client ID of the app I created in the developer portal, I got the messagexmlrpc.client.Fault: <Fault 2: '[InvalidKey]Invalid Key'>
So I am not sure if I am missing something here?
Any help would be appreciated.