Use these models as a reference when building integrations. Request and response bodies use application/json (or multipart/form-data for SOP uploads). Successful responses are wrapped in the standard envelope; error responses follow RFC 7807 ProblemDetails — see the error reference for the full catalogue.
Response Envelopes
Success response
Paginated response
Error response
Errors are RFC 7807 ProblemDetails, served as application/problem+json. Switch on the stable code extension; the title and detail strings are human-readable and may be reworded between releases.
The full set of code values, validation errors map shape, and resolution guidance live on the error reference page.
Incidents
Incident object
Returned by GET /workspaces/{workspaceId}/incidents/{source}/{incidentId}:
Enum values:
Response object from GET /workspaces/{workspaceId}/incidents/{source}/{incidentId}/comments:
List incidents across workspaces
Request body for POST /incidents/across-workspaces:
Time filter enum values for type: TwentyFourHours, SevenDays, ThirtyDays, Custom
When using Custom, include customStartUtc and customEndUtc:
Webhooks
Webhook configuration
Response object from GET /webhooks/{id}:
Create webhook
Request body for POST /webhooks:
Enum values for authenticationType: None, Bearer, Basic, ApiKey
Delivery log
Response object from GET /webhooks/{id}/delivery-logs/{logId}:
Service Accounts
Service account
Response object from GET /service-accounts/{id}:
Create service account
Request body for POST /service-accounts:
Credential created (shown once)
Response from POST /service-accounts/{id}/credentials:
The clientSecret is returned only once in this response. Store it immediately in a secrets manager.
Users
User object
Response object from GET /users/{userId}: