Sage 200
We’re sharing important information about the Sage 200 UKI API Developer Programme to help you support customers who use applications connected to the Sage 200 API, particularly if an application stops working.
What you need to know
- Organisations that develop or maintain commercial or bespoke Sage 200 API applications must join the programme and manage their own API credentials
- Developers must register each application separately and use unique credentials
- Organisations that only resell, implement or support Sage 200 don’t need to join
- Customers who develop and maintain applications solely for their own internal use don’t need to act yet. We’ll provide guidance before any requirements apply
- Microsoft 365 App Proxy onboarding remains a separate requirement
We’ve contacted registered API developers about the programme requirements, fees and updated Developer Services Licence Agreement (DLA). We’ve also contacted customers to ask them to check that their developer has taken the required action.
What's changing
The updated DLA introduces paid subscription tiers for Sage 200 API access. The new terms took effect on:
- 1 September 2026 for new applicants
- 1 October 2026 for existing API users
Developers must choose the appropriate subscription tier, provide the required organisation and developer information, and manage separate credentials for each application they develop or maintain.
If a developer doesn’t join
Developers must join by the deadline we’ve given them. If they don’t, we’ll suspend their API credentials and applications using those credentials will stop working.
If they join within 30 days of suspension, we’ll reactivate their credentials. After 30 days, we’ll delete the credentials. They’ll then need new credentials and must update their application before it can reconnect.
Further guidance is available in the Sage Knowledgebase.
How to support customers
If your organisation didn’t develop or maintain the application, direct the customer to the application developer, who’s responsible for joining the programme and managing their credentials.
You should continue to support customers with Sage 200 or Microsoft 365 App Proxy setup where appropriate Microsoft 365 App Proxy onboarding hasn’t changed. The customer’s Sage 200 Business Partner must complete the required M365 Order form for Sage 200 API connection and support the customer with setup.
The customer and application developer are responsible for any remaining actions needed to enable and maintain the integration.
Fintech and financial services solutions
Payments, banking, lending, open banking, embedded finance and other financial services solutions sit outside the Sage 200 UKI API Developer Programme and may require separate fintech onboarding and commercial terms.
We’re contacting developers whose solutions we identify as fintech. Developers who aren’t sure whether this applies should contact fintech@sage.com.
For more information, review the Partner and Developer FAQ.
