Sage 200 Authentication and Sage Access Token Generation
Once you have your Sage 200 developers subscription keys the next step is to generate a Sage Access token.
With every API request you must supply a valid Access Token within the Authorization Header.
Authorization: bearer ‹‹Access Token››
There are typically two different types of applications:
Public Client
Mobile and Desktop applications are classed as a public client types as they would need to store the client and secret locally and securely, which are then used as part of the Sage user authentication process. This is potentially less secure as the client and secret would need to be distributed with the compiled applications. To improve security a temporary certificate is issued by Sage to secure any communication between the application and Sage.
Confidential Client
Web based applications that store the Client and Secret keys on a server are classed as Confidential Clients. They are more secure because only the server has access to the keys; they are not distributed to end users.
Realnet Integrations Sage 200 integrations are Web based microservices apps that use the Confidential Client approach which are more secure and only the application has access to them.
How can you generate a Sage Access Token?
To generate a token, your application requires a Client ID and Client Secret.
To obtain these, please contact the Sage Developer Services team by emailing developers.programme@sage.com.
What should I write on my email to Sage Developer Services team to request a Client ID and Client Secret?
You simply need to send an email to: developers.programme@sage.com
Subject: Request for application a Client ID and Client secret
Message:
To whom it may concern
I hope you are well.
My name is {your_name} and I am an API developer for a Sage200 client.
We are developing an web based application to connect to Sage200.
Client Details:
Sage company name: {company name}
Sage company number: {company number}
Subscription:
I have signed up to the Sage200 Unlimited Subscription and saved the developer primary and secondary keys.
Getting Started:
I have read the Getting Started guide and the next stage refers to Sage ID Access Token Generation and it mentions this:
“
To generate a token, your application requires a Client ID and Client Secret.
To obtain these, please contact the Sage Developer Services team by emailing developers.programme@sage.com.
https://developer.columbus.sage.com/docs#/uk/sage200extra/accounts/gs-authentication
Thank you for your assistance regarding this matter.
Kind regards
{your_name}
Once you have sent the email to the Sage Developers Programme Team you should get an automated email reply saying “Sage Developer Services Support – Auto Response” saying:
Thanks for your query. We endeavour to respond to you within the following timeframe.
After a few hours the Sage Developers Programme Team should reply
Hi {your_name},
Thank you for the query.
If you require credentials then you need to submit a new credentials request, using this form.
Hope that helps.
Kind Regards