Dealboard

The Dealboard API. Built for humans and AI agents.

Read and write deals, listen for events, and connect Dealboard to AI tools. Use the REST API, signed webhooks, OpenAPI spec, or MCP server depending on what you're building.

v1 API note (May 2026 release): thestagefield on deal responses is now an object instead of a string. The same applies tofrom_stageandto_stageon webhook payloads. Update integrations accordingly — see the examples below for the new shape.

# Your first call — list deals curl "https://app.getdealboard.com/v1/deals" \ -H "Authorization: Bearer $DEALBOARD_API_KEY" # Response { "data": [ { "id": "deal_8f3a...", "company": "Acme Inc.", "amountCents": 4800000, "currency": "USD", "stage": { "id": "stg_abc123", "name": "Proposal Sent", "region": "anchor", "isAnchor": true }, "ownerName": "Alex Chen" } ], "next_cursor": null }

Dealboard separates raw inbound interest from your sales pipeline, so each gets the right UI and the right schema. They connect via one explicit promote call.

Created when someone submits your website form, your hosted contact page, or emails your inbound address. Holds the submitter's contact info, their message, and any enrichment your qualifier writes. Lives in the Leads inbox until you triage it.

newcontactedpromotedjunkbad_fitstale

Has a stage, owner, amount, notes, attached proposals, contracts, and an activity feed. Moves through your board's pipeline regions (early → anchor → late → won/dead). This is what shows up in Reports.

Connecting the two. Promote a Lead withPOST /v1/leads/{lead_id}/promote. The Lead row sticks around withtriage_status: "promoted"and adeal_idpointing at the new Deal — you keep the full inbound provenance forever, and the call is idempotent so replays return the existing deal id without creating a second one.