Export API guide

Export account lists

Start an asynchronous export for all accounts, one list, or multiple account lists.

POST /v1/accountList/job • Authentication: Bearer token

On this page: Quickstart Request anatomy Response anatomy Rules and constraints Empty results Errors and recovery Next steps

Before you start

Send Authorization: Bearer <token> on every request and keep tokens out of logs and source control.

Submit the request, save jobId, poll status, then download the result.

The cURL and JSON examples are copy-ready starting points. Replace IDs, dates, and tokens with values from your tenant.

Export the complete account universe with only jobName when supported for the tenant.

Export one list with accountListId.

Export several lists with accountListIds, then poll the returned jobId.

curl --request POST \

--url https://uapi.demandbase.com/data/export/v1/accountList/job \

--header "Authorization: Bearer $DB_API_KEY" \

--header "Content-Type: application/json" \

--data '{"jobName":"AccountListExport"}'

Request body

{

"jobName": "AccountListExport"

}

{

"jobName": "AccountListExport",

"jobStatus": "accepted",

"entityType": "accountlist",

"jobId": "dcb34525-2baa-4f54-8c11-9e6175ecbc74",

"createdAt": "2024-03-24T16:43:57.378Z"

}

Part	Required	What to send
jobName	required	Client-readable name for the asynchronous job.
accountListId	optional	Single account-list identifier.
accountListIds	optional	Array of account-list identifiers for a multi-list export.

Field	Type / state	How to use it
entityType	accountlist	Identifies this as an account-list export.
jobId	string	Identifier used with the status endpoint.
jobStatus	accepted	The export has been queued.
createdAt	timestamp	Creation time in ISO-8601 format.

Use the single-list and multi-list properties deliberately; do not send both forms in one request.
Keep list IDs available for audit and retry diagnostics.
An accepted response starts an asynchronous workflow; it does not contain the file.

If the resulting file has no rows, confirm that the list IDs exist, the token can access them, and the lists contain accounts at export time.

Handle these responses explicitly so your integration can report an actionable cause and next step.

Status	Meaning	Recovery
400	The list request is malformed or contains invalid IDs.	Send one supported scope form and validate identifiers.
401	The bearer token is missing, expired, or invalid.	Refresh the token and retry after authentication succeeds.
403	The caller cannot access the requested lists.	Check tenant membership and list permissions.
429	The API rate limit was exceeded.	Back off and retry without creating duplicate jobs unnecessarily.