JAGGAER Contacts API
Event contact management
JAGGAER Contacts API is one of 16 APIs that JAGGAER publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Contacts. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 6 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version v26.0.0.4.
Requests are made against a single base URL, https://ches.aso-api.jaggaer.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
JAGGAER Contacts API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerAuth).
An API key is passed in the header as X-Api-Key (apiKeyHeader).
By default, every request must be authenticated.
bearerAuth— OAuth 2.0 bearer token for authentication.apiKeyHeader— API key passed as a request header.
Paths & Operations 6
Across 5 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Event contact management
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ContactResponse (5 properties), ContactCreateRequest (3 properties), ContactUpdateRequest (3 properties), ContactListResponse (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from JAGGAER 12
Other APIs JAGGAER publishes across the network.