Documentation
Connect OpsCommand to everything you run.
Guides and references for the people who connect OpsCommand to their systems and run it.
The API
GET /v1/openapi.json
GET /v1/organisations/{org}/…
Authorization: Bearer …
Idempotency-Key: …
200 application/json
4xx application/problem+json
X-Request-Id: …All guides
Fifteen guides, by what you are doing.
01
Connect your systems
Send signals, deployments and reports into OpsCommand.
02
Developer tools
Link incidents to code, and let assistants help within limits.
03
Operate and govern
AI, workflows, analytics, regulatory reports and your data.
- AI in OpsCommandWhat AI does, how it is evaluated, and what it never does→
- Custom workflowsFields, subcategories, sub-statuses and automation rules→
- AnalyticsIncidents and response, computed from the records→
- Regulatory reportsNIS2, GDPR breach and DORA clocks, drafts and evidence→
- Export and erasureAn organisation’s export, closing and erasure; a person’s data→
04
Brand and deploy
Your own name on public pages, or OpsCommand on your servers.
Reference
The API
Everything the web app does, it does through the API: OpenAPI 3.1, JSON, versioned in its path.
- OpenAPI 3.1
/v1/openapi.json - RFC 9457
application/problem+json - Idempotency-Key
POST, safe to retry - X-Request-Id
On every answer