crm_vocabulary_set
Set the CRM vocabulary: the organization types and pipelines this company runs its CRM in. Both lists are written at once, so read crm_vocabulary_get first and send it back with what changes. The stages are the product’s and are not set here. This is an administrator’s. `workspace_write` · v1
Authorization
memberToken The tools internkim uses inside a company, callable from outside it. A token belongs to a person, and every call runs as that person, so a token can never do more than its owner can.
The first token is made signed in, from the settings screen. After that a token makes its own
successors: POST /token for a new one, DELETE /token for the old one, so a script rotates
without a browser. A token can neither mint a rung above its own nor revoke itself.
Send Authorization: Bearer <token> on every request.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
curl -X POST "https://example.com/tools/crm_vocabulary_set/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": { "organizationTypes": [], "pipelines": [] } }'{ "toolName": "crm_vocabulary_set", "outcome": "succeeded", "selectedBackend": "device", "effects": [ { "objectType": "crm", "effect": "created", "id": "7a93de11-…" } ], "result": { "…": "the tool's own document" }}crm_vocabulary_get POST
The CRM vocabulary, the words this company runs its CRM in: the organization types it sorts relationships by, the pipelines it runs deals through, and the stages a deal can stand at with what each one means. `read` · v1
Accept an invitation as its verified email recipient POST
Next Page