Create an import job — Guide

First-request guide for Create an import job.

API GUIDE

Create an import job

Create an import job

POST/jobJSONAuthentication required

Overview

Create a new job to perform a Data Import. This is prerequisite before posting a file with records to be imported.

Call the endpoint

Send a POST request to /job with the required authentication and parameters.

Build the request body

Use the JSON shape below and replace example values with your data.

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 POST \
  --url https://uapi.demandbase.com/import/v1/job \
  --header "Authorization: Bearer $DB_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"dataImportName":"example","entityType":"example","source":"example","activityTypeId":1}'
STEP 2

Read the response

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

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 200 for the documented success case. Returns a JSON object of the newly-created job. The Job ID will be used to upload data and to check on job status.

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

Rules

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

StatusMeaning
400Returned if the job specification in the request body does not match the required format.
401Returned if the authentication credentials are missing or invalid.
403Returned if the authenticated user lacks the "Import Data" permission
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