Deals

Set the org member who owns a deal, or pass owner_id=null to leave it unassigned. The user must already be a member of this organization.

Parameters

Example

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

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

Create a deal on a pipeline board. Only a title is required: without pipeline_id it lands on the org's default pipeline, and without stage_id it goes in that pipeline's first stage. The status is derived from the stage — creating straight into a won/lost stage closes the deal.

Parameters

Example

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

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

Permanently delete a deal. DESTRUCTIVE: its activity timeline (notes, stage changes) is deleted with it, and any task pointing at it loses the link. The contact and company survive. Cannot be undone.

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/deals.delete \
  -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 deals_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one deal by id, with all of its fields including custom fields.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/deals.get \
  -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 deals_get at https://app.chirply.io/api/mcp, same bearer token, same input.

Attach a deal to a contact and/or a company so it shows on that record, or pass null to unlink. Supply at least one of contact_id or company_id; both must belong to this organization.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/deals.link \
  -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 deals_link at https://app.chirply.io/api/mcp, same bearer token, same input.

List and search deals, newest first. Filter by pipeline, stage, status, owner, contact, or company, by who holds a Team member field ("deals where I'm the Designer": member_field=designer, member=me), and search deal titles with `query`. Values come back as integer cents.

Parameters

Example

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

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

Close a deal as abandoned (walked away, not a loss) and stamp its close time. No stage carries an 'abandoned' flag, so the deal keeps its current column but stops counting as open.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/deals.mark_abandoned \
  -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 deals_mark_abandoned at https://app.chirply.io/api/mcp, same bearer token, same input.

Close a deal as lost and stamp its close time. If the pipeline has a stage flagged as lost, the deal is moved into that column and a stage-change entry is logged.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/deals.mark_lost \
  -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 deals_mark_lost at https://app.chirply.io/api/mcp, same bearer token, same input.

Close a deal as won and stamp its close time. If the pipeline has a stage flagged as won, the deal is moved into that column and a stage-change entry is logged, exactly as dragging it there would.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/deals.mark_won \
  -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 deals_mark_won at https://app.chirply.io/api/mcp, same bearer token, same input.

Drop a deal card into a stage of its own pipeline — the drag gesture on the board. Without `position` it lands at the bottom of the target column; with one it lands at that slot and the rest of the column shifts down. Moving to a new stage re-derives the deal's status from that stage's outcome (won/lost stages close the deal and stamp closed_at) and logs a stage-change entry on the deal's timeline. Passing the stage the deal is already in just reorders it inside that column — no status change, no timeline entry.

Parameters

Example

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

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

Put a closed deal (won, lost, or abandoned) back to open and clear its close time. Pass stage_id to also move it back into a working column — otherwise it stays where it is, which may be a won/lost column.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/deals.reopen \
  -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 deals_reopen at https://app.chirply.io/api/mcp, same bearer token, same input.

Update any field on a deal — title, value, currency, expected close date, links, custom fields, stage, or status. Omitted fields are left alone. Moving it with stage_id re-derives the status from that stage; passing status explicitly wins and stamps or clears closed_at accordingly. Changing the stage also writes one stage-change entry on the deal's timeline and the account Activity Log, recording the previous and new stage and naming the caller honestly — an API key is recorded as the API, not as a person.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/deals.update \
  -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 deals_update at https://app.chirply.io/api/mcp, same bearer token, same input.