Zaius Consent (Legacy) API
The legacy Consent API is only available for the United States region. Migrate to the latest Update consent API.
Zaius Consent (Legacy) API is one of 17 APIs that Zaius publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Consent (Legacy). The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 1 operation across 1 path, and defines 2 schemas. It is described by OpenAPI 3.0.1, at version v3.
Requests are made against 3 base URLs: https://api.us1.odp.optimizely.com/v3, https://api.eu1.odp.optimizely.com/v3, https://api.au1.odp.optimizely.com/v3.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Zaius Consent (Legacy) API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as x-api-key (x-api-key).
By default, every request must be authenticated.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
The legacy Consent API is only available for the United States region. Migrate to the latest Update consent API.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are GenericUpdateResponse (3 properties), LegacyConsentUpdateRequest (2 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 Zaius 12
Other APIs Zaius publishes across the network.