Endpoint
Authentication
This endpoint requires authentication via API key. Include your API key in theX-API-Key header:
Path Parameters
Request Body
The request body must be a JSON object with the following fields:Required Fields
Attribute Object
Each object in theattributes array contains:
Request Example
Response
Success Response
Status Code:200 OK
Response Fields
Error Responses
401 Unauthorized
Returned when authentication fails. See the authentication errors section for details.404 Not Found
Returned when the specified file does not exist or is not accessible with your API key.422 Validation Error
Returned when the request body is invalid or contains unsupported attribute types.500 Internal Server Error
Returned when the attribute update fails due to a server error.Notes
This endpoint uses a merge strategy: attributes you provide are added or overwritten, while attributes not included in the request are left unchanged. To remove an attribute entirely, contact support.
Use Cases
This endpoint is useful for:- Post-upload enrichment - Add or correct metadata after a document has been processed
- Bulk attribute updates - Programmatically update attributes across many documents via automation
- Workflow integration - Update document metadata as part of a downstream workflow (e.g., after review or signing)
- Data correction - Fix incorrect attribute values without re-uploading the document