Revert Ticketing API
Unified ticketing models - tasks, users, comments, collections.
Revert Ticketing API is one of 6 APIs that Revert publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Ticketing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 11 operations across 7 paths, and defines 1 schema. It is described by OpenAPI 3.0.3, at version 1.0.
Requests are made against 2 base URLs: https://api.revert.dev, http://localhost:4001.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Revert Ticketing API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as x-revert-api-token (revertApiToken).
An API key is passed in the header as x-revert-t-id (revertTenantId).
By default, every request must be authenticated.
revertApiToken— Your Revert API key (private token) for the environment.revertTenantId— The tenant / customer id of the linked connection.
Paths & Operations 11
Across 7 paths, the API surfaces 11 operations — 7 GET, 2 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Unified ticketing models - tasks, users, comments, collections.
Schemas 1
The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Revert 5
Other APIs Revert publishes across the network.