Workday Financial Management Python API Docs | dltHub
Build a Workday Financial Management-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Workday Financial Management REST API provides programmatic access to financial operations, accounting data, and reporting capabilities within the Workday platform. The REST API base URL is https://{tenantHostname}/ccx/api/financial-management/{version}/{tenant} and all requests require a Bearer token obtained via OAuth 2.0 authentication flows.
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 Workday Financial Management data in under 10 minutes.
What data can I load from Workday Financial Management?
Here are some of the endpoints you can load from Workday Financial Management:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| ledger_accounts | /ledgerAccounts | GET | data | Retrieve a collection of ledger accounts |
| accounts | /accounts | GET | data | Returns a collection of general ledger accounts |
| supplier_invoices | /supplierInvoices | GET | data | Retrieve a collection of supplier invoices |
| ledger_account_details | /ledgerAccounts/{id} | GET | Retrieve details of a specific ledger account | |
| account_details | /accounts/{accountId} | GET | Retrieve details of a specific general ledger account | |
| supplier_invoice_details | /supplierInvoices/{id} | GET | Retrieve details of a specific supplier invoice |
How do I authenticate with the Workday Financial Management API?
Workday REST APIs use OAuth 2.0 bearer tokens for authentication. Requests to the REST API must include an Authorization header with the value 'Bearer <access_token>'. Requests to the token endpoint typically require a Basic or custom 'ID' header containing base64-encoded client credentials.
1. Get your credentials
- Log in to your Workday tenant and search for the 'Register API Client' task. 2. Configure the client by setting a Client Name, selecting the appropriate grant type (e.g., 'Authorization Code Grant' for user-authorized access or 'Client Credentials' for server-to-server), and choosing 'Bearer' as the access token type. 3. Define the required scopes (e.g., Financials) and, if necessary for long-term access, enable 'Non-expiring Refresh Tokens'. 4. Save the registration to generate and retrieve your 'Client ID' and 'Client Secret'. 5. If using Client Credentials, perform the additional 'Create Integration System User' task and 'Create Client Credentials Mapping' task to link the API Client with an integration user. Securely store these credentials.
2. Add them to .dlt/secrets.toml
[sources.workday_financial_management_source] access_token = "REPLACE_ME"
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 Workday Financial Management 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 workday_financial_management_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline workday_financial_management_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset workday_financial_management_data The duckdb destination used duckdb:/workday_financial_management.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 /authorize and /token from the Workday Financial Management 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 workday_financial_management_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{tenantHostname}/ccx/api/financial-management/{version}/{tenant}", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "ledger_accounts", "endpoint": {"path": "ledgerAccounts", "data_selector": "data"}}, {"name": "accounts", "endpoint": {"path": "accounts", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="workday_financial_management_pipeline", destination="duckdb", dataset_name="workday_financial_management_data", ) load_info = pipeline.run(workday_financial_management_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("workday_financial_management_pipeline").dataset() sessions_df = data.ledger_accounts.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM workday_financial_management_data.ledger_accounts LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("workday_financial_management_pipeline").dataset() data.ledger_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 Workday Financial Management 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.
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 Workday Financial Management?
Request dlt skills, commands, AGENT.md files, and AI-native context.