Accept an invitation as its verified email recipient
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
Path Parameters
Response Body
curl -X POST "https://example.com/data-room/invitations/497f6eca-6276-4993-bfeb-53cbbbba6f08"crm_vocabulary_set POST
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
Read what a share link for a circle would show, before creating one GET
Answers a member who could share the circle with exactly the categories and documents its link would show. canDownload=1 previews a link that allows original downloads, when the member could create one. Signed URLs expire after one minute.