This communication was sent 1st September 2026. Sage 200 Hello, We recently contacted your organisation about important changes to how we register and manage Sage 200 API access. Our records show that the email address we used for our previous communication is no longer valid, so we’re trying alternative details. We’re contacting you because you hold a valid Sage account and currently use, or have requested access to, the Sage 200 API. We’re sharing important information about changes to how we register and manage Sage 200 API access. Your use of the Sage 200 API is governed by the Developer Services Licence Agreement and the Acceptable Use Policy. These requirements apply to all API access and form part of the controls we’re introducing manage API registrations. What’s changing We’ll introduce updated processes and guidance for Sage 200 API access, including: - You must have a valid Sage account to request and maintain API access
- We’ll register all API requests under a master registration
- You must register each developer app separately and use unique credentials.
- Two credentials per app are available:
- Development (Test) credentials will support up to 20 authentication requests per minute
- Production credentials will support up to 600 authentication requests per minute
- Where you’re the developer of an App, regardless if this is for one or many customers you should request API credentials, not the customer.
- We’ll provide new documentation to support these changes
- In future you’ll submit credential requests through an App Registry on developer.sage.com. We’ll send a further communication to let you know.
What this means for you Because you hold a valid Sage account, we’ll send a separate email with your API master registration details shortly (known as a serial number). The account and registration link are mandatory and what determine continued access. You’ll need these details to speak to Sage about the Sage 200 API. We’re asking you to review your current app and credential set up to confirm it meets these requirements. If any of your credential requests don’t align with these requirements or the Acceptable Use Policy, get in touch with our teams by 15 September so we can review them with you. Help and support If you have any questions, you can: Kind regards, Sage Customer Support |