Primetric Python API Docs | dltHub

Build a Primetric-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Primetric is a resource planning and time‑tracking platform exposing REST endpoints for projects, employees, assignments, worklogs, timeoffs, contracts and related organization data. The REST API base URL is https://api.primetric.com/beta/ and All requests require OAuth 2.0 access tokens..

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 Primetric data in under 10 minutes.


What data can I load from Primetric?

Here are some of the endpoints you can load from Primetric:

ResourceEndpointMethodData selectorDescription
projectsprojects/GETresultsList of projects (paginated)
project_phasesprojects/{id}/phases/GETresultsPhases for a project
employeesemployees/GETresultsList of employees (paginated)
assignmentsassignments/GETresultsAssignments (resource allocations)
worklogsworklogs/GETresultsWorklogs / timesheet entries
timeoffstimeoffs/GETresultsTime off requests and records
contractscontracts/GETresultsContracts data
custom_attributescustom-attributes/GETresultsCustom attributes definitions
organizationorganization/GETresultsOrganization‑level info

How do I authenticate with the Primetric API?

Primetric uses OAuth 2.0. Include the token in requests with the header Authorization: Bearer <access_token>.

1. Get your credentials

  1. Log in to Primetric as an administrator. 2) Navigate to the Administrator → Integrations or API Applications panel. 3) Create a new Application (choose Authorization Code or Client Credentials). 4) Record the client_id and client_secret; configure a redirect URI if using Authorization Code. 5) Use the token endpoint /auth/token/ to exchange the credentials for an access token.

2. Add them to .dlt/secrets.toml

[sources.primetric_source] client_id = "your_client_id" client_secret = "your_client_secret"

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

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

dlt 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 Primetric 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 primetric_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline primetric_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 projects and employees from the Primetric 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 primetric_source(client_credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.primetric.com/beta/", "auth": { "type": "oauth2", "access_token": client_credentials, }, }, "resources": [ {"name": "projects", "endpoint": {"path": "projects/", "data_selector": "results"}}, {"name": "employees", "endpoint": {"path": "employees/", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="primetric_pipeline", destination="duckdb", dataset_name="primetric_data", ) load_info = pipeline.run(primetric_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("primetric_pipeline").dataset() sessions_df = data.projects.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM primetric_data.projects LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("primetric_pipeline").dataset() data.projects.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 Primetric data to?

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

DestinationExample 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.


Troubleshooting

Authentication failures

If you receive 401 Unauthorized, verify that your OAuth 2.0 token is valid and not expired. Re‑obtain a token from /auth/token/ and ensure the Authorization: Bearer <access_token> header is included.

Rate limiting (429)

Primetric enforces 60 requests per minute. A 429 Too Many Requests response indicates the limit was exceeded; back off and retry after a short delay.

Pagination

List endpoints are paginated with a default page size of 50. Responses contain count, next, previous and a results array. Follow the URL in next to retrieve subsequent pages.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Primetric?

Request dlt skills, commands, AGENT.md files, and AI-native context.