Support

Add a public comment to a feature request and email its author. Only requests on a board this account is on can be commented on; anything else reports as not found. Set internal=true (platform admins only) for a note nobody else sees.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.comment_on_feature \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "body": "example"
  }'

Over MCP the same operation is the tool support_comment_on_feature at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently delete a bug report, its whole thread, and its uploaded screenshots. Only the person who filed it, or the platform team, can do this.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.delete_bug_report \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_delete_bug_report at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently delete one comment from a feature request, along with anything attached to it. Only its author, or the platform team, can do this.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.delete_feature_comment \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_delete_feature_comment at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently delete a feature request, its comments, its votes, and its attachments. Only the person who posted it, or the platform team, can do this.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.delete_feature_request \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_delete_feature_request at https://app.chirply.io/api/mcp, same bearer token, same input.

Raise a client's bug report with Chirply as a genuine platform fault. This opens a SEPARATE ticket between this agency and Chirply, quoting what the client wrote, and Chirply's team answers the agency on it. The client is not told, is never contacted by Chirply, and sees nothing change on their own ticket — the agency stays the only company they deal with. When Chirply finishes, an internal note lands back on the client's ticket and the agency's support desk is emailed — the client's report is NOT closed for them, because only the agency may tell their own customer anything. One escalation per client ticket; asking twice is refused. Refuses any ticket that is not on this agency's desk.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.escalate_client_report \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "report_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_escalate_client_report at https://app.chirply.io/api/mcp, same bearer token, same input.

File a support report on behalf of the signed-in user or the person who created its API credential. Right away, an AI answers whatever current Chirply help guides can answer, in the report's public thread (emailed to the reporter), quoting the guides it relies on: a plain question the guides fully answer is then resolved; anything else it answers in part stays open in the support queue for the team. Anything about money, legal or security, and reports with no question in them, get no automatic answer. The team is emailed either way. Screenshots and screen recordings can only be attached from the app.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.file_bug \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Example",
    "body": "example"
  }'

Over MCP the same operation is the tool support_file_bug at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one bug report with its full reply thread. Account owners and admins may open any report filed by their team; members may open only their own. Internal platform-team notes are included only for platform admins.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.get_bug_report \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_get_bug_report at https://app.chirply.io/api/mcp, same bearer token, same input.

Read one bug report filed by a client of this agency, in full, with every reply on the thread. Internal notes the agency's own staff left are included; the client cannot see those. If the ticket was raised with Chirply, says where that escalation got to — `chirply_answered` means Chirply has finished and the client is still waiting to hear it from the agency. Reads only. Refuses any ticket that is not on this agency's desk.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.get_client_report \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "report_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_get_client_report at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one feature request with its vote count and its comment thread. Only requests on a board this account is on are readable — its own public-board posts, or the private board of the white-label agency it belongs to; anything else reports as not found. Internal platform-team comments are included only for platform admins.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.get_feature_request \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_get_feature_request at https://app.chirply.io/api/mcp, same bearer token, same input.

List bug reports newest first, with reply and attachment counts. Account owners and admins see every report filed by their team; members see only reports they filed. Optionally filter by status, keep only tickets awaiting a reply from the platform team, or search titles and descriptions.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.list_bug_reports \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool support_list_bug_reports at https://app.chirply.io/api/mcp, same bearer token, same input.

List the feature requests this agency's client accounts have posted to the agency's OWN board — what their clients are asking THEM to build, sorted by how many clients voted for it. A white-label agency's clients post here rather than to Chirply's public board, so nobody outside the agency's own accounts can see these. Reads only. Not to be confused with support.list_feature_requests, which is the board this agency posts to as Chirply's customer.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.list_client_ideas \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "status": "open",
    "limit": 50
  }'

Over MCP the same operation is the tool support_list_client_ideas at https://app.chirply.io/api/mcp, same bearer token, same input.

