How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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.2.0, at version v26.1.0.9.

Requests are made against a single base URL, https://ees.aso-api.jaggaer.com.

6 operations 5 paths 6 schemas 1 DELETE2 GET2 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v26.1.0.9
Base URL
https://ches.aso-api.jaggaer.com/
Authentication
HTTP Bearer, API Key
Resource Areas
1

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.

Contacts 6

Event contact management

GET
/event/{event-id}/apiContact/{contact-id}
Contact
getContact 2 params → 200401404
DELETE
/event/{event-id}/apiContact/{contact-id}
Delete Contact
deleteContact 2 params → 204401404
PATCH
/event/{event-id}/user/{user-id}/apiContact/{contact-id}
Contact by User
updateContactByUser 3 params body → 200401404
PATCH
/event/{event-id}/user/{user-id}/apiContacts
Contacts by User (Bulk Update)
updateContactsByUser 2 params body → 200401422
GET
/event/{event-id}/supplier/{supplier-id}/apiContacts
Contacts by Supplier
getContactsBySupplier 2 params → 200401404
POST
/event/{event-id}/user/{user-id}/supplier/{supplier-id}/apiContacts
Contacts by User and Supplier
createContactByUserAndSupplier 3 params body → 200401422

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), ContactBulkUpdateRequest (1 property). Each schema is shown below with its type and property counts.

ErrorResponse
object
Error response with validation details.
1 property
ContactResponse
object
Event contact details.
5 properties
ContactUpdateRequest
object
Request body for updating an event contact.
3 properties
ContactCreateRequest
object
Request body for creating an event contact.
3 properties
ContactListResponse
object
List of event contacts.
1 property
ContactBulkUpdateRequest
object
Request body for bulk updating event contacts.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jaggaer-contacts-api-openapi.yml Raw ↑

Other APIs JAGGAER publishes across the network.

JAGGAER Async API
JAGGAER Attributes API
JAGGAER Awards API
JAGGAER Bids API
JAGGAER Customer Hosts API
JAGGAER Events API
JAGGAER Items API
JAGGAER Jobs API
JAGGAER Locations API
JAGGAER Rates API
JAGGAER Scenarios API
JAGGAER Suppliers API
Where this information came from

This is an independent, third-party profile of JAGGAER Contacts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.