canonical: https://jentic.com/apis/productive.io/productive

# Productive API

Productive.io project management API following JSON:API specification. Provides endpoints for managing projects, tasks, time entries, invoices, deals, contacts, services, bookings, and more. The API exposes 27 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a project, list projects. Covers 27 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a project
- List projects
- Get a project
- Update a project
- Delete a project

## Use cases

### E-Commerce Operations

Use the Productive API to perform e commerce operations programmatically. The API provides 27 endpoints covering core functionality including create a project, list projects, get a project.

Example prompt: Call POST /projects to create a project

### Automated Bookings Management

Automate bookings operations by combining multiple Productive API endpoints. Agents can list projects and then get a project in a single workflow.

Example prompt: Call GET /projects to list projects, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Productive 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 'create a project', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/projects` | Create a project |
| GET | `/projects` | List projects |
| GET | `/projects/{id}` | Get a project |
| PATCH | `/projects/{id}` | Update a project |
| DELETE | `/projects/{id}` | Delete a project |
| POST | `/tasks` | Create a task |
| GET | `/tasks` | List tasks |
| GET | `/tasks/{id}` | Get a task |

## Key resources

- **Bookings** — Operations related to Bookings
- **Companies** — Operations related to Companies
- **Deals** — Operations related to Deals
- **Invoices** — Operations related to Invoices
- **People** — Operations related to People

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/productive.io/productive/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Productive API by hand means setting its API key, targeting api.productive.io/api/v2, and mapping project and task operations yourself. Through Jentic you install once, import Productive from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Productive puts the project and task id in the URL path (`/projects/{id}`, `/tasks/{id}`), so a rule can pin your agent to specific projects and tasks. You choose the operations it may call, so a destructive one like deleting a project is not included unless you add it.
- **Credential handling:** Your Productive API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a project' or 'list open tasks', and Jentic returns the matching Productive operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Productive API use?

The Productive API uses an API key passed in the `X-Auth-Token` 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 create a project with the Productive API?

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

### What are the rate limits for the Productive 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 create a project through Jentic?

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

### How many endpoints does the Productive API have?

The Productive API exposes 27 endpoints covering bookings, companies, deals operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Productive operations the agent may call, so you can grant read-only access like GET /projects and GET /tasks while withholding a destructive call such as DELETE `/projects/{id}` unless you explicitly add it. Since Productive puts the project and task id in the URL path (`/projects/{id}`, `/tasks/{id}`), you can also pin the agent to specific projects or tasks rather than the whole account. Your Productive API key is held by your own instance and injected only for the operations you have allowed.