List the bug reports filed by this agency's client accounts — the tickets the agency answers itself, because its clients bought a white-labelled product and have never heard of Chirply. Shows each ticket's title, status, severity, which client account it came from, who is waiting on whom, whether it has already been raised with Chirply, and whether Chirply has since ANSWERED that escalation — `chirply_answered` marks a ticket where the fix is done but the client has still been told nothing, because Chirply never contacts them. Reads only. This is the agency's own desk; it never returns tickets belonging to another agency, or the agency's own tickets with Chirply.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.list_client_reports \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "status": "active",
    "limit": 50
  }'

Over MCP the same operation is the tool support_list_client_reports at https://app.chirply.io/api/mcp, same bearer token, same input.

List the feature-request board this account is on, with vote and comment counts. Which board that is depends on the account: a client of a white-label agency is on that agency's own private board, and everyone else is on the platform-wide public board, which is shared by every account on purpose and carries no customer data — only a poster's display name. A white-label agency can additionally pass board=clients to read the board its own clients post to. Never returns another agency's board.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.list_feature_requests \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "limit": 25,
    "offset": 0
  }'

Over MCP the same operation is the tool support_list_feature_requests at https://app.chirply.io/api/mcp, same bearer token, same input.

Send one of this agency's client ideas up to Chirply as a request for the platform itself. Opens a SEPARATE request on Chirply's public board, authored by this agency, quoting what the client wrote and carrying the number of client accounts that voted for it — that vote count is the argument, so it travels with the request. The client is not told, is never contacted by Chirply, and their own post is unchanged. One promotion per idea; asking twice is refused. Refuses any request that is not on this agency's board.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.promote_client_idea \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "request_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_promote_client_idea at https://app.chirply.io/api/mcp, same bearer token, same input.

Post a reply on a bug report's thread. Account owners and admins may reply to any report filed by their team; members may reply only to their own. A platform admin's public reply emails the reporter; a reporter's reply emails the platform team and, if the ticket was resolved or closed, automatically reopens it. Set internal=true (platform admins only) to leave a note the reporter never sees.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.reply_to_bug \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "body": "example"
  }'

Over MCP the same operation is the tool support_reply_to_bug at https://app.chirply.io/api/mcp, same bearer token, same input.

Post a reply on a client's bug report. A public reply is SENT TO A REAL PERSON — the client who filed it gets an email, branded as this agency, and sees the message in their own account. An internal note is visible only to this agency's staff and is never shown to the client. Refuses any ticket that is not on this agency's desk.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.reply_to_client_report \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "report_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "body": "example"
  }'

Over MCP the same operation is the tool support_reply_to_client_report at https://app.chirply.io/api/mcp, same bearer token, same input.

Post a feature request, and upvote it for its author. Posted on behalf of the signed-in user — or, for an API key, OAuth connection, or installed app, the person who created that credential. If you are an agent and the platform is missing something you need, this is the right way to ask for it — but search support.list_feature_requests first and upvote an existing request instead of posting a duplicate. It lands on whichever board this account posts to — the platform-wide public board, where every user on the platform can see and vote on it, or, for a client of a white-label agency, that agency's own private board. The team that answers that board is emailed.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.request_feature \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Example",
    "body": "example"
  }'

Over MCP the same operation is the tool support_request_feature at https://app.chirply.io/api/mcp, same bearer token, same input.

Change the status and/or severity of a client's bug report on this agency's desk. CHANGING THE STATUS EMAILS THE CLIENT who filed it, branded as this agency — marking something resolved tells a real person their problem is fixed, so do not use it to tidy a queue. Refuses any ticket that is not on this agency's desk.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.set_client_report_status \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "report_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_set_client_report_status at https://app.chirply.io/api/mcp, same bearer token, same input.

Upvote a feature request, or take your vote back. Only requests on a board this account is on can be voted on; anything else reports as not found. Votes are one per person and drive that board's “most wanted” ranking, which is how the team behind it decides what to build next.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/support.vote_feature \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool support_vote_feature at https://app.chirply.io/api/mcp, same bearer token, same input.