Certn API Documentation | Developer Reference
Welcome to CertnCentric API
This document is intended to help you get started, and provides an overview of the concepts you'll need to understand in order to interact with the API as well as code examples and best practices.
Sandbox Environment
You are viewing examples for https://api.sandbox.certn.co
Safe for testing - no real data or charges.
Data Domiciling
To comply with regional data domiciling laws, Certn's platform is globally distributed, with isolated servers ("instances") in multiple regions around the world, each with its own data store. Each instance has its own API, which allows you to interact with data stored in that region.
Generally, you should choose the instance closest to your location. All information collected from applicants will be stored in the region in which the Case is ordered. Most customers will only need to interact with a single region, but if you have a global presence, you may need to interact with multiple regions. API configurations (API keys, webhooks etc) are per-region and are not replicated globally.
| Region | Name | Base Production URL | Base Sandbox URL |
|---|---|---|---|
| CA | North America | https://api.ca.certn.co |
https://api.sandbox.certn.co |
| UK | Europe, Middle East and Africa | https://api.uk.certn.co |
https://api-uk.sandbox.certn.co |
| AU | Asia Pacific | https://api.au.certn.co |
https://api-au.sandbox.certn.co |
API Rate Limiting
To ensure fair usage and maintain service quality, the Certn API enforces rate limits on all endpoints.
- Per Minute: 60 requests
- Per Day: 7,220 requests
- Exceeded: HTTP 429 Too Many Requests
Best Practices
- Batch operations: Combine multiple operations into single requests where possible.
- Use pagination: Fetch large datasets in pages rather than all at once.
- Implement caching: Cache responses locally to reduce redundant API calls.
- Use webhooks: Subscribe to event notifications instead of polling for updates.
Getting StartedQuickstart
Last updated: June 2026