Essentials
Responses
Response and error formats for the Stigg REST API
Related topics
REST API OverviewDebugging requests with trace IDsI want to run Stigg Sidecar and API in productionCheck and ingestGetting temporary credentials for event queuesDocumentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Response and error formats for the Stigg REST API
{
"id": "customer-123",
"name": "Acme Corp",
"email": "billing@acme.com",
"createdAt": "2024-01-15T10:30:00Z",
"updatedAt": "2024-01-15T10:30:00Z"
}
| Status | Meaning |
|---|---|
200 | Success — request completed, body contains the resource |
201 | Created — resource was successfully provisioned |
400 | Bad request — invalid parameters or request body |
401 | Unauthenticated — missing or invalid X-API-KEY |
403 | Forbidden — authenticated but not authorized for this resource |
404 | Not found — the specified resource does not exist |
409 | Conflict — e.g. a subscription already exists for this customer |
429 | Too many requests — rate limit exceeded; see Rate Limits |
Related topics
REST API OverviewDebugging requests with trace IDsI want to run Stigg Sidecar and API in productionCheck and ingestGetting temporary credentials for event queues