Job status — Guide

First-request guide for Job status.

API GUIDE

Job status

Job status

GET/job/{id}No request bodyAuthentication required

Overview

Use this endpoint to retrieve the current status and relevant details of a specific data import job. The job is identified by the unique path parameter {id} that was returned when the job was initially created.

Call the endpoint

Send a GET request to /job/{id} 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/import/v1/job/1 \
  --header "Authorization: Bearer $DB_API_KEY" \
  --header "Accept: application/json"
STEP 2

Read the response

SUCCESS RESPONSE · HTTP 200
{
  "id": 67849,
  "dataImportName": "EMEA accounts import",
  "entityType": "Account",
  "state": "completed",
  "createdAt": "2019-08-24T14:15:22Z",
  "updatedAt": "2019-08-24T17:53:11Z"
}

Request anatomy

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

Parameters

NameLocationTypeRequiredDescription
idpathinteger (int64)Required

Request body

This endpoint does not define a JSON request body.

Response anatomy

The endpoint returns 200 for the documented success case. The response body contains the comprehensive details of the job's current status and metadata.

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

Rules

  • Use GET with the path /job/{id}.
  • Required inputs: id.
  • 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
idpathinteger (int64)Required

Errors

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

StatusMeaning
400Bad Request Error
401Returned if the authentication credentials are missing or invalid.
403Returned if the authenticated user lacks the "Import Data" permission
404Returned if the referenced job is not found
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 import-job

Back to top