C1 Access Conflict API
The Access Conflict API from C1 — 2 operation(s) for access conflict.
C1 Access Conflict API is one of 47 APIs that C1 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Access Conflict. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 4 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.1.0, at version 0.1.0-alpha.
Requests are made against a single base URL, https://{tenantDomain}.conductor.one.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
C1 Access Conflict API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
It supports OAuth 2.0 (oauth) using the clientCredentials flow.
By default, every request must be authenticated.
oauth— This API uses OAuth2 with the Client Credential flow. Client Credentials must be sent in the BODY, not the headers. For an example of how to implement this, re…
Paths & Operations 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are c1.api.accessconflict.v1.ConflictMonitor (10 properties), c1.api.accessconflict.v1.ConflictMonitorCreateRequest (3 properties), c1.api.accessconflict.v1.SlackNotifications (3 properties), c1.api.accessconflict.v1.ConflictMonitorUpdateRequestInput (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 C1 12
Other APIs C1 publishes across the network.