Financial Times Python API Docs | dltHub

Build a Financial Times-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Financial Times provides REST APIs for developers to integrate FT content into their applications and services. The REST API base URL is https://api.ft.com and all requests require an API key via header or query parameter.

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 add "dlt[hub]" and start loading Financial Times data in under 10 minutes.


What data can I load from Financial Times?

Here are some of the endpoints you can load from Financial Times:

ResourceEndpointMethodData selectorDescription
notificationscontent/notificationsGETGet list of content created/changed/deleted
contentcontent/{itemId}GETGet specific article content
enriched_contentenrichedcontent/{itemId}GETGet enriched article metadata
searchcontent/search/v1POSTSearch for content items
notifications_pushcontent/notifications-pushGETStreaming notifications

How do I authenticate with the Financial Times API?

All requests require an API key, which must be passed as an 'X-Api-Key' HTTP header or an 'apiKey' query parameter.

1. Get your credentials

To obtain Financial Times API credentials, you must join the FT Developer Programme and formally request access. First, visit the FT Developer Programme portal to register for a developer account. Once registered, you must submit a sales or licensing enquiry to the FT's B2B team (via the 'Request an API Key' documentation link or by contacting b2b.channels@ft.com) to discuss your specific use case and purchase or arrange a licence agreement. API keys are issued based on these agreed-upon terms, and some services may not be available on a self-service basis. Once approved and licensed, the FT will provide your API key, typically via email.

2. Add them to .dlt/secrets.toml

[sources.financial_times_source] ft_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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Financial Times 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:

uv run python financial_times_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline financial_times_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset financial_times_data The duckdb destination used duckdb:/financial_times.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub 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 content and enrichedcontent from the Financial Times 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 financial_times_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.ft.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "notifications", "endpoint": {"path": "content/notifications", "data_selector": "notifications"}}, {"name": "search", "endpoint": {"path": "content/search/v1", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="financial_times_pipeline", destination="duckdb", dataset_name="financial_times_data", ) load_info = pipeline.run(financial_times_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("financial_times_pipeline").dataset() sessions_df = data.notifications.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM financial_times_data.notifications LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("financial_times_pipeline").dataset() data.notifications.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 Financial Times data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Financial Times?

Request dlt skills, commands, AGENT.md files, and AI-native context.