Authentication
Databar uses API keys to allow access to the API. Include your key in thex-apikey header on every request.
Base URL
All API requests should be made to:Async Pattern
Some operations (bulk enrichments, waterfalls) run asynchronously. The flow is:Poll for results
Call
GET /v1/tasks/{request_id} with the task_id. The status field will be processing, completed, or failed.Pagination
TheGET /v1/table/{table_uuid}/rows endpoint supports pagination:
| Parameter | Default | Description |
|---|---|---|
per_page | 1000 | Number of rows to return per page. |
page | 1 | Page number to retrieve. |
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 adetail field describing the issue.
Common Error Codes
| Code | Meaning | When it happens |
|---|---|---|
400 | Bad Request | Invalid or missing parameters in your request. The response body shows which fields failed validation. |
403 | Forbidden | Your API key is missing, invalid, or doesn’t have access to the requested resource. |
404 | Not Found | The enrichment, waterfall, table, or task ID you referenced doesn’t exist. |
406 | Insufficient Credits | Your account doesn’t have enough credits or your plan doesn’t support this operation. |
410 | Gone | The requested data has expired. Task results are deleted after 1 hour. |
422 | Validation Error | The request body failed schema validation. The response includes field-level error details. |
Error Response Formats
Parameter validation error (400):BATCH_TOO_LARGE, UNKNOWN_COLUMNS, INVALID_DATA.
Insufficient credits (406):