Overview
PreStartGo provides a versioned REST API (/api/v1) for integrating your compliance data with the systems around it — an ERP, a CMMS, a safety management platform, or your own reporting. This article is the orientation; the endpoint-by-endpoint detail lives in the interactive API reference.
Before you start
- Plan
- Any paid plan, with the Developer platform add-on
- Role
- Account Owner or Administrator to create API keys
What the developer platform includes
The Developer platform add-on covers three surfaces together:
| Surface | Direction | Best for |
|---|---|---|
| REST API | Pull | Reading and writing records on your schedule — syncs, reports, tools |
| Webhooks | Push | Reacting to events as they happen |
| MCP server | Query | Letting an AI assistant answer questions over your fleet |
Choosing between them is its own short read: Webhooks, the API, or MCP?
The API is deliberately not bundled into any plan — organisations that don't integrate never fund it. See Plans Overview.
The shape of the API
- Versioned in the path — everything lives under
/api/v1. Breaking changes only ever arrive in a new version; existing/api/v1integrations keep working. - JSON in, JSON out, with consistent error envelopes and machine-readable error codes — catalogued, with meanings, at /developers/errors.
- Cursor-paginated lists — follow the cursor rather than page numbers.
- Tenant-scoped absolutely — a key sees exactly one organisation's data. Cross-organisation requests 404; they don't 403, because even confirming a record exists would leak.
Authentication, in one line
Every request carries an API key as a bearer token:
Authorization: Bearer psg_live_...
Keys, scopes, environments and rotation get their own article: Authentication and API Keys.
Rate limits
Requests are rate-limited per organisation; exceeding the limit returns 429 with a Retry-After header — honour it and back off. The current per-tier quotas are published, and kept automatically current, at /developers/rate-limits.
Where to go deeper
- /developers — quickstart, authentication, pagination, idempotency, errors, versioning: the guides.
- /developers/reference — the interactive OpenAPI reference: every endpoint, schema, and a try-it console.
- Errors and Rate Limits — the operational view: what to do when calls fail.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Every call returns 401 | Missing, revoked or expired key, or the wrong environment | See Authentication and API Keys |
| Calls return 403 | The key lacks the scope for that resource | Create a key with the needed scopes |
| A record you can see in the console 404s over the API | Key belongs to a different organisation | Generate the key while operating as the right organisation |
| 429 responses | Rate limit | Honour Retry-After — see Errors and Rate Limits |
| API access refused entirely | The add-on isn't active | See Plans Overview |