Skip to main content

Authentication

Databar uses API keys to allow access to the API. Include your key in the x-apikey header on every request.
To find your API key, head over to your Databar workspace and click Integrations.

Base URL

All API requests should be made to:

Async Pattern

Some operations (bulk enrichments, waterfalls) run asynchronously. The flow is:
1

Submit the request

Call a run or bulk-run endpoint. You’ll receive a task_id in the response.
2

Poll for results

Call GET /v1/tasks/{task_id} with the task_id. The status field will be processing, completed, or failed.
3

Retrieve your data

When status is completed, the data field contains your results. For bulk runs, data is aligned to your inputs: one element per input, in the same order you submitted them, with null for inputs that returned no data (so len(data) equals the number of inputs and data[i] is the result for input i). A single (non-bulk) run returns the result object directly.
Data from enrichment and waterfall tasks is stored for 24 hours. After that, the data is permanently deleted and the task status will return gone. Make sure to retrieve your results promptly.

Pagination

The GET /v1/table/{table_uuid}/rows endpoint supports pagination: The response includes has_next_page and total_count to help you iterate.

Error Handling

The API uses standard HTTP status codes. All error responses return a JSON body with a detail field describing the issue.

Common Error Codes

Error Response Formats

Parameter validation error (400):
Batch operation error (400) — for row insert/update/upsert:
Batch error codes: BATCH_TOO_LARGE, UNKNOWN_COLUMNS, INVALID_DATA. Insufficient credits (406):
Schema validation error (422):