Dynamics CRM Python API Docs | dltHub
Build a Dynamics CRM-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Dynamics 365 (Dataverse) Web API is a RESTful service used for interacting with platform data and table definitions based on the OData protocol. The REST API base URL is https://yourorg.api.crm.dynamics.com/api/data/v9.2/ and all requests require a Bearer token via OAuth 2.0.
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 Dynamics CRM data in under 10 minutes.
What data can I load from Dynamics CRM?
Here are some of the endpoints you can load from Dynamics CRM:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| Service Document | /api/data/v9.2/ | GET | value | Retrieves the list of available entity sets for the environment. |
| Accounts | /api/data/v9.2/accounts | GET | value | Retrieves a collection of account entities. |
| Contacts | /api/data/v9.2/contacts | GET | value | Retrieves a collection of contact entities. |
| Leads | /api/data/v9.2/leads | GET | value | Retrieves a collection of lead entities. |
| Opportunities | /api/data/v9.2/opportunities | GET | value | Retrieves a collection of opportunity entities. |
How do I authenticate with the Dynamics CRM API?
Authentication is handled via OAuth 2.0. Requests must include an Authorization header with a Bearer token: 'Authorization: Bearer <access_token>'
1. Get your credentials
- Register an application in the Microsoft Entra ID (Azure) portal: Go to App registrations, click New registration, provide a name, and select account types. 2. Copy the Application (client) ID and Directory (tenant) ID from the app's Overview page. 3. Generate a client secret: Navigate to Certificates & secrets, click New client secret, add a description, and copy the secret Value immediately (it cannot be retrieved later). 4. Add API permissions: Go to API permissions, click Add a permission, select Dynamics CRM (or Dataverse), and add the user_impersonation delegated/application permission. 5. Grant admin consent for the configured permissions. 6. Link the app to Dynamics 365: In the Power Platform Admin Center, navigate to the specific environment, go to S2S Apps or Users, and add the registered app as an Application User with an appropriate security role (e.g., System Administrator or custom restricted role).
2. Add them to .dlt/secrets.toml
[sources.dynamics_crm_source] dynamics_crm.client_id = "your_application_client_id_here" dynamics_crm.client_secret = "your_client_secret_value_here" dynamics_crm.tenant_id = "your_directory_tenant_id_here" dynamics_crm.resource_url = "https://yourorg.crm.dynamics.com"
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 harness:
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:
dlthub 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 Dynamics CRM 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 dynamics_crm_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline dynamics_crm_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset dynamics_crm_data The duckdb destination used duckdb:/dynamics_crm.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline dynamics_crm_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 Discovery and Organization from the Dynamics CRM 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 dynamics_crm_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://yourorg.api.crm.dynamics.com/api/data/v9.2/", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "accounts", "endpoint": {"path": "accounts", "data_selector": "value"}}, {"name": "contacts", "endpoint": {"path": "contacts", "data_selector": "value"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="dynamics_crm_pipeline", destination="duckdb", dataset_name="dynamics_crm_data", ) load_info = pipeline.run(dynamics_crm_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("dynamics_crm_pipeline").dataset() sessions_df = data.accounts.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM dynamics_crm_data.accounts LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("dynamics_crm_pipeline").dataset() data.accounts.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 Dynamics CRM 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 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.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install
Was this page helpful?
Community Hub
Need more dlt context for Dynamics CRM?
Request dlt skills, commands, AGENT.md files, and AI-native context.