First-request guide for Create export job (Account, Opportunity, Person, Activity, Campaign, and Creative).
Export API guide
Create an export job
Start an asynchronous export with an explicit entity, field selection, and output format.
On this page: QuickstartRequest anatomyResponse anatomyRules and constraintsEmpty resultsErrors and recoveryNext steps
Before you start
Common workflows
Quickstart
Step 1 — Send the request
curl --request POST \
--url https://uapi.demandbase.com/data/export/v1/job \
--header "Authorization: Bearer $DB_API_KEY" \
--header "Content-Type: application/json" \
--data '{"entityType":"account","jobName":"AccountExportJob","fields":["{Account}.name","{Account}.industry"],"format":"CSV"}'
Request body
{
"entityType": "account",
"jobName": "AccountExportJob",
"fields": [
"{Account}.name",
"{Account}.industry"
],
"format": "CSV"
}
Request anatomy
| Part | Required | What to send |
|---|---|---|
| entityType | required | Export object to generate. |
| jobName | required | Client-readable name for the job. |
| fields | required | Array of field tokens from the fields endpoint. |
| fromDate / toDate | conditional | Required for activity and other date-bounded variants. |
| format | optional | CSV or JSON. |
Response anatomy
| Field | Type / state | How to use it |
|---|---|---|
| jobId | string | Identifier used to check status. |
| jobStatus | accepted | The asynchronous job has been queued. |
| entityType | string | Entity selected for the job. |
| createdAt | timestamp | Creation time in ISO-8601 format. |
Rules and constraints
- The fields array is required and must contain valid names for the selected entity.
- Activity exports require fromDate and toDate; campaign and creative ad reports may require adReportType and source.
- Buying-group and source-account variants have additional conditional properties.
- Store jobId and do not assume an accepted job has a downloadable result.
Empty results
A successful submission can still produce a file with no rows. Treat an empty export as valid, then verify filters, date range, entity access, and field selection.
Errors and recovery
Handle these responses explicitly so your integration can report an actionable cause and next step.
| Status | Meaning | Recovery |
|---|---|---|
| 400 | The job body fails validation. | Check required fields, conditional properties, enum values, and date format. |
| 401 | The bearer token is missing, expired, or invalid. | Refresh the token and retry once authenticated. |
| 403 | The tenant cannot create this export. | Confirm export permissions and entity access. |
| 429 | The API rate limit was exceeded. | Back off, honor Retry-After when supplied, and retry safely. |