They Said So Python API Docs | dltHub
Build a They Said So-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
They Said So is a REST API providing quote-of-the-day, random, search and curated quote image endpoints across categories, authors and tags. The REST API base URL is https://quotes.rest/ and some endpoints are public; private endpoints require an API key via the X-TheySaidSo-Api-Secret header..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading They Said So data in under 10 minutes.
What data can I load from They Said So?
Here are some of the endpoints you can load from They Said So:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| qod | qod.json | GET | contents.quotes | Quote of the day (optionally category via ?category=) |
| qod_categories | qod/categories.json | GET | contents | List of QOD categories |
| random_quote | quote/random.json | GET | contents | Random quote |
| search_quotes | quote/search.json | GET | contents.quotes | Search/random with query params (author, category, minlength, maxlength) |
| quote_categories_popular | quote/categories/popular.json | GET | contents | Popular quote categories |
| authors_popular | quote/authors/popular.json | GET | contents | Popular authors listing |
| image_search | quote/image/search.json | GET | contents | Curated quote images (supports category, author) |
| quote_submit | quote.json | PUT/POST | contents | Create/submit a private quote (requires auth) |
How do I authenticate with the They Said So API?
Public endpoints work without authentication but are rate limited. Private endpoints require an API key passed in the request header X-TheySaidSo-Api-Secret (or as an api_key query parameter, which is discouraged).
1. Get your credentials
- Sign up or log in at They Said So (https://theysaidso.com or https://quotes.rest). 2) From your account/dashboard subscribe to an API plan. 3) Obtain the API key (labelled API Secret or API Key) in the dashboard. 4) Use header X-TheySaidSo-Api-Secret: <your_api_key> for requests.
2. Add them to .dlt/secrets.toml
[sources.they_said_so_source] api_key = "your_api_key_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the They Said So API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python they_said_so_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline they_said_so_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset they_said_so_data The duckdb destination used duckdb:/they_said_so.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline they_said_so_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads qod and quote/search from the They Said So API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def they_said_so_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://quotes.rest/", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "qod", "endpoint": {"path": "qod.json", "data_selector": "contents.quotes"}}, {"name": "search_quotes", "endpoint": {"path": "quote/search.json", "data_selector": "contents.quotes"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="they_said_so_pipeline", destination="duckdb", dataset_name="they_said_so_data", ) load_info = pipeline.run(they_said_so_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("they_said_so_pipeline").dataset() sessions_df = data.qod.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM they_said_so_data.qod LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("they_said_so_pipeline").dataset() data.qod.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load They Said So data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Troubleshooting
Authentication failures
If you get 401/403 responses, ensure you include the header X-TheySaidSo-Api-Secret with a valid API key. Passing api_key as a query parameter is supported but discouraged. Check account subscription and API plan limits.
Rate limiting
Public endpoints are rate limited (example headers from docs: X-RateLimit-Limit: "10 per hour", X-RateLimit-Remaining). If you exceed limits you will receive an error response; reduce request frequency or upgrade your plan.
Pagination & selectors
Most GET list responses place records under contents (e.g. contents.quotes for quotes). Some endpoints return contents directly (e.g. qod/categories returns contents). When writing selectors target the exact key: contents.quotes for arrays of quote objects.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for They Said So?
Request dlt skills, commands, AGENT.md files, and AI-native context.