We’re trying to migrate to Infusionsoft REST API from old code which uses direct http requests. Here is what we currently have
• Desktop application product for end-users. When users activates the application it sends an HTTP request to our .NET API with contact information.
• .Net API gets contact information from HTTP request, then builds an System.Net.WebRequest to https://abge.infusionsoft.com/AddForms/processFormSecure.jsp with contact information in querystring.
• .Net admin website which sends the same HTTP request to Infusionsoft as .NET API, but allows our managers to submit contact info to Infusionsoft manually (instead of desktop application)
We would like to start using your latest API(s) but not sure which product to choose and which API methods to call instead of current code. So we have the following questions:
Which product will you recommend to use so we could replace current requests with new API(s)?
Seems like XML-RPC and REST APIs redirect user to login page to authenticate. We cannot have end-user to sign-in because our desktop app sends an HTTTP request to .net API behind the scenes. Is there any other way to get an AccessToken in the .NET API to be able to use it in API calls?
How to link our business Infusionsoft account with our developer’s Infusionsoft account, so he could use provided client_id/secret_key or he should create his own sandbox account and use it in development and then just replace client_id/secret_key with production values on the server while deployment?