Our company now uses a new FreeAgent account so our website needs to be an
“approved” third-party application to speak to it.
As we now have new web developers, none of us yet know how the previous
developers set up the invoice API (for creating and sending invoices).
I notice in the “old” FreeAgent account that our website has been
“approved” as the third-party application to speak to it. Now, the website
needs to be approved on the new FreeAgent account.
Much appreciated if somebody could tell me what details/codes needs to be
changed in order to achieve this so I can inform the new developers.
You’ll need to obtain a new access token for your website from the new
account. If your website has an “authorise with FreeAgent” process, you’ll
need to run through it and sign into your new FreeAgent account during the
process.
However, it’s possible that your previous developers did this manually, in
which case you’ll need to obtain a new access token by manually running
through the process outlined in the developer docs https://dev.freeagent.com/docs/oauth. If your new developers are familiar
with OAuth 2, this should be fairly straightforward for them.
Our company now uses a new FreeAgent account so our website needs to be an
“approved” third-party application to speak to it.
As we now have new web developers, none of us yet know how the previous
developers set up the invoice API (for creating and sending invoices).
I notice in the “old” FreeAgent account that our website has been
“approved” as the third-party application to speak to it. Now, the website
needs to be approved on the new FreeAgent account.
Much appreciated if somebody could tell me what details/codes needs to be
changed in order to achieve this so I can inform the new developers.
I will pass this on to our devs and see if they can get somewhere with it.
If not, I’ll come back here and relay any issues there may be.
Regards,
Russell.On Tuesday, August 26, 2014 2:16:54 PM UTC+1, Jonathan Barrett wrote:
Hi Russell,
You’ll need to obtain a new access token for your website from the new
account. If your website has an “authorise with FreeAgent” process, you’ll
need to run through it and sign into your new FreeAgent account during the
process.
However, it’s possible that your previous developers did this manually, in
which case you’ll need to obtain a new access token by manually running
through the process outlined in the developer docs https://dev.freeagent.com/docs/oauth. If your new developers are
familiar with OAuth 2, this should be fairly straightforward for them.
Our company now uses a new FreeAgent account so our website needs to be
an “approved” third-party application to speak to it.
As we now have new web developers, none of us yet know how the previous
developers set up the invoice API (for creating and sending invoices).
I notice in the “old” FreeAgent account that our website has been
“approved” as the third-party application to speak to it. Now, the website
needs to be approved on the new FreeAgent account.
Much appreciated if somebody could tell me what details/codes needs to be
changed in order to achieve this so I can inform the new developers.