Breeze

Delete a comment via DELETE /projects/{project_id}/cards/{card_id}/comments/{comment_id}.json. Delete a comment from a card. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Delete a card via DELETE /projects/{project_id}/cards/{card_id}.json. Delete a card with its comments, todo lists and todos. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Delete a time entry via DELETE /projects/{project_id}/cards/{card_id}/time_entry/{time_entry_id}.json. Remove one logged time entry from a card. The project's tracked total changes with it. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Delete a todo list via DELETE /projects/{project_id}/cards/{card_id}/todo_lists/{todo_list_id}.json. Delete a todo list and every todo in it. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Delete a todo via DELETE /projects/{project_id}/cards/{card_id}/todos/{todo_id}.json. Delete one todo. NOTE THE PATH: the delete is addressed under the CARD, not under the todo list -- the opposite of the update, and both were measured that way. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Delete a project via DELETE /projects/{project_id}.json. Delete a project and everything under it -- stages, cards, comments, todo lists and todos. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Remove a person from a project via DELETE /projects/{project_id}/people/{user_id}.json. Remove one person's access to a project. REMOVING THE LAST MEMBER ORPHANS THE PROJECT AND NOTHING CAN RECOVER IT THROUGH THIS API -- measured: the project then disappears from the project list, its own read answers 404, and its DELETE answers 404, so it can be neither used nor cleaned up. Check the people list first and never remove the final member. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Delete a stage via DELETE /projects/{project_id}/stages/{stage_id}.json. Delete a stage from a project. Cards sitting in it go with it. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Delete a swimlane via DELETE /projects/{project_id}/swimlanes/{swimlane_id}.json. Delete a swimlane from a project. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Delete a workspace via DELETE /workspaces/{workspace_id}.json. Delete a workspace. DESTRUCTIVE AND NOT REVERSIBLE THROUGH THIS API: Breeze publishes no undelete endpoint, so absence is confirmed by re-reading the COLLECTION rather than by a 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List one user's activity via GET /activities/{user_id}.json. The audit log filtered to one user, across every project. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List activity across all projects via GET /activities.json. The account's audit log. 50 entries per page; `message` carries Breeze's own HTML. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List cards across all projects via GET /cards.json. Every card the connected user can see, across every project, as a flat array. Paginated. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Show the connected Breeze user via GET /me.json. Who this connection authenticates as, and -- the field that matters for a multi-team account -- the `team_id` to configure on the connection. THE API TOKEN IS STRIPPED FROM THIS REPLY: Breeze echoes the caller's own credential back in `authentication_token`, and Agentic Fabriq replaces it before the result is returned. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List notifications via GET /notifications.json. The connected user's Breeze notifications. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List one user's activity in a project via GET /projects/{project_id}/activities/{user_id}.json. The audit log for one project, filtered to one user. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a project's activity via GET /projects/{project_id}/activities.json. The audit log for one project. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Archive a project via GET /projects/{project_id}/archive.json. Archive a project: it leaves the active project list and its work is hidden from the boards. THIS IS A WRITE BEHIND A GET -- Breeze mounts it as a GET, so it is NOT safe to retry idly or to call while exploring. Reversible with the reactivate tool. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a card's activity via GET /projects/{project_id}/cards/{card_id}/activities.json. The audit log for one card. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a card's comments via GET /projects/{project_id}/cards/{card_id}/comments.json. A card's comments. The LIST shape differs from the create/update shape: it nests `project`, `card` and `user` objects instead of the bare `user_id`/`card_id` a write returns. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Show a card via GET /projects/{project_id}/cards/{card_id}.json. One card with its tags, todo lists, time entries, attachments and custom fields. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a card's time entries via GET /projects/{project_id}/cards/{card_id}/time_entry.json. The time logged against one card. NOTE THE SINGULAR PATH SEGMENT -- `time_entry`, not `time_entries`. The research concluded this resource had no endpoint at all; it tried eight plural spellings and the singular is the one Breeze serves. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a todo list's todos via GET /projects/{project_id}/cards/{card_id}/todo_lists/{todo_list_id}/todos.json. The todos in one todo list. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a card's todo lists via GET /projects/{project_id}/cards/{card_id}/todo_lists.json. A card's todo lists, each carrying its own todos. THE ONLY WAY TO READ A CARD'S TODOS in one call. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a project's cards by stage via GET /projects/{project_id}/cards.json. A project's board: an array of STAGES, each carrying its own cards. This is NOT a flat card list -- read `cards` inside each stage. A project id Breeze cannot resolve answers 200 with an empty array rather than 404. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a project's custom fields via GET /projects/{project_id}/custom_fields.json. The custom fields defined on a project. Read these before setting `custom_fields` on a card. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Show a project via GET /projects/{project_id}.json. One project by id, with its budget, members and tags. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a project's people via GET /projects/{project_id}/people.json. The people on a project. This is the endpoint Breeze's own documentation names; the `users` path answers the same shape. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Reactivate an archived project via GET /projects/{project_id}/reactivate.json. Bring an archived project back to the active list. THIS IS A WRITE BEHIND A GET, like its archive counterpart. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a stage's cards via GET /projects/{project_id}/stages/{stage_id}/cards.json. The cards in one board column, as a flat array. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a project's stages via GET /projects/{project_id}/stages.json. A project's stages -- the board columns Breeze's documentation calls "lists". Read stage ids here before creating or moving a card. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a swimlane's cards via GET /projects/{project_id}/swimlanes/{swimlane_id}/cards.json. The cards in one swimlane, as a flat array. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a project's swimlanes via GET /projects/{project_id}/swimlanes.json. A project's swimlanes -- the horizontal bands that cross the stage columns. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a project's members via GET /projects/{project_id}/users.json. The people assigned to one project. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List projects via GET /projects.json. Every project the connected user can see, each with its budget, tags and member list. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List running timers via GET /running_timers.json. Every timer running right now across the team, each with the card and project it is on. A running entry carries `started` (epoch milliseconds); a completed one does not. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List team members via GET /teams.json. Breeze's team endpoint. MEASURED, IT RETURNS PEOPLE RATHER THAN TEAMS: on this account its reply is byte-identical to the user list. Prefer the connected-user tool's `team_id` if what you need is a team identifier. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List users via GET /users.json. The people on the account, with their roles. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List cards across all projects (v2) via GET /v2/cards.json. Every card across every project as a FLAT array -- the v2 shape, which is what to prefer over the stage-grouped v1 board when you want cards rather than columns. Paginated 100 per page. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List a project's cards (v2, flat) via GET /v2/projects/{project_id}/cards.json. One project's cards as a FLAT array rather than grouped by stage. Prefer this over the v1 board when you want the cards themselves. Paginated 100 per page. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Show a workspace via GET /workspaces/{workspace_id}.json. One workspace with the projects inside it -- the only place the membership is listed, since the workspace COLLECTION carries no `projects` array. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

