TimeClock 365 Python API Docs | dltHub

TimeClock 365 is a workforce management platform offering an open API for accessing attendance records, employee data, and real-time events. The REST API base URL is https://live.timeclock365.com/api/v1/json-rpc and all requests require a Bearer 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 TimeClock 365 data in under 10 minutes.

---

What data can I load from TimeClock 365?

Here are some of the endpoints you can load from TimeClock 365:

---

How do I authenticate with the TimeClock 365 API?

All requests require an Authorization header with a Bearer token, formatted as 'Authorization: Bearer YOUR_API_TOKEN'.

1. Get your credentials

Log in to your TimeClock 365 admin dashboard. Navigate to Settings, then select Integrations, and click on API Keys. From there, you can generate and manage your API token. Once generated, use this token in the Authorization header of your API requests as a Bearer token.

2. Add them to .dlt/secrets.toml

Copy
[sources.timeclock_365_source]
api_key = "your_api_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI harness:

Copy
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:

Copy
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 TimeClock 365 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:

Copy
python timeclock_365_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline timeclock_365_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset timeclock_365_data
The duckdb destination used duckdb:/timeclock_365.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline timeclock_365_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 timesheet and employees from the TimeClock 365 API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def timeclock_365_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://live.timeclock365.com/api/v1/json-rpc",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "sessions", "endpoint": {"path": "api/v1/json-rpc"}},
            {"name": "lunches", "endpoint": {"path": "api/v1/json-rpc"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="timeclock_365_pipeline",
        destination="duckdb",
        dataset_name="timeclock_365_data",
    )
    load_info = pipeline.run(timeclock_365_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):

Copy
import dlt

data = dlt.pipeline("timeclock_365_pipeline").dataset()
sessions_df = data.sessions.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM timeclock_365_data.sessions LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("timeclock_365_pipeline").dataset()
data.sessions.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 TimeClock 365 data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

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.

Copy
dlthub ai toolkit data-exploration install
dlthub ai toolkit dlthub-platform install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack