Event subscriptions
Register endpoints for selected event types.
Subscribe to operational events and fan them into automation, chat, or data pipelines.
Webhooks provide limited, practical outbound event delivery—not a fake MCP server.
Register endpoints, verify payloads, and keep downstream systems in sync when Orqit work changes state.
Outbound event hooks for near-real-time integrations.
Register endpoints for selected event types.
Verify X-Orqit-Signature on every delivery.
Create/list/deactivate subscriptions with webhooks:manage scope.
| Event | When it fires | Typical payload keys |
|---|---|---|
| `ticket.created` | A ticket is created via public API (and other dispatch points that emit this event) | `ticket` |
| `ticket.updated` | A ticket is updated | `ticket` |
| `asset.created` | An asset is created | `asset` |
| `task.updated` | A project task is updated | `task` |
Deliveries include an HMAC signature header (`X-Orqit-Signature`). Recompute the digest with your subscription secret and reject mismatches.
ticket.created, ticket.updated, asset.created, and task.updated.
No. Collaboration hubs may use additional internal domain events. Public webhook subscriptions use the event list above.
Launch a pilot workspace or book a walkthrough — with estimated seat savings versus legacy suites, plus 24/7 support.