Paycom Python API Docs | dltHub
Build a Paycom-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Paycom provides a REST-based API for accessing payroll, employee, and time-tracking data, requiring formal access granted by a Paycom representative. The REST API base URL is https://api.paycom.com and All requests typically require Basic Authentication using a client-specific SID and API token, often provided by a Paycom representative..
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 Paycom data in under 10 minutes.
What data can I load from Paycom?
Here are some of the endpoints you can load from Paycom:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| employees | /employees | GET | Retrieve list of employees | |
| payrolls | /payrolls | GET | Retrieve list of payroll runs | |
| time_entries | /time_entries | GET | Retrieve time and attendance records | |
| locations | /locations | GET | Get company locations | |
| establishments | /establishments | GET | Get company establishments |
How do I authenticate with the Paycom API?
Paycom typically uses Basic Authentication where the SID acts as the username and the API token as the password, which must be Base64 encoded for the Authorization header. Official documentation provided to clients via the Paycom portal contains the exact endpoint URLs and specific header requirements for your agreement.
1. Get your credentials
Access to the Paycom REST API is restricted and requires a formal commercial agreement with Paycom. To obtain credentials: 1. Contact your Paycom representative to discuss API access and sign the necessary agreement (MSA). 2. Request your 'Paycom API SID' and 'Paycom API Token' from your representative. 3. If required, provide the public IP addresses from which you will access the API so they can be added to Paycom's allowlist. 4. Once authorized, internal documentation can be accessed by a Paycom client admin in the system via 'User Options' -> 'User Access and Security' -> 'API Setup'.
2. Add them to .dlt/secrets.toml
[sources.paycom_source] api_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 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 Paycom 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 paycom_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline paycom_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset paycom_data The duckdb destination used duckdb:/paycom.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline paycom_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 api_get_employee and api_punchhistory from the Paycom 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 paycom_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.paycom.com", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_token}, }, "resources": [ {"name": "employees", "endpoint": {"path": "employees", "data_selector": "data"}}, {"name": "time_entries", "endpoint": {"path": "time_entries", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="paycom_pipeline", destination="duckdb", dataset_name="paycom_data", ) load_info = pipeline.run(paycom_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("paycom_pipeline").dataset() sessions_df = data.employees.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM paycom_data.employees LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("paycom_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 Paycom 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 Paycom?
Request dlt skills, commands, AGENT.md files, and AI-native context.