canonical: https://jentic.com/apis/pivotaltracker.com/pivotaltracker

# Pivotal Tracker API

Pivotal Tracker is an agile project management tool. The API provides access to projects, stories, epics, labels, iterations, memberships, and activity. The API exposes 22 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get authenticated user, create a project. Covers 22 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for productivity only.

## Capabilities

- Get authenticated user
- Create a project
- List all projects
- Update a project
- Delete a project

## Use cases

### Productivity Operations

Use the Pivotal Tracker API to perform productivity operations programmatically. The API provides 22 endpoints covering core functionality including get authenticated user, create a project, list all projects.

Example prompt: Call GET /me to get authenticated user

### Automated Account Management

Automate account operations by combining multiple Pivotal Tracker API endpoints. Agents can create a project and then list all projects in a single workflow.

Example prompt: Call POST /projects to create a project, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Pivotal Tracker API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get authenticated user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/me` | Get authenticated user |
| POST | `/projects` | Create a project |
| GET | `/projects` | List all projects |
| GET | `/projects/{projectId}` | Get a project |
| PUT | `/projects/{projectId}` | Update a project |
| DELETE | `/projects/{projectId}` | Delete a project |
| POST | `/projects/{projectId}/stories` | Create a story |
| GET | `/projects/{projectId}/stories` | List stories in project |

## Key resources

- **Account** — Operations related to Account
- **Activity** — Operations related to Activity
- **Epics** — Operations related to Epics
- **Iterations** — Operations related to Iterations
- **Labels** — Operations related to Labels

## Why Jentic

- **Setup:** Wiring Pivotal Tracker by hand means sending its X-TrackerToken header on every call, paging through projects and stories, and handling retries yourself. Through Jentic you install once, import Pivotal Tracker from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Pivotal Tracker puts the project id in the URL path (`/projects/{projectId}/stories`), so a rule can pin your agent to one project and its stories. You choose the operations it may call, so deleting a project is not included unless you add it.
- **Credential handling:** Your Pivotal Tracker token is stored once, encrypted, by your own Jentic One instance and injected as the X-TrackerToken header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a story in a project' or 'list my projects', and Jentic returns the matching Pivotal Tracker operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Pivotal Tracker API use?

The Pivotal Tracker API uses an API key passed in the `X-TrackerToken` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get authenticated user with the Pivotal Tracker API?

Yes. Use the GET /me endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Pivotal Tracker API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get authenticated user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get authenticated user'. Jentic returns the matching Pivotal Tracker API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Pivotal Tracker API have?

The Pivotal Tracker API exposes 22 endpoints covering account, activity, epics operations.

### Can I limit what my agent is allowed to do with the Pivotal Tracker API?

Yes. Because you run Jentic One yourself, your own rules decide which Pivotal Tracker operations and credentials the agent may use. Since the project id sits in the URL path, such as `/projects/{projectId}/stories`, you can pin the agent to a single project and its stories. You also choose which operations it may call, so destructive calls like DELETE `/projects/{projectId}` are excluded unless you explicitly allow them.