Planview Portfolios Python API Docs | dltHub

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

Last updated:

Planview Portfolios is a project portfolio management platform that exposes public REST APIs for data integration and extraction. The REST API base URL is https://{your_account}.pvcloud.com/{your_server}/public-api/v1 and all requests require a Bearer token obtained via OAuth2 client_credentials flow.

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


What data can I load from Planview Portfolios?

Here are some of the endpoints you can load from Planview Portfolios:

ResourceEndpointMethodData selectorDescription
portfolios_metadatametadataGETMetadata for portfolios
project_metadataproject/metadataGETMetadata for project attributes
project_getproject/{id}GETGet single project by id
work_for_projectwork?filter=project.Id%20.eq%20{projectId}GETDataReturns work items for a specific project
odataserviceodataservice/odataservice.svcGETOData feed endpoint for list retrieval

How do I authenticate with the Planview Portfolios API?

All requests to the Planview Portfolios public REST API require an OAuth2 access token passed in the Authorization header using the Bearer scheme. The token must be obtained from the OAuth token endpoint using a client_id and client_secret with the client_credentials grant type.

1. Get your credentials

To obtain credentials for the Planview Portfolios REST API: 1. Log in to your Planview instance as an administrator. 2. Navigate to the main menu and select Administration > Users and Roles (or Users) > OAuth clients (or OAuth2 credentials). 3. Click Create to add a new OAuth client. 4. Note the generated Client ID and Client Secret. Note: The Client Secret is typically displayed only once upon creation, so ensure you store it securely. You may also need your Tenant ID or organization instance URL.

2. Add them to .dlt/secrets.toml

[sources.planview_portfolios_source] client_id = "your_client_id_here" client_secret = "your_client_secret_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 Planview Portfolios 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 planview_portfolios_pipeline.py

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

Pipeline planview_portfolios_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset planview_portfolios_data The duckdb destination used duckdb:/planview_portfolios.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 oauth/token and work from the Planview Portfolios 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 planview_portfolios_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{your_account}.pvcloud.com/{your_server}/public-api/v1", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "work_for_project", "endpoint": {"path": "work?filter=project.Id%20.eq%20{projectId}", "data_selector": "Data"}}, {"name": "odataservice_workdimension", "endpoint": {"path": "odataservice/odataservice.svc/WorkDimension"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="planview_portfolios_pipeline", destination="duckdb", dataset_name="planview_portfolios_data", ) load_info = pipeline.run(planview_portfolios_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("planview_portfolios_pipeline").dataset() sessions_df = data.work_for_project.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM planview_portfolios_data.work_for_project LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("planview_portfolios_pipeline").dataset() data.work_for_project.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 Planview Portfolios 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.


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 Planview Portfolios?

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

Available Pipelines