Earlier this year, Sage introduced new controls for their own Sage 200 API registration, credential management and developer identification.
To be very clear, this information relates to the native Sage 200 API provided by Sage and should NOT be confused with the PKF Smith Cooper Sage 200 API products, MRGE and WIRE.
As the next step, Sage are now introducing the Sage 200 UKI API Developer Programme, a new registration and subscription requirement for organisations and individuals developing applications and integrations using the Sage 200 API.
This new scheme is applicable to anyone who uses, develops against, or maintains applications that use the native Sage 200 API. Read on to find out more.
What’s Changing
Sage are updating the commercial terms of their Developer Services Licence Agreement (DLA) to introduce paid subscription tiers for access to and use of the Sage 200 API.
The new terms took effect from 1 September 2026 for new applicants, and from 1 November 2026 if you’re an existing API user. If you are a user of the Sage 200 API, you should have already received correspondence direct from Sage UK going back to August this year.
The programme introduces:
- Application registration and credential management requirements
- Developer identification and governance controls
- Programme-specific access and subscription tiers
- Ongoing API credential management requirements
You can review the Sage 200 API Developer Programme Tiers & Pricing, including programme requirements, available tiers and associated charges. This is an agreement you or your developer will make directly with Sage UK and will not be billed via PKF Smith Cooper Systems.
If you’re using Sage’s Developer Services and they do not hear from you before 1 November 2026, your API licence will be temporarily suspended.
Who This Applies To
The programme applies to organisations and individuals who:
- Develop commercial applications that integrate with Sage 200
- Build solutions used by one or more Sage customers
- Create bespoke customer integrations
- Maintain applications that use Sage 200 API credentials
- Develop software distributed, implemented or supported by a third party
Where a third-party developer, partner, reseller, ISV or software company develops an application, that organisation must enrol in the Sage 200 UKI API Developer Programme and manage its API credentials directly.
Customers should no longer obtain API credentials on behalf of third-party developers.
Customer-Developed Applications
Sage recognise that some customers build and maintain their own internal applications and integrations using the Sage 200 API. Sage are currently finalising their approach for these scenarios and will provide further guidance before any requirements take effect. Until then, customers developing applications solely for their own internal business use don’t need to take any action.
Existing API Users
If you’ve previously registered for Sage 200 API access, your existing registration remains valid during the transition period.
To continue using Sage 200 API credentials for third-party applications after 1 November 2026, you’ll need to:
- Review the available programme tiers
- Complete the order form, selecting the appropriate subscription
- Complete any activities outlined in the Sage 200 API Migration Guide
Essential Links
- Developer Services Licence Agreement
- Acceptable Use Policy
- Sage 200 UKI API Programme Tiers & Pricing
- Sage 200 Migration Guide
- Sage Developer Services Order Form
If you require any further assistance, please reach out to sagesales@pkfscs.co.uk and we’ll be happy to help.
Written by: Chris Smith, Managing Director at PKF Smith Cooper Systems
Last updated: October 2026
