canonical: https://jentic.com/apis/planka.app/planka

# Planka App Planka API

Planka is an open-source Trello-like kanban board. The API provides management of projects, boards, lists, cards, labels, tasks, comments, attachments, and users. The API exposes 45 endpoints secured with bearer authentication.

## For AI agents

Programmatically login and get access token, logout (delete token). Covers 45 operations with bearer authentication.

## Scope

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

## Capabilities

- Login and get access token
- Logout (delete token)
- Create a project
- List all projects
- Get project details
- Update a project
- Delete a project

## Use cases

### Productivity Operations

Use the Planka API to perform productivity operations programmatically. The API provides 45 endpoints covering core functionality including login and get access token, logout (delete token), create a project.

Example prompt: Call POST `/api/access-tokens` to login and get access token

### Automated Auth Management

Automate auth operations by combining multiple Planka API endpoints. Agents can logout (delete token) and then create a project in a single workflow.

Example prompt: Call DELETE `/api/access-tokens` to logout (delete token), then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Planka 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 bearer tokens manually.

Example prompt: Search Jentic for 'login and get access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/access-tokens` | Login and get access token |
| DELETE | `/api/access-tokens` | Logout (delete token) |
| POST | `/api/projects` | Create a project |
| GET | `/api/projects` | List all projects |
| GET | `/api/projects/{projectId}` | Get project details |
| PATCH | `/api/projects/{projectId}` | Update a project |
| DELETE | `/api/projects/{projectId}` | Delete a project |
| POST | `/api/projects/{projectId}/managers` | Add project manager |

## Key resources

- **Auth** — Authentication
- **Projects** — Project management
- **Boards** — Board management
- **Lists** — List management
- **Cards** — Card management

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 57 / 100
- **View full report:** https://jentic.com/apis/planka.app/planka/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 Planka by hand means learning its bearer access-token auth, setting the host for your own Planka instance, and hand-building requests across its project and access-token endpoints yourself. Through Jentic you install once, import Planka from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Planka puts the project id in the URL path (`/api/projects/{projectId}`), so a rule can pin your agent to one project: it reads and updates that project and manages its members and nothing else. You choose the operations it may call, so destructive ones like deleting a project are not included unless you add them.
- **Credential handling:** Your Planka token 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 'log in and get an access token' or 'create a project', and Jentic returns the matching Planka 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 Planka API use?

The Planka API uses a Bearer token in the Authorization 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 login and get access token with the Planka API?

Yes. Use the POST `/api/access-tokens` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Planka 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 login and get access token through Jentic?

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

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

The Planka API exposes 45 endpoints covering auth, projects, boards operations.

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

Yes. Because you run Jentic One yourself, you decide which Planka operations and credentials the agent may use, and your own rules govern every call. Since Planka carries the project id in the URL path (`/api/projects/{projectId}`), you can pin the agent to a single project so it only reads and updates that project and manages its members. You choose the operations it may call, so destructive ones such as deleting a project stay off limits unless you explicitly add them.