MATTR Python API Docs | dltHub
Build a MATTR-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The MATTR API documentation provides endpoints for issuing authorization codes, pre-authorized codes, and credential offers. The core API manages MATTR VII tenant interactions, while additional APIs extend capabilities for verification and credential management. The documentation is essential for integrating MATTR services. The REST API base URL is https://{tenant_url} and All protected requests require a Bearer access token in the Authorization 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 MATTR data in under 10 minutes.
What data can I load from MATTR?
Here are some of the endpoints you can load from MATTR:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| issuer_metadata | /.well-known/openid-credential-issuer | GET | Retrieve OpenID Credential Issuer metadata (issuer, authorization_endpoint, token_endpoint, credential_endpoint, credentials_supported, credential_configurations_supported). | |
| credentials | /v2/credentials | GET | data | List credentials in the tenant (cursor pagination: 'limit' and 'cursor'; list payload returned in 'data'). |
| mobile_iacas | /v2/credentials/mobile/iacas | GET | data | Retrieve mobile IACA (IACA list) for credentials/mobile channel (tenant-specific mobile iacas list; paginated). |
| oauth_authorize | /v1/oauth/authorize | GET | Authorization endpoint (opens redirect for authorization_code flows; may return error object on invalid requests). | |
| dids | /v1/dids | GET | data | List DIDs for tenant (list responses follow standard list format using 'data'). |
How do I authenticate with the MATTR API?
MATTR uses OAuth2 client_credentials to obtain a Bearer access token from the tenant's auth server (auth_url). Include the token in the Authorization header: "Authorization: Bearer <access_token>".
1. Get your credentials
- Obtain your tenant details (auth_url, audience, tenant_url, client_id, client_secret) from MATTR tenant creation/email or console.
- Request a token: POST https://{auth_url}/oauth/token with body (application/json or x-www-form-urlencoded as docs indicate): { "client_id": "<client_id>", "client_secret": "<client_secret>", "audience": "", "grant_type": "client_credentials" }
- Receive { "access_token": "...", "expires_in": ..., "token_type": "Bearer" }.
- Use header Authorization: Bearer <access_token> for protected endpoints.
- Renew token when expired (use client credentials flow).
2. Add them to .dlt/secrets.toml
[sources.mattr_source] token = "your_access_token_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 MATTR 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 mattr_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline mattr_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mattr_data The duckdb destination used duckdb:/mattr.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline mattr_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 credentials and issuer_metadata from the MATTR 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 mattr_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{tenant_url}", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "credentials", "endpoint": {"path": "v2/credentials", "data_selector": "data"}}, {"name": "issuer_metadata", "endpoint": {"path": ".well-known/openid-credential-issuer"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mattr_pipeline", destination="duckdb", dataset_name="mattr_data", ) load_info = pipeline.run(mattr_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("mattr_pipeline").dataset() sessions_df = data.credentials.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM mattr_data.credentials LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("mattr_pipeline").dataset() data.credentials.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 MATTR 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.
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 MATTR?
Request dlt skills, commands, AGENT.md files, and AI-native context.