Handling Errors

Handling Errors

The Export API returns standard HTTP status codes and a JSON error body with a more specific Demandbase error code.

{
  "errorCode": "400-115",
  "errorMessage": "Invalid field names: {Account}.All, {Account}.test",
  "diagnosticCode": "ce0fc1770e0d425b88892df4f663bf07"
}
PropertyDescription
errorCodeStable Demandbase error identifier. The first three digits match the HTTP status. Use this value when handling a specific failure in your application.
errorMessageHuman-readable details about the failure. Values from the request may be included.
diagnosticCodeOpaque identifier for the individual API request. Record this value in your logs and include it when contacting Demandbase Support. Do not parse it or use it for application logic.

Recommended handling

HTTP statusMeaningRecommended action
400The request is invalid.Correct the indicated parameter or payload. Do not retry the same request unchanged.
401Authentication credentials are missing or invalid.Obtain a valid access token and retry. See Authentication.
403The authenticated API key or tenant cannot access the requested resource.Verify API-key permissions, enabled Export collections, and tenant access.
404The requested resource or job does not exist.Verify the identifier and that it belongs to the authenticated tenant.
429A request, concurrency, or export quota was exceeded.Back off before retrying. See Rate Limits.
500Demandbase could not complete the request because of a temporary service failure.Retry with backoff. If the failure continues, contact Demandbase Support and provide the diagnosticCode.

400 validation errors

Error codeCondition
400-102The request body is not a valid JSON object.
400-103A request parameter is invalid.
400-104A required parameter is missing.
400-111A date is not in yyyy-mm-dd or yyyy-mm-ddThh:mm:ssZ format.
400-112Only one of fromDate and toDate was supplied; both are required together.
400-113fromDate is after toDate.
400-114The requested Activity date range is longer than 90 days.
400-115One or more requested field names are invalid. Use GET /v1/fields to retrieve supported fields.
400-116format is not CSV or JSON.
400-117Export results were requested before the job reached finished.
400-118limit is not numeric.
400-119limit is outside the supported range of 1–1,000.
400-120sort is not ascending or descending.
400-121page is not a positive number.
400-122perPage is not a positive number.
400-123The entityType query value is unsupported.
400-124The jobStatus query value is unsupported.
400-125The entityType supplied to the fields endpoint is unsupported.
400-126jobName is missing or longer than 50 characters.
400-127The request body contains an unsupported entityType.
400-129An account-list ID is not numeric.
400-130performance is unsupported.
400-131Neither creativeId nor campaignId was supplied where one is required.
400-132creativeId is not numeric.
400-133campaignId is not numeric.
400-134accountId is not numeric.
400-135A required account or campaign identifier is missing.
400-136The selected campaign export supports only rollup performance.
400-137fromDate is not before toDate.
400-138source contains an unsupported value or data type.
400-139adReportType is invalid for the selected entity type.
400-140The filter operator is invalid for the selected field's data type.
400-141A person-list ID is not numeric.
400-142One or more account-list IDs do not exist.
400-143One or more person-list IDs do not exist.
400-144accountListId and accountListIds were supplied together.
400-145accountListIds contains more than 10,000 IDs.
400-146personListIds contains more than 10,000 IDs.
400-147The request contains an unrecognized property.
400-148One or more accountIds values are not numeric.
400-149accountIds is required for the selected Buying Group entity type.
400-150accountIds contains more than 10,000 IDs.
400-151One or more companyIds values are not numeric.
400-152companyIds is required for the selected Buying Group entity type.
400-153companyIds contains more than 10,000 IDs.
400-154The requested reference-data object is unsupported.
400-155A requested field is outside the tenant's enabled Export collection, or the selected entity type does not support paginated result retrieval.

Authentication and access errors

Error codeCondition
401-100Authentication credentials are missing or invalid.
403-100The authenticated user is not permitted to perform the requested export.
403-101The tenant cannot access the requested entity type.
403-102The API key cannot access the requested resource.
403-103The tenant does not have an Export collection enabled.
403-104The requested fields are not available in the tenant's enabled Export collection.
403-105The tenant cannot access the requested endpoint.

Resource errors

Error codeCondition
404-301The requested resource does not exist.
404-302The export job ID is invalid or does not exist.
404-303The requested export-result part is invalid or does not exist.

Rate-limit errors

Error codeCondition
429-100The concurrent-query limit was exceeded.
429-101The rolling 24-hour export quota was exceeded.
429-102The concurrent export-job limit was exceeded.

Service errors

Error codeCondition
500-100Demandbase could not complete the request because of a temporary service failure.

When escalating an error, provide the endpoint, UTC timestamp, HTTP status, errorCode, and diagnosticCode. Do not send API credentials or access tokens.


Did this page help you?