canonical: https://jentic.com/apis/mindburp.se/mindburp

# Mindburp Se mindburp API

Jentic publishes the only available OpenAPI specification for mindburp API, keeping it validated and agent-ready. mindburp is a personal task tool whose 'burps' are individual tasks; the API exists to drive Zapier integrations, so it offers webhook subscribe and unsubscribe endpoints, a perform-list lookup that Zapier uses to populate triggers, an endpoint to enumerate burp ids, and an actions endpoint that runs a chosen Zapier-style action against a burp. Authentication is by bearer token.

## For AI agents

Subscribe to and unsubscribe from mindburp burp (task) webhooks, list burp ids, and perform Zapier-style actions on burps via bearer authentication.

## Scope

Does not handle direct burp creation, calendar scheduling, or note-taking - use for Zapier-style webhook subscriptions, burp id lookup, and action execution against existing burps only.

## Capabilities

- Subscribe to a webhook so external systems are notified when a burp event occurs
- Unsubscribe a previously registered webhook to stop receiving burp events
- Retrieve the perform list - the set of triggers a Zapier-style integration can drive
- Enumerate every burp id the authenticated user owns to feed downstream automations
- Run a v1 action against a burp to update or process it from an external trigger

## Use cases

### Zapier-Style Webhook Integration

External automations register a callback URL with mindburp to receive events when burps change, then unregister the URL when the integration is removed. The two webhook endpoints together provide the lifecycle that any Zapier or Make integration needs.

Example prompt: POST `/api/zapier/wh-subscribe` with the callback URL when the integration starts, and DELETE `/api/zapier/wh-unsubscribe` when the user removes it.

### Burp Id Enumeration for Triggers

When a Zapier-style trigger is configured, mindburp's perform list and burp-id list endpoints supply the data needed to populate dropdowns and run polling-based triggers. The id list is the source of truth for which burps an automation can target.

Example prompt: Call GET `/api/zapier/performlist` to fetch supported triggers, then GET `/api/zapier/getAllMyBurpIds` to populate a burp-selection dropdown.

### Action Execution From an External Trigger

When an external event fires (calendar, email, IoT, agent decision), an integration calls mindburp's actions endpoint to update the matching burp. mindburp stays in sync with the user's wider workflow without manual edits in the app.

Example prompt: POST `/api/zapier/v1/actions` with the burp id and the action key returned from the perform list to update the burp.

### Agent Task Management via Jentic

Through Jentic, an agent connects to mindburp with bearer auth held in the vault and triggers webhook setup or actions by intent. The agent can maintain Zapier-style integrations on the user's behalf without ever holding the bearer token directly.

Example prompt: Use Jentic search 'subscribe to a mindburp webhook', load the schema for POST `/api/zapier/wh-subscribe`, and execute with the agent's callback URL.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/zapier/wh-subscribe` | Subscribe to a webhook |
| DELETE | `/api/zapier/wh-unsubscribe` | Unsubscribe from a webhook |
| GET | `/api/zapier/performlist` | Get the Zapier perform list |
| GET | `/api/zapier/getAllMyBurpIds` | Get all burp ids for the authenticated user |
| POST | `/api/zapier/v1/actions` | Perform an action on a burp |

## Key resources

- **Webhooks (Zapier)** — Subscribe and unsubscribe webhook callbacks for burp events
- **Perform List** — Enumerate the actions a Zapier-style integration supports
- **Burps** — List the burp ids owned by the authenticated user
- **Actions** — Perform v1 actions on a burp

## Why Jentic

- **Setup:** Wiring mindburp by hand means handling its bearer auth against app.mindburp.se and coding the Zapier-style webhook subscribe, unsubscribe, and action calls yourself. Through Jentic you install once, import mindburp from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** mindburp's webhook and action endpoints carry their target in the request body rather than a URL path resource, so scope the agent to the operations it needs, such as listing burp ids or subscribing to a webhook. You choose which operations are allowed, so unsubscribing a webhook is only included if you add it.
- **Credential handling:** Your mindburp bearer token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'subscribe to a mindburp webhook' or 'list my burp ids', and Jentic returns the matching mindburp operation with its input schema so the agent calls POST `/api/zapier/wh-subscribe` without parsing docs.mindburp.se.

## Related APIs

- **Asana API** — Full task and project management API with native CRUD on tasks.
- **Trello API** — Card-and-board task tracker with rich webhook support.
- **ClickUp API** — Project management platform that can mirror mindburp burps into a shared workspace.

## FAQ

### Why is there no official OpenAPI spec for mindburp API?

mindburp does not publish an OpenAPI specification at docs.mindburp.se. Jentic generates and maintains this spec so that AI agents and developers can call mindburp API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the mindburp API use?

The API uses bearer token authentication (the BearerAuth security scheme). Generate a token in the mindburp app and pass it as Authorization: Bearer <token>. Through Jentic, the token sits in the encrypted vault and is injected per request without entering the agent's context.

### Can I subscribe to webhook events for new burps?

Yes. POST `/api/zapier/wh-subscribe` registers a callback URL that mindburp will call when burp events occur, and DELETE `/api/zapier/wh-unsubscribe` removes the registration. This is the supported pattern for Zapier-style integrations.

### What are the rate limits for the mindburp API?

mindburp does not publish public rate limits in the spec. Treat the API as rate-limited per token, back off on HTTP 429 responses, and contact mindburp support via docs.mindburp.se for details on integration tiers.

### How do I run an action on a burp through Jentic?

Run pip install jentic, search for 'perform a mindburp action', load the schema for POST `/api/zapier/v1/actions`, and execute with the burp id and action key. Jentic injects your stored bearer token automatically.

### Can I create a new burp via this API?

Not directly. The published surface is built around the Zapier integration pattern: webhook subscribe/unsubscribe, perform list, burp id enumeration, and actions. Burp creation happens inside the mindburp app or via configured action keys returned by the perform list.

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

Yes. Because you run Jentic One yourself, your own rules decide which of mindburp's operations the agent may call, such as listing burp ids or subscribing to a webhook, while leaving others out. Since the webhook and action endpoints carry their target in the request body rather than a URL path, you scope access at the operation level, so an agent that only needs GET `/api/zapier/getAllMyBurpIds` never gains DELETE `/api/zapier/wh-unsubscribe.` Your stored bearer token is injected per request without entering the agent's context, so the agent acts only within the operations you allow.