First-request guide for Create a New Subscription.
Create a New Subscription
Create a New Subscription
Overview
Use this endpoint to create a subscription for monitoring updates to companies or DB Person records. Subscriptions allow you to receive change alerts via webhook and access historical alerts via API. Each subscription is processed asynchronously. A jobId is returned on submission. Upon completion, the job will return a subscriptionId which can be used to fetch alerts or manage the subscription.
Quickstart
Follow these two steps to make a request and recognize a successful response.
Make a request
curl --request POST \
--url https://uapi.demandbase.com/data/b2b/v1/subscriptions/job \
--header "Authorization: Bearer $DB_API_KEY" \
--header "Content-Type: application/json" \
--data '{"companyIds":[1,2,3,4,5],"name":"Company Subscription","description":"This is a subscription for company updates","subscriptionType":"company","startDate":"2025-06-25","frequency":"7d","fields":["all"],"webhook":"http://www.your-domain.com/webhook","signingSecret":"secret-key"}'Read the response
{
"jobId": "39ddf756-c04e-465c-b8c1-8d2c2be0abed",
"jobStatus": "accepted",
"totalEntitiesProcessed": 0,
"jobType": "notificationSubscriptionCreate",
"subscriptionType": "company",
"createdAt": "2025-06-25T09:00:42.620Z"
}Request anatomy
Build the request from the method, path, parameters, and payload described below.
Parameters
This endpoint does not define additional parameters.
Request body
No fields are defined for this payload.
Response anatomy
The endpoint returns 202 for the documented success case. Successful operation
The response schema does not enumerate fields; inspect the example response and status code.
Rules
- Use
POSTwith the path/subscriptions/job. - Required inputs: No parameters are marked required in the published schema..
- Authenticate every request with a valid Demandbase access token.
- Send the request body as
application/json.
Filters
This endpoint has no additional filters or parameters beyond its authentication requirements.
Errors
Handle non-success responses explicitly so your integration can report actionable failures.
| Status | Meaning |
|---|---|
400 | Bad Request |
401 | Unauthorized because the user is not authenticated. |