Paycor Python API Docs | dltHub
Build a Paycor-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Paycor is an HCM platform providing a REST API for accessing payroll, HR, benefits, and employee organizational data. The REST API base URL is https://apis.paycor.com and requests require an OAuth 2.0 Bearer token and an APIM subscription key 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 add "dlt[hub]" and start loading Paycor data in under 10 minutes.
What data can I load from Paycor?
Here are some of the endpoints you can load from Paycor:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| employees | v1/employees | GET | Retrieves a list of all employees | |
| legal_entities | v1/legalEntities | GET | Retrieves a list of all legal entities | |
| earnings | v1/employees/{employeeId}/earnings | GET | Retrieves earnings for a specific employee | |
| deductions | v1/employees/{employeeId}/deductions | GET | Retrieves deductions for a specific employee | |
| custom_fields | v1/employees/{employeeId}/customfields | GET | Retrieves custom fields for a specific employee |
How do I authenticate with the Paycor API?
Paycor requires a dual authentication scheme involving an OAuth 2.0 Bearer token provided in the Authorization header and an Ocp-Apim-Subscription-Key header for API management. Both the Access Token and the Subscription Key are mandatory for every API request.
1. Get your credentials
- Create an account on the Paycor Developers Portal (developers.paycor.com). 2. Log in and navigate to the 'Applications' section to create a new 'Standard Application'. 3. Save the 'Application OAuth Client ID' and 'Application OAuth Client Secret' provided upon creation. 4. Navigate to the 'Security Connections' tab within your application details to retrieve the 'APIm Subscription Key'. 5. In the 'Data Access' tab, select the required access scopes and save your changes. 6. Visit the 'General' tab to note the 'Scope Name' (required for authentication). 7. Use these credentials to obtain an OAuth 2.0 access token via the Paycor token endpoint, providing your Client ID, Client Secret, and subscription key as headers/parameters as required by your integration flow.
2. Add them to .dlt/secrets.toml
[sources.paycor_source] client_id = "your_oauth_client_id_here" client_secret = "your_oauth_client_secret_here" subscription_key = "your_apim_subscription_key_here" legal_entity_id = "your_legal_entity_id_here" scope_name = "your_scope_name_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 Paycor 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 paycor_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline paycor_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset paycor_data The duckdb destination used duckdb:/paycor.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 https://apis.paycor.com/sts/v1/common/token and https://apis.paycor.com/v1/ (base URL for API resources) from the Paycor 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 paycor_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://apis.paycor.com", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "employees", "endpoint": {"path": "v1/employees", "data_selector": "$.records[*]"}}, {"name": "legal_entities", "endpoint": {"path": "v1/legalEntities", "data_selector": "$.records[*]"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="paycor_pipeline", destination="duckdb", dataset_name="paycor_data", ) load_info = pipeline.run(paycor_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("paycor_pipeline").dataset() sessions_df = data.employees.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM paycor_data.employees LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("paycor_pipeline").dataset() data.employees.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 Paycor 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 Paycor?
Request dlt skills, commands, AGENT.md files, and AI-native context.