Content-Type: application/json(ormultipart/form-datafor SOP uploads)- Property names are camelCase; enum values are PascalCase (
Sentinel,High,TwentyFourHours) - Workspace IDs and most other identifiers are GUIDs
- Source segment values:
Sentinel,DefenderXDR,CrowdStrike,QRadar,Splunk,SentinelOne
Workspace-Scoped Endpoints
Path prefix:/workspaces/{workspaceId}/...
The workspace ID is a GUID and identifies the customer environment the request operates against. The credential’s service account must have a role on the target workspace, otherwise the request returns 403 INSUFFICIENT_WORKSPACE_ROLE.
- incidents:read
- incidents:comments
- gamebooks:read
- datasources:read
- tickets:read / tickets:manage
- investigation:read
Every incident is the child of one SIEM source — the source is encoded as a route segment, not a query parameter.
Some incident operations that don’t yet thread an explicit SIEM source through their handlers (
/{incidentId}/summary, /{incidentId}/entities, /{incidentId}/alert-rules, assign, status, bulk, comment create/update, /high) have been removed from the v2 surface. They will return once their handlers operate against an explicit source rather than implicitly defaulting to Sentinel.Cross-Workspace Endpoints
These endpoints span every workspace your service account can see — no workspace ID in the path. The handlers filter results to the workspaces the credential has been mapped to.Paginating /incidents/across-workspaces
The cross-workspace incidents list uses opaque continuation tokens. The first request leaves the token map empty; every subsequent request echoes the previous response’s tokens back unchanged. Tokens are server-encrypted strings — treat them as a single blob the API gave you, never parse or construct one yourself.
First request:
isFirstCall: false and pass sourcePageTokens back verbatim as workspacePageTokens:
moreIncidentsAvailable: false. A workspace that has finished paging drops out of sourcePageTokens on subsequent responses; do not synthesize entries for it. Page size is server-controlled.
A token that has been modified or hand-built returns 400 VALIDATION_ERROR with the message One or more pagination tokens are invalid. Use the tokens from the previous response unmodified. Recover by restarting from the first call with an empty workspacePageTokens array.
Organization-Scoped Endpoints
These endpoints operate on the organization (service provider). The credential’s service account must hold the relevant org-level scope; workspace mappings are not required.- webhooks:read / webhooks:manage
- org:service-accounts:read / manage
- org:users:read / manage / roles
- org:azure:read / manage
Read (
webhooks:read):Manage (
webhooks:manage):What Comes Back
Every successful response is wrapped in the standard envelope:pagination block; see the object models page for shapes per endpoint family.
Error responses are RFC 7807 ProblemDetails (application/problem+json) with a stable code extension you can switch on — the error reference lists every code.