NG-SOS Connector
NG-SOS Connector describes the API implemented by an external system selected by an Agency, typically a computer-aided dispatch (CAD) system. NG-SOS acts as the client and sends incident changes to the configured external system endpoint. This is the opposite direction from the NG-SOS API, which is hosted by NG-SOS and called by partner systems.
Each Agency chooses the external system that receives its incident data and a supported connector version. The selected external system should implement the highest available NG-SOS Connector version. NG-SOS also supports PEMEA for Agencies already connected through that standard.
The Connector OpenAPI documents are implementation contracts, not APIs hosted by NG-SOS. Implement the documented endpoints in the external system; there is no Try it workflow against NG-SOS.
| Connector | Transport | Versions | Machine-readable contract |
|---|---|---|---|
| NG-SOS Connector | HTTPS + JSON | v1 and v2 | v1 contract, v2 contract |
| PEMEA | Standardized emergency-services network | PEMEA standard | Official PEMEA documentation |
For NG-SOS Connector, the external system exposes an HTTPS base URL and validates the NG-SOS bearer access token. The Agency configures that endpoint in NG-SOS. NG-SOS appends the selected version route and sends JSON requests containing requestId and requestTimeStampUtc. The connector returns 200, 201, or 204; response bodies are ignored.
The connector must validate the token signature, issuer, lifetime, and token type. The aud claim must exactly equal urn:ng-sos:psap:{your-psap-id}, where the PSAP ID is the lowercase UUID assigned during onboarding. Both sub and client_id must equal PsapConnector, and the token must contain the psap.* scope required by the called endpoint.
Current connector tokens contain psap.incident.create, psap.incident.update, psap.incident.video, and psap.incident.close. Reject requests with an unexpected audience, client identity, or scope. NG-SOS sends connector requests only to HTTPS endpoints with a valid server certificate.
Both connector versions expose shared GET /about and GET /health endpoints. The about response returns the implemented connector version and a capability flag for every operation in that version. Its allowsMonitoring value is always true; NG-SOS may send test incidents as heartbeat requests. The health endpoint returns 200 when the connector is available.