REST API reference
Base URL: https://api.tngat.com. All requests are JSON and authenticated with Authorization: Bearer <api-key>.
Scoping
Org-scoped requests accept an optional ?orgId= override; without it the caller's active organization is used. Project- and service-scoped routes derive the org from the resource and verify the caller's role on it.
Listing and pagination
List endpoints accept ?limit=, ?cursor= and, on services, ?q= for search. The response body stays a plain array for compatibility, and the paging metadata rides in headers:
Errors
Every failure carries a JSON body with a human-readable message, a stable machine-readable code, and the conventional error label:
{ "error": "Conflict", "message": "This project already has 20 databases…", "code": "resource_limit_exceeded" }Branch on code, never on the message — the message is written for a person and can be reworded, the code is part of the contract.
A status outside the table falls back to request_failed (or internal_error for a 5xx), and a product may tag a more specific code than its status implies — resource_limit_exceeded on a 409 and org_suspended on a 503 are the two the platform distinguishes today. Treat an unfamiliar code as a refusal and show the message.
Most-used endpoints
The complete per-service list is on the REST endpoints page; these are the calls most integrations start with.
Audit
Every mutating call writes an audit row naming the actor, the action, the target and the request outcome. Machine actors are recorded separately from people, so a service account's changes are distinguishable from a member's.