Skip to main content
The Dataville API authenticates requests with an API key. Send the key in the Authorization header on every request. Requests without a key are limited to data lookups, at 50 requests per 24 hours per IP address. This allowance is for evaluating the API before you create an account and is not compatible with production usage.

Managing API keys

You can create and manage your API key on the API Keys page of the dashboard. Keys start with dataville_.
The API Keys page in the Dataville dashboard: a Replace Key button above a table of keys showing name, key prefix, status, last used, created date, and Reveal, Copy, and Revoke actions.
Each Dataville account can have one active API key. If you generate a new API key, your previous key will be deactivated.

Sending the key

Send the key in the Authorization header using the Bearer scheme:

Passing the key as a query parameter

Some clients cannot set request headers, including DuckDB’s httpfs extension and DuckDB WASM. These clients can pass the key in the token query parameter:
The token parameter is accepted on data lookups, export downloads, and the MCP endpoint:
  • GET /{source}/{keywords}
  • GET /https:/{wikipediaUrl}
  • GET /api/v1/export/{source}
  • GET /api/v1/export/dataville.db, dataville.csv.zip, and dataville.parquet.zip
  • POST /mcp
For security reasons, you should always use the Authorization header when possible. Passing API keys as a parameter is supported purely for compatibility reasons and should not be considered best practice.

MCP authentication

You can also use your API key to authenticate with Dataville’s MCP server. Learn more on the MCP page.