Overview

Retrieve the current status of a bulk subscription job using its unique job ID. After you submit a create or update subscription job request, you’ll receive a job ID. This endpoint allows you to monitor that job’s progress and determine whether it has completed successfully. If the job completes, the response will include the generated subscriptionId—which you can use to manage the subscription. If the job fails, the response will contain error details explaining what went wrong.

Quickstart

Follow these two steps to make a request and recognize a successful response.

curl --request GET \
  --url https://uapi.demandbase.com/data/b2b/v1/subscriptions/job/ln63a2kv6k2cm09cubar \
  --header "Authorization: Bearer $DB_API_KEY" \
  --header "Accept: application/json"

{
  "jobId": "39ddf756-c04e-465c-b8c1-8d2c2be0abed",
  "subscriptionId": "63914a27-a5ca-4fdf-80b0-ffc985f53c14",
  "jobStatus": "finished",
  "totalEntitiesProcessed": 5000,
  "jobType": "notificationSubscriptionCreate",
  "subscriptionType": "company"
}

Request anatomy

Build the request from the method, path, parameters, and payload described below.

Parameters

Request body

This endpoint does not define a JSON request body.

Response anatomy

The endpoint returns 200 for the documented success case. Job status retrieved successfully.

The response schema does not enumerate fields; inspect the example response and status code.

Rules

• Use GET with the path /subscriptions/job/{jobId}.
• Required inputs: jobId.
• Authenticate every request with a valid Demandbase access token.
• This endpoint does not require a JSON request body.

Filters

The published schema exposes the following endpoint inputs. Use the location column to place each value correctly.

Errors

Handle non-success responses explicitly so your integration can report actionable failures.

Next steps

Back to top