List workspaces via GET /workspaces.json. The account's workspaces -- the folders projects are grouped into. A project's `workspace_id` names one. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Comment on a card via POST /projects/{project_id}/cards/{card_id}/comments.json. Add a comment to a card. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Move a card to another stage via POST /projects/{project_id}/cards/{card_id}/move.json. Move a card between stages. `stage_id` is the destination; `prev_id` is the card it should sit after (0 for the top). Breeze's own docs note that the PUT form documented elsewhere is an error and this is the endpoint to use. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Log time on a card via POST /projects/{project_id}/cards/{card_id}/time_entry.json. Log time against a card. The entry is attributed to THE CONNECTED USER and to no one else -- Breeze's own documentation says so and there is no field to name another person. `tracked` is MINUTES. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Create a todo list on a card via POST /projects/{project_id}/cards/{card_id}/todo_lists.json. Create a todo list (a checklist) on a card. A todo cannot exist without one, so this is the first call when adding todos to a card that has none. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Add a todo to a card via POST /projects/{project_id}/cards/{card_id}/todos.json. Add a todo. `todo_list_id` IS REQUIRED and names the list it joins: measured, a body without it answers 404 even though the route exists. Create a todo list first if the card has none. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Create a card via POST /projects/{project_id}/cards.json. Create a card in a project. It lands in the project's first stage unless `stage_id` names another. `tags` is an array of strings. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Invite people to a project via POST /projects/{project_id}/people.json. Add people to a project by email address. THIS SENDS BREEZE INVITATION EMAIL to every address that is not already a member, and it may consume a seat on the plan. Returns the project's member list. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Create a stage via POST /projects/{project_id}/stages.json. Add a stage (board column) to a project. It is appended after the existing stages. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Create a swimlane via POST /projects/{project_id}/swimlanes.json. Add a swimlane to a project. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Create a project via POST /projects.json. Create a project. Breeze seeds a new project with three stages -- Todo, Doing, Done -- which is why a create is immediately followed by a stage list rather than a stage create. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Generate a time-tracking report via POST /reports.json. A time-tracking report over a date range, optionally narrowed by project, user, stage and tag. `start_date` also accepts the relative words last_month, last_week, yesterday, today, this_week and this_month. It READS: nothing is created or changed, despite the POST. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Create a workspace via POST /workspaces.json. Create a workspace to group projects into. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Edit a comment via PUT /projects/{project_id}/cards/{card_id}/comments/{comment_id}.json. Replace a comment's text. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Update a card via PUT /projects/{project_id}/cards/{card_id}.json. Change a card's fields. TAGS ARE OVERWRITTEN, NOT APPENDED -- Breeze's own documentation says so and it was measured: sending ["gamma"] over a card tagged ["alpha","beta"] leaves exactly one tag. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Update a time entry via PUT /projects/{project_id}/cards/{card_id}/time_entry/{time_entry_id}.json. Change a logged time entry. Breeze updates it for the CONNECTED USER only. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Rename a todo list via PUT /projects/{project_id}/cards/{card_id}/todo_lists/{todo_list_id}.json. Change a todo list's name. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Update a todo via PUT /projects/{project_id}/cards/{card_id}/todo_lists/{todo_list_id}/todos/{todo_id}.json. Change a todo's text or tick it off. THE PATH MUST GO THROUGH THE TODO LIST: measured, the shorter `/cards/{card_id}/todos/{todo_id}.json` form answers 404 on PUT even though its DELETE works. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Update a project via PUT /projects/{project_id}.json. Change a project's name or description. Fields that are omitted keep their value. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Rename a stage via PUT /projects/{project_id}/stages/{stage_id}.json. Change a stage's name. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Reorder a stage via PUT /projects/{project_id}/stages/{stage_id}/move.json. Move a board column so it sits after another one. `prev_id` is the stage it should follow, and it must be a DIFFERENT stage: measured, naming the moved stage as its own predecessor answers 500. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Rename a swimlane via PUT /projects/{project_id}/swimlanes/{swimlane_id}.json. Change a swimlane's name. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.

Rename a workspace via PUT /workspaces/{workspace_id}.json. Change a workspace's name. The connection's Breeze API token is attached server-side as the `api_token` query parameter and never appears in this tool's arguments. Breeze routes before it authenticates, and its two 404s mean different things: `{"status":404,"error":"Not Found"}` is no such route, while `{"error":"404 Not found"}` is a route that exists and a record it could not resolve.