Step 2 of the upload. Call POST /v1/contacts/{id}/attachments/upload-url, upload the file with the returned presigned POST, then call this endpoint with the returned key to link the file to the contact. The file size, URL and extension are read from the stored object; a key can be linked only once. The response has the same shape as an item of GET /v1/contacts/{id}/attachments. Attachments created through the API have uploaded_by: null.
Recent Requests
Log in to see full request history
Time
Status
User Agent
Retrieving recent requests…
Loading…
Responses
403
API key is missing the contacts:write scope.
404
Contact not found for this account.
409
The key is already attached, or another upload for this account is in progress (retry shortly). Codes: KEY_ALREADY_ATTACHED, UPLOAD_IN_PROGRESS. For KEY_ALREADY_ATTACHED, details also carries documentId, attachmentId and contactId of the existing attachment, so a client retrying after a lost response can recognise its own earlier success.
422
The file does not fit the account limits. Codes: QUOTA_FILE_TOO_LARGE, QUOTA_STORAGE_EXCEEDED, INVALID_FILE_SIZE.
Updated 14 days ago
Did this page help you?
Yes
No
Language
ShellNodeRubyPHPPython
Loading…
Response
Click Try It! to start a request and see the response here! Or choose an example: