Breeze API

Name: Breeze API 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.

Quickstart

Get started with Breeze API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a kanban card"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Breeze API 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

Comment on cards via POST /projects/{project_id}/cards/{card_id}/comments.json and edit or delete previous comments

GET STARTED

Start building with Breeze API API

Explore with Jentic

View OpenAPI Document

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. Teams use the API to mirror the UI's workflow: create projects, add people, push cards through stages, log comments and todos against a card, and track time. Activity, notifications, and reports endpoints support standups, weekly reviews, and external dashboards. Authentication is HTTP Basic, either with a Breeze username and password or with an API token used as the basic-auth username.

Use Cases

Patterns agents use Breeze API 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 though Jentic?

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

Credential isolation

Breeze HTTP Basic credentials (api token or username/password) are stored encrypted in the Jentic vault and attached to the Authorization header at execution time. Agents call card and project operations by intent without ever holding the raw token in prompt context.

Intent-based discovery

Agents search Jentic for intents like 'create a kanban card' or 'move a card to done' and Jentic returns the matching Breeze operation (POST /projects/{project_id}/cards.json, POST /projects/{project_id}/cards/{id}/move.json) with input schemas typed.

Time to first call

Direct Breeze integration: 1-2 days to wire 61 endpoints across projects, cards, stages, comments, and time entries. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Breezy HR API

Create Breeze cards for new-hire onboarding tasks fired from Breezy HR pipeline events

Use Breezy HR when the agent needs to track candidates and hires; use Breeze to spawn the resulting onboarding kanban tasks.

Complementary

Braze Endpoints

Trigger Braze customer messages when a Breeze card moves into the 'Delivered' stage

Use Braze when the agent needs to notify customers; use Breeze to detect the workflow transition that triggered the notification.

Complementary

Brandfolder API

Attach approved Brandfolder assets to Breeze cards for creative review workflows

Use Brandfolder when the agent needs to fetch the approved asset; use Breeze to track its review and approval as a card.

FAQs

Specific to using Breeze API 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.