Getting Started with Zeta APIs

ZMP RESTful APIs

ZMP provides a RESTful API with endpoints for interacting with people, resources, events, and recommendations.

The API can be accessed using the standard HTTP request methods GET, POST, and PUT. There are several endpoints that can be used to manage events, resources, and users.

Zeta REST API Authorization

The Zeta REST API by default uses a Basic authentication pattern where the username is "api," and the password is the 32-character REST API key found in your ZMP account under Settings > Integrations > Keys & Apps.

There is also a JSON Web Token (JWT) JSON Web Token authorization option that can be enabled for you; please reach out to have this turned on for your account(s). To access these routes, supply a bearer token to the route as part of an Authorization header. You can generate a JSON Web Token by first generating a refresh token within the Keys and Apps page under Integrations in the settings section of ZMP. Once you have a refresh token, you can use it to generate a bearer token using our Authorization API.

Server-Side Integration REST API Authorization

Authorization for SSI REST APIs is granted via JSON Web Token (JWT) JSON Web Token. To access these routes, supply a bearer token to the route as part of an Authorization header. You can generate a JSON Web Token by requesting one using our Authorization API.

Zeta DSP API

To request access to the Zeta DSP API, visit the Zeta Programmatic Service Desk.

Missing something? Check this supplemental Zeta DSP API Article for more information on the Zeta DSP API.

API Compatibility and Integration Guidelines

Zeta APIs may evolve over time as new functionality is introduced. These updates may include new response fields, optional parameters, objects, or resources. Such additive changes are considered non-breaking changes and may be introduced without a new API version.

To ensure your integration remains compatible with future API updates, do not use strict schema validation that rejects unknown or additional response fields. API clients and deserializers should safely ignore response fields they do not recognize.

Zeta considers changes to existing API behavior—such as removing or renaming fields, changing a field's data type or meaning, or changing an optional parameter to required—to be breaking changes.

Need Help?

If you have any questions or would like to learn more, don't hesitate to reach out to us!