Get Bulk Job Status — Guide

First-request guide for Get Bulk Job Status.

API GUIDE

Get Bulk Job Status

Get Bulk Job Status

GET/job/{jobId}No request bodyAuthentication required

Overview

Check the status of a bulk job using its unique job ID. This endpoint supports all bulk job types, including Company Fetch, Contact Fetch, and Match. Once the job completes successfully, the response will contain a signed `resultsUrl` for downloading the results. Important notes: - The `resultsUrl` is included **only when the job status is `finished`** - The URL remains valid for **24 hours** - If the job fails, an `errorMessage` field will be present in the response explaining the reason **CSV Results Format:** - The `resultsUrl` points to a CSV file containing the requested data - CSV column headers correspond exactly to the field names sp…

Call the endpoint

Send a GET request to /job/{jobId} with the required authentication and parameters.

Supply endpoint parameters

Review the parameter table to see which path, query, or header values the endpoint accepts.

Inspect the response

Use the success response shape to validate the fields your integration receives.

Quickstart

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

STEP 1

Make a request

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

Read the response

SUCCESS RESPONSE · HTTP 200
{
  "jobName": "jobNameTest",
  "jobStatus": "finished",
  "jobType": "contactfetch",
  "jobId": "f546c341-2dc3-4797-b43d-59ac0d334346",
  "createdAt": "2024-09-16T04:46:21.684Z",
  "updatedAt": "2024-09-02T06:07:44.550Z",
  "resultsUrl": "https://uapi-results.db-data-api-dev.demandbase.com/bulkjobs/companyfetch/0ab5c350-c6d2-4dcc-a9cd-dbba521f468d/response/c1ebe044-0c93-4643-b4bf-9ab1ea9b4ee3.csv?Policy=..."
}

Request anatomy

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

Parameters

NameLocationTypeRequiredDescription
jobIdpathstringRequiredUnique identifier of the bulk job.

Request body

This endpoint does not define a JSON request body.

Response anatomy

The endpoint returns 200 for the documented success case. Bulk job status fetched successfully. Results URL is present only for finished jobs.

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

Rules

  • Use GET with the path /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.

NameLocationTypeRequiredDescription
jobIdpathstringRequiredUnique identifier of the bulk job.

Errors

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

StatusMeaning
400Bad request. For example, job id is missing or invalid.
401Unauthorized - Missing or invalid tenant ID
404Job not found. Invalid job id.
500Internal server error.

Next steps

Try the quickstart

Start with the request example, then replace the sample values with your credentials and data.

Return to the API area

Back to asynchronous-batch-api

Back to top