Breeze API

Name: Breeze API
Brand: Breeze API
Availability: InStock

✓ Official Vendor SpecProductivityTask Managementbasic61 EndpointsREST

For Agents

Create projects, move cards through kanban stages, post comments, and log time in Breeze project management through 61 REST endpoints behind HTTP Basic auth.

Install Jentic One Beta

Connect the Breeze API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Breeze API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Breeze API.

Create and update projects via POST /projects.json and PUT /projects/{id}.json, with archive/reactivate via /projects/{id}/archive.json and /reactivate.json

Add or remove people on a project via POST /projects/{id}/people.json and DELETE /projects/{id}/people/{user_id}.json

Create cards in a project and move them between stages via POST /projects/{project_id}/cards.json and POST /projects/{project_id}/cards/{id}/move.json

GET STARTED

Start building with Breeze API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Breeze API for, with concrete tasks.

★ Sync external tickets into Breeze cards

Mirror tickets from a support tool or issue tracker as Breeze cards so the engineering team works from a single board. The integration calls POST /projects/{project_id}/cards.json on inbound tickets and POST /projects/{project_id}/cards/{id}/move.json when status changes upstream. Comments stay in sync via POST /projects/{project_id}/cards/{card_id}/comments.json so context is preserved.

On every new support ticket, POST /projects/{project_id}/cards.json with title and description, then on status change POST /projects/{project_id}/cards/{id}/move.json with the matching stage_id.

Time tracking for client billing

Capture time spent on each card and roll it up into invoices. Team members start a timer, the integration lists running timers via GET /running_timers.json, and at end of week pulls per-card and per-user time via GET /projects/{project_id}/cards/{card_id}/time_entry.json. The data feeds an invoicing system without manual time-entry exports.

GET /running_timers.json for an as-of snapshot, then for each project iterate cards and GET /projects/{project_id}/cards/{card_id}/time_entry.json to assemble the weekly billable-hours report.

Project status reports for stakeholders

Produce weekly status updates by reading project activity, card movements, and notifications through the API. GET /projects/{project_id}/activities.json gives a chronological feed; combined with GET /projects/{project_id}/cards.json and stage filtering it becomes the basis for an automated 'what shipped this week' email or Slack post.

GET /projects/{project_id}/activities.json filtered to the last 7 days, group by stage, and send a summary listing cards that moved into the Done stage.

AI agent integration via Jentic

An agent that triages incoming work into a Breeze board can discover the API through Jentic, load the create-card and move-card operations, and execute them without holding the user's Breeze API token in prompt context. Jentic injects HTTP Basic credentials at execution time and returns typed card responses.

Through Jentic, search 'create a kanban card', load the operation that targets POST /projects/{project_id}/cards.json, and execute with project_id, title, and assignee from the inbound request.

Key Endpoints

61 endpoints — breeze is a kanban-style project management tool whose api exposes 61 endpoints across workspaces, projects, cards, stages, swimlanes, todo lists, time entries, comments, and activity feeds.

METHOD

PATH

DESCRIPTION

POST

/projects/{project_id}/cards.json

Create a new card in a project

POST

/projects/{project_id}/cards/{id}/move.json

Move a card to a different stage

GET

/projects/{project_id}/cards.json

List cards in a project

POST

/projects/{project_id}/cards/{card_id}/comments.json

Comment on a card

POST

/projects/{project_id}/cards/{card_id}/time_entry.json

Log a time entry against a card

GET

/running_timers.json

List timers currently running across the workspace

GET

/projects/{project_id}/activities.json

Project activity feed

POST

/projects.json

Create a new project

POST

/projects/{project_id}/cards.json

Create a new card in a project

POST

/projects/{project_id}/cards/{id}/move.json

Move a card to a different stage

GET

/projects/{project_id}/cards.json

List cards in a project

POST

/projects/{project_id}/cards/{card_id}/comments.json

Comment on a card

POST

/projects/{project_id}/cards/{card_id}/time_entry.json

Log a time entry against a card

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Breeze HTTP Basic credentials are stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a kanban card' or 'move a card to done', and Jentic returns the matching Breeze operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Breeze API through Jentic.

What authentication does the Breeze API use?

The API uses HTTP Basic auth - either a Breeze username and password or an API token passed as the basic-auth username with a blank password. Through Jentic, the credentials are stored in the encrypted vault and attached to the Authorization header at execution time.

Can I move a card between kanban stages with the Breeze API?

Yes. POST /projects/{project_id}/cards/{id}/move.json accepts a target stage_id (and optionally swimlane_id and position) and returns the updated card. Use this to mirror status changes from external systems into the Breeze board.

How do I log time against a Breeze card?

POST /projects/{project_id}/cards/{card_id}/time_entry.json with duration and optional notes creates a time entry on the card. GET /running_timers.json shows timers currently in progress across the workspace, useful for end-of-day reconciliation.

What are the rate limits for the Breeze API?

Breeze does not publish numeric rate limits in the OpenAPI spec - quotas are tied to plan tier. For activity feed polling and bulk card operations, throttle client-side and back off on 429 responses against /projects/{project_id}/activities.json or /v2/cards.json.

How do I create a Breeze card with the Breeze API through Jentic?

Install with pip install jentic, then await client.search('create a kanban card'), await client.load on the POST /projects/{project_id}/cards.json operation, and await client.execute with project_id, title, and assignee. Jentic attaches the basic-auth credentials automatically.

Does the Breeze API support comments and todo lists on cards?

Yes. POST /projects/{project_id}/cards/{card_id}/comments.json adds a comment, and the /todo_lists and /todos endpoints under a card create checklists with individual checkable items. Both are versioned per card so progress can be tracked independently of stage moves.

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

Yes. Because you run Jentic One yourself, your own rules decide which Breeze operations and credentials the agent may use, and it can only call what you include. Breeze puts the resource id in the URL path, so you can pin an agent to a single project or card on calls like POST /projects/{project_id}/cards/{id}/move.json and POST /projects/{project_id}/cards/{card_id}/comments.json. Writes such as creating projects or moving cards are only available if you add them, so a reporting agent can be held to reads like GET /projects/{project_id}/activities.json and GET /running_timers.json.

Breeze API

Connect the Breeze API to your agent

Capabilities

Start building with Breeze API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs