post_v1_crm_opportunities
CreateOpportunity adds a deal to the caller's org and answers 201 with the stored record.
CreateOpportunity adds a deal to the caller's org and answers 201 with the stored record. A name is required; the stage defaults to NEW; companyId and pointOfContactId must name records in the same org.
| Tool | post_v1_crm_opportunities |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 8 |
| Operation | POST /v1/crm/opportunities |
| Product | crm |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
amount | integer | — | — | — | Amount is the deal value in minor units (cents) of Currency. |
closeDate | integer | — | — | — | CloseDate is the expected close, as a unix second (0 = unset). |
companyId | string | — | — | — | CompanyID links the deal to one of the org's companies. |
currency | string | — | — | — | Currency is the ISO code Amount is denominated in; empty defaults to USD. |
id | string | — | — | — | ID names the opportunity to update and comes from the path. A create ignores it: the server mints the id. |
name | string | — | — | — | Name is the deal name. Required. |
pointOfContactId | string | — | — | — | PointOfContact links the deal to one of the org's contacts. |
stage | string | — | — | — | Stage is the pipeline stage: NEW, SCREENING, MEETING, PROPOSAL or CUSTOMER (case-insensitive). Empty defaults to NEW. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "post_v1_crm_opportunities",
"arguments": {
"amount": 0,
"closeDate": 0,
"companyId": "<companyId>",
"currency": "<currency>",
"id": "<id>",
"name": "<name>",
"pointOfContactId": "<pointOfContactId>",
"stage": "<stage>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. amount and closeDate hold stand-ins that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so those values are this page's, not the API's. Neither the door nor the operation declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
post_v1_crm_opportunities | POST /v1/crm/opportunities | crm | Adds a deal to the caller's org and answers 201 with the stored record. |
The same capability over plain HTTP is in the crm API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?