The Databox API allows you to integrate Databox with external systems, automate data ingestion, and extend platform functionality. It follows REST conventions with resource-oriented URLs, JSON request/response bodies, and standard HTTP methods/status codes.
Databox API (v1)
Download OpenAPI description
Languages
Servers
Production server
https://api.databox.com/
Request
Creates an ingestion data source (a container for one or more datasets).
If accountId
is provided, the data source is created in that account; otherwise, it is created in the account associated with the API key.
Requires a valid x-api-key
with permission to create data sources in the target account.
Security
x-api-key
Human-readable name of the data source. May be empty but not null.
Example: "ERP System"
- Production server
https://api.databox.com/v1/data-sources
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api.databox.com/v1/data-sources \
-H 'Content-Type: application/json' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-d '{
"accountId": 123456,
"title": "ERP System",
"timezone": "UTC"
}'
Response
application/json
{ "requestId": "b0eac937-c25c-47a5-bb7e-552f6b860458", "status": "processing", "id": 4754489, "title": "ERP System", "created": "2025-10-01T12:00:00.000000Z", "timezone": "UTC", "key": "ingestion" }
- Production server
https://api.databox.com/v1/data-sources/{dataSourceId}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
https://api.databox.com/v1/data-sources/4754489 \
-H 'x-api-key: YOUR_API_KEY_HERE'
Response
application/json
{ "requestId": "b0eac937-c25c-47a5-bb7e-552f6b860458", "status": "success", "message": "Data source deleted successfully" }
- Production server
https://api.databox.com/v1/data-sources/{dataSourceId}/datasets
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://api.databox.com/v1/data-sources/4754489/datasets \
-H 'x-api-key: YOUR_API_KEY_HERE'
Response
application/json
{ "requestId": "b0eac937-c25c-47a5-bb7e-552f6b860458", "status": "success", "datasets": [ { … } ] }