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

# Planzer.io API

The Planzer.io API reads and creates tasks in a Planzer account and notifies your endpoint when tasks are created or completed. A new task takes a title plus optional notes, a planned date, a deadline, an estimate in minutes, a priority from none to urgent, and a project and tag; leaving the date out puts it in the inbox. Tasks can be listed newest first with status, sort, and title search filters, fetched one at a time, and marked complete. The same API backs Planzer's Zapier and Make integrations, and each personal API key reaches only the tasks of the account that created it.

## For AI agents

Create, search, and complete tasks in Planzer.io with dates, deadlines, estimates, priorities, projects, and tags, and subscribe a webhook to task.created or task.completed events.

## Scope

Does not handle calendar events, team assignment, or time tracking. Use for creating, searching, and completing personal Planzer tasks only.

## Capabilities

- Create a task with a title, notes, planned date, deadline, estimate_minutes, priority, project_id, and tag_id, or drop it into the inbox by leaving the date out
- List tasks newest first, filtered by open or completed status and by text in the title, with up to 100 per page
- Mark a task complete by its taskId and read back its completed_at timestamp
- Look up the active projects and tags to file new tasks under the right ones
- Subscribe a target_url to task.created or task.completed events, and unsubscribe it by webhookId
- Read the account the API key belongs to, including its timezone, which Planzer uses to interpret dates

## Use cases

### Agent-Driven Task Capture via Jentic

An AI assistant that reads email or meeting notes turns action items into Planzer tasks. Through Jentic it looks up the right project and tag, creates each task with a title, deadline, priority, and estimate, and leaves undated items in the inbox for later planning, so action items land in the planner instead of a chat log.

Example prompt: List projects to find the id of 'Client Work', then create a task titled 'Send Q3 report to Acme' with deadline 2026-11-20, priority high, estimate_minutes 45, and that project_id

### Daily Review of Open Work

Someone planning their day asks for what is still open. The listTasks operation returns tasks newest first with status set to open, and the search parameter narrows by title text, so an assistant can surface everything mentioning a client or project before the day starts and complete finished items in the same session.

Example prompt: List open tasks with search 'Acme' and limit 50, then complete the task titled 'Book kickoff call' with completeTask

### Syncing Completed Tasks to Other Tools

Teams that log finished work elsewhere subscribe a webhook to task.completed. Planzer posts to the target_url whenever a task is completed, so a time tracker, CRM note, or status report can be updated without polling, and the subscription is removed with a single unsubscribe call when it is no longer needed.

Example prompt: Create a webhook for event task.completed with target_url https://hooks.example.com/planzer, then confirm it by completing a test task

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/tasks` | Create a task |
| GET | `/tasks` | List and search tasks |
| GET | `/tasks/{taskId}` | Get a task |
| POST | `/tasks/{taskId}/complete` | Complete a task |
| GET | `/projects` | List active projects |
| POST | `/webhooks` | Subscribe to a task event |
| DELETE | `/webhooks/{webhookId}` | Unsubscribe a webhook |

## Key resources

- **Tasks** — Create, list, search, fetch, and complete tasks with dates, deadlines, estimates, priorities, projects, and tags.
- **Projects** — List the account's active projects.
- **Tags** — List the account's tags.
- **Webhooks** — Subscribe a target URL to task.created or task.completed, and unsubscribe it.
- **Me** — Read the account behind the API key, including name, email, and timezone.

## 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:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 60 / 100
- **View full report:** https://jentic.com/apis/planzer.io/planzer/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 Planzer.io by hand means creating a personal pk_ key, sending it as a bearer token, handling the 429 Retry-After limit, and running a receiver for webhook events. Through Jentic you install once, import Planzer.io from the API Directory, store the key once, and your agent manages tasks.
- **Permission scoping:** Planzer.io puts the task id in the URL path (`/tasks/{taskId}/complete`), so a rule can pin your agent to completing one task. You choose the operations it may call, so webhook creation and deletion are not included unless you add them.
- **Credential handling:** Your Planzer.io 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 'add a task to my planner' or 'complete a task', and Jentic returns the matching Planzer.io operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Asana manages team projects with assignees and workflows; Planzer.io is a personal day planner for one account's tasks.
- **ClickUp** — ClickUp covers tasks, docs, and goals across workspaces; Planzer.io keeps to tasks, projects, tags, and two webhook events.
- **Calendly** — Calendly books meetings; Planzer.io holds the follow-up tasks those meetings create.
- **Trello** — Trello organises cards on boards and lists; Planzer.io organises tasks by planned day, deadline, and priority.

## FAQ

### What authentication does the Planzer.io API use?

The Planzer.io API uses bearer authentication per its OpenAPI spec: create a personal API key in Planzer under Settings, Integrations, API keys and send it as Authorization: Bearer pk_... A key gives access to the tasks of the account that created it. Through Jentic the key is stored encrypted on your own instance and injected at call time.

### Is there a Planzer.io MCP server?

You don't need an MCP server to give your agent Planzer.io. Jentic connects it directly from the API Directory: import Planzer.io, store your API key once, and your agent can create and complete tasks straight away. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

### Can I limit what my agent is allowed to do with the Planzer.io API?

Yes. Write a rule that allows only listTasks, getTask, and createTask, so the agent can read and add tasks but cannot complete them or register and delete webhooks, and every call it makes is logged.

### What are the rate limits for the Planzer.io API?

Per the Planzer.io OpenAPI spec, requests are limited to 120 per minute per API key, or per IP address for requests without a valid key. Over the limit the API returns 429 with a Retry-After header.

### How does the Planzer.io API interpret task dates?

The date field takes YYYY-MM-DD, the word today, or an ISO date-time, and is read as a day in the account's time zone, which you can check with the getMe operation. Leaving the date out puts the task in the inbox. The deadline field accepts YYYY-MM-DD or an ISO date-time in the same way.

### How do I create a task with the Planzer.io API through Jentic?

Search Jentic for an intent like 'add a task to my planner', import Planzer.io, and store your API key once. Your agent then calls createTask at /tasks with a title and optional date, deadline, priority, and project_id. To run it on your own infrastructure, install Jentic One from its GitHub repo.