Don’t worry if some of these are new. Each one is just a name for something simple.Documentation Index
Fetch the complete documentation index at: https://docs.trydatadriver.com/llms.txt
Use this file to discover all available pages before exploring further.
API
A way for two programs to talk over the internet. You send a
request, the API sends a response. Like ordering at a drive-thru:
you say what you want, you get it back.
HTTP
The language of the web. Every request has a method (GET =
read, POST = send data), a URL (where to send it), headers
(extra info), and sometimes a body (the data).
JSON
A text format for data. Looks like
{"name": "Cody", "age": 35}.
The API speaks JSON for both questions and answers.API key (bearer token)
A secret string that identifies you. You send it in a header on
every request:
Authorization: Bearer dd_xxxx. Treat it like a
password.Filter
A rule that narrows down what you get back. Like searching
“homeowners in Texas, age 30-50” — you only get matching rows.
Pagination & cursor
If a query matches 10,000 rows, we don’t dump all of them at once.
We send 100 at a time + a cursor (like a bookmark) so you can
ask for the next 100.
Export
For really big pulls, paginating is slow. Instead, you ask us to
generate a CSV file. We build it in the background and give you a
download link.
Rate limit
The max requests you can send per minute (60 by default). Go over
and you’ll get a 429 error telling you to wait.
The mental model. You’re a client. We’re a server. You make
HTTP requests with your API key. We send JSON back. That’s the
whole API.