Subscription API

Subscription creation, updates, status, alerts, and lifecycle operations.

START HERE

Make your first request

Use this guide to move from authentication to a valid Subscription API request, then open each endpoint guide for the full request and response details.

1 · AUTHENTICATE

Get an access token

Use the authentication flow for your workspace and send the token as a Bearer credential.

3 · INSPECT

Read the response

Check the status, content type, and documented response fields before processing results.

REQUEST SCHEMA

PUT /subscriptions/job
Endpoint guides explain URL parameters, headers, request bodies, and required values.

RESPONSE SCHEMA

Endpoint guides pair a response example with the generated technical schema so implementation and validation stay together.

B2B API

Subscription API

Create, monitor, and manage subscription jobs, alert delivery, and subscribed entity data through a consistent two-level reference experience.

10 endpointsRequires bearer tokenAlerts and entitiesJob monitoring

Overview

The Subscription API supports the lifecycle around subscription configuration and delivery. Use the overview below to choose the right operation, then open a child page for the exact endpoint request, response, and schema details.

CONFIGURE

Manage subscriptions

List, inspect, update, and delete subscriptions using the operations in the core group.

OBSERVE

Monitor delivery

Review alerts, entity IDs, and job status to understand what the subscription is delivering and how processing is progressing.

OPERATE

Use job workflows

Persist job IDs and poll job status so asynchronous subscription changes are observable and recoverable.

Subscription lifecycle

A typical integration lists or retrieves a subscription, submits any required change job, and monitors the job through completion. Alert and entity operations provide the supporting visibility needed to reconcile downstream state.

Use the child specs

The endpoint pages below define the required subscription IDs, alert IDs, job IDs, request bodies, and response schemas for each lifecycle step.

Endpoint tech specs

Operations are grouped by the workflow they support.

Core subscription operations

Alerts and entities

Subscription jobs

Operational notes

AUTH

Authentication

Send the required bearer token with every request and protect it from browser code, logs, and client-side storage.

IDENTIFIERS

Use returned IDs

Carry subscription, alert, entity, and job IDs between calls exactly as returned by the API.

RECONCILIATION

Handle retries safely

Record request intent and job state so retries do not create unexplained duplicate changes or gaps in downstream delivery.