This page lists the changes to the Pristo API that affect your integration, newest first. The API reference always describes the current API; this page says what changed and when.
The API has one version, v1, at https://api.pristo.io. A change that would break existing calls keeps the old behavior working and is listed here first.
21 October 2026
Section titled “21 October 2026”The API reference on this site replaces the old developer pages. It describes the API as released on 11 October 2026. If you built against the old pages, check these differences:
- The base URL is
https://api.pristo.io. - You create API keys in the Pristo CX app. See Authenticate with an API key.
- The API has two operations: send an event and generate a survey link. There is no endpoint that saves or reads contacts or responses.
- A survey link’s
languagesets the language of the link’s expired and thank-you pages only. The questionnaire opens in its main language. - A missing or unknown API key returns 401 with a problem JSON body. The other errors are listed in API errors.
23 August 2026
Section titled “23 August 2026”- Each API key belongs to one program: the program that was active in the app when the key was created. Keys created earlier were assigned to the account’s first program.
POST /v1/events/sendfinds the population from the key’s program. The older routePOST /v1/events/send/{popId}still works and does the same thing; itspopIdis ignored. Use/v1/events/sendin new code.
3–6 August 2026
Section titled “3–6 August 2026”- API access is part of the Standard and Pro plans. Creating, activating and renaming a key on another plan returns 403. Deactivating and deleting a key always work.
- An account can have up to 10 active API keys.
- Keys that were created before this rule on a plan without API access were revoked.