No logo available for MarketAux to DuckDB connector icon

Load MarketAux data to DuckDB

Build a MarketAux to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the MarketAux API base URL, auth, endpoints, and incremental loading.

SourceMarketAuxMarketAux API DocumentationDestinationDuckDBIn-process analytical database. The default local destination for dlt pipelines.

MarketAux is a financial news data platform providing stock market news with sentiment analysis and entity tagging via a REST API. Everything needed to build a working MarketAux → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.


Build your MarketAux to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

Prompt
Run uvx dlthub-init@latest to build a pipeline from MarketAux to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the MarketAux API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.


MarketAux API at a glance

Base URLhttps://api.marketaux.com/v1
Example endpointGET news/all
Records found atdata
Authenticationall requests require an api_token passed as a query parameter
PaginationPage-number
API referencehttps://www.marketaux.com/documentation

These values come from the MarketAux API reference — the authoritative source if anything here looks out of date.


How do I authenticate with the MarketAux API?

Authentication is performed by passing a unique API token as a query parameter named 'api_token' on every request. No headers are required for authentication.

1. Get your credentials

To obtain your credentials for the MarketAux REST API, follow these steps: 1. Navigate to the MarketAux website and create a free account. 2. Once your account is created, log in to your account. 3. Navigate to your user dashboard. 4. Locate the section labeled 'API Key' or 'Settings' to find your unique API token. This token is required to authenticate all API requests.

2. Add them to .dlt/secrets.toml

[sources.marketaux_source] api_token = "your_api_token_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.


What MarketAux data can I load into DuckDB?

These are the MarketAux endpoints dlt can load into DuckDB:

ResourceEndpointMethodData selectorDescription
news_allnews/allGETdataList news articles (supports pagination via page and limit; returns meta and data)
news_headlinesnews/headlinesGETdataList headline items (paginated via limit/page)
news_sentimentnews/sentimentGETdataList sentiment-tagged news for specified symbols
news_by_uuidnews/similar/{uuid}GETdataFetch similar news by UUID (response includes data)
entity_stats_aggregationentity/stats/aggregationGETdataEntity stats (aggregation) for countries/other group_by filters
entity_trendingentity/trendingGETdataTrending entities
entitiescompaniesGETdataResolve companies/tickers metadata
sourcessourcesGETdataList available news sources (publishers)

How do I load only new MarketAux records?

The MarketAux API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

{"name": "news_all", "endpoint": { "path": "news/all", # Replace with a field that increases on every write. "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"}, }}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.


What does the generated MarketAux pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /news/all and /news/headlines from the MarketAux API into DuckDB:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def marketaux_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.marketaux.com/v1", "auth": {"type": "api_key", "api_key": api_token, "name": "api_token"}, }, "resources": [ {"name": "news_all", "endpoint": {"path": "news/all", "data_selector": "data"}}, {"name": "news_headlines", "endpoint": {"path": "news/headlines", "data_selector": "data"}} ], } yield from rest_api_resources(config) def load_marketaux_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="marketaux_pipeline", destination="duckdb", dataset_name="marketaux_data", ) load_info = pipeline.run(marketaux_source()) print(load_info) if __name__ == "__main__": load_marketaux_to_duckdb()

Run it with python marketaux_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.


How do I query MarketAux data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("marketaux_pipeline").dataset() df = data.news_all.df() print(df.head())

SQL:

SELECT * FROM marketaux_data.news_all LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.


How do I deploy the MarketAux to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

  • Deploy & schedule — run the pipeline as a managed job with automatic retries.
  • Monitor — observable job queues, alerting, and load metrics for every run.
  • Transform — promote raw MarketAux loads into governed, documented models.
  • Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →


What other destinations can I load MarketAux data to?

dlt loads into any of these — only the destination argument changes:

DestinationExample value
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.


Next steps

Was this page helpful?

Community Hub

Need more dlt context for MarketAux to DuckDB?

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