API overview

The Safety Radar REST API lets you read and write your organization’s data from your own systems: create events from another reporting tool, sync locations, assets and users from your HR or asset systems, pull action items into a work-management tool, or feed metrics into a BI dashboard.

Base URL

All requests go to:

https://safe-api.safetyradar.com/v2

For example, listing events is GET https://safe-api.safetyradar.com/v2/events. Always use HTTPS.

Request and response format

• Request and response bodies are JSON. Send Content-Type: application/json with every request that has a body.
• Timestamps are ISO 8601 strings in UTC, for example 2026-06-04T18:49:00.000Z.
• IDs are UUIDs. Many resources also accept an externalId, your own identifier for the record, which you can use to match records between Safety Radar and your system.
• Every response includes an X-Request-Id header. Include it when you contact support about a specific request.

Organization scope

An API key belongs to one Safety Radar organization. Every request made with it reads and writes that organization’s data only. If you work with several organizations, create a key in each one.

Versioning

The current version is v2, and it is part of the base URL. We add fields and endpoints to v2 without changing the version, so write your integration to ignore fields it does not recognize. Changes that would break existing integrations will come with a new version.

Next steps

AuthenticationCreate an API key and send it with your requests.

Pagination and pollingPage through lists and fetch only what changed since your last sync.

Errors and limitsError responses, status codes and the rate limit.

API referenceEvery endpoint, with parameters, request bodies and responses.