Closed Hesslon closed 8 years ago
This is interesting.. I'll have to look into this. I know there are implementations that are using the url that doesn't seem to work for you.
Both the REST and XMLRPC docs make mention of this, eg. https://developer.infusionsoft.com/docs/xml-rpc/
All requests except authentication requests made to the Infusionsoft XML-RPC API will be an HTTP POST to https://api.infusionsoft.com/crm/xmlrpc/v1?access_token=123abc, and all requests made after authenticating with OAuth 2.0 must have an access token appended as the access_token query parameter in order to authenticate the request.
That being said, with this patch I kept getting 302 redirects to log in when trying to access the API, and with the original code it works fine.
I'm going to close this and refer to the OAuth 2 issue
Hi Nate,
i couldn't get your implementation to work with InfusionSoft and found out that the url to their API seemed to be wrong. Could you check that and then maybe merge that back?
Thanks for your work, Ben.