Connected workflows
Automate Orqit with API keys, scopes, and documented rate limits.
Integrations
Automate against a real public API
Authenticate, call resources, and glue Orqit into your internal platforms with OpenAPI-backed docs.
Overview
The REST API is the primary machine interface for Orqit—documented via public OpenAPI.
Audience
Who this is for
- Integration admins
- ITSM owners
- Platform engineers
Challenges
Problems we address
-
Tool islands Work happens in chat or Jira while Orqit holds the system of record.
Context
How Orqit approaches this
Build scripts and services that create work, sync status, or trigger operational flows while respecting tenant auth and rate limits.
Capabilities
Platform capabilities
Public REST API surface for automating Orqit operations.
Tenant-scoped setup
Configure from admin integration experiences with least privilege.
Details
In depth
Status
Yes — public API for tickets, assets, users (read), projects/tasks, webhook management.
Related
FAQ
Common questions
OAuth for APIs?
Public APIs authenticate with API keys today (Bearer or X-API-Key), not as an OAuth resource server.
Next step
Ready to modernize IT operations?
Launch a pilot workspace or book a walkthrough — with estimated seat savings versus legacy suites, plus 24/7 support.
Entity graph