This communication was sent 1st September 2026. Sage 200 We're contacting you because you're registered to use, develop against, or maintain applications that use the Sage 200 API. Earlier this year, we introduced new controls for Sage 200 API registration, credential management and developer identification. As the next step, we're 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. What's changing We're updating the commercial terms of your Developer Services Licence Agreement (DLA) to introduce paid subscription tiers for access to and use of the Sage 200 API. The new terms take effect from 1 September 2026 for new applicants, and from 1 October 2026 if you're an existing API user. This email is your formal notice of these changes under your DLA with Sage Global Services Limited. This agreement allows us to update the DLA and Acceptable Use Policy by giving you at least 30 days’ notice. You'll find a copy of this notice on our Developer Services pages. 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
Review the Sage 200 API Developer Programme Tiers & Pricing, including programme requirements, available tiers and associated charges. If you're using Developer Services and we don't hear from you before 1 October 2026, you will lose access. 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 shouldn't obtain API credentials on behalf of third-party developers. Customer-developed applications We recognise that some customers build and maintain their own internal applications and integrations using the Sage 200 API. We're finalising our 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 October 2026, you'll need to: What you need to do If you haven't chosen and subscribed to a tier by 1 October 2026, we'll deactivate the Sage 200 API credentials linked to your registration and your access to Developer Services will end, as set out in your DLA. If you no longer use the Sage 200 API, you don't need to do anything. The credentials linked to your registration will be deactivated on that date. The number of currently active credentials associated with your registration will determine the applicable programme tier. If you no longer need some credentials, you can request their removal. Fintech and financial services solutions The Sage 200 UKI API Developer Programme supports general application development and integration scenarios. If your solution provides financial services capabilities, including payments, banking, lending, open banking, embedded finance or similar fintech services, separate commercial requirements may apply. These solutions fall outside the scope of the Sage 200 UKI API Developer Programme and are subject to separate fintech onboarding and commercial requirements. If we've identified your API-connected solution as a fintech solution, our team will contact you directly. If you're unsure whether your solution falls into this category, contact [email protected]. Essential links Kind regards, Sage Customer Support |