Upload Signature

This endpoint allows an enterprise user to upload a signature image file, which will be associated with their account for use in document signing workflows.

HTTP Method and URL

POST {{host}}/client/signature?user_type=ENTERPRISE_API

Authentication Requirements

Requires a valid user-token to be provided as a variable or header for authentication.

Query Parameters

• user_type (string, required): Must be set to ENTERPRISE_API.

Request Body

Content-Type: multipart/form-data

• file (file, required): The signature image file to upload (e.g., PNG).

• source (string, optional): Example value: Draw.

• uuid (string, optional): Example value: p3WjzWLMCDmYiO3.

• type (string, optional): Example value: SIGNATURE.

Example Request

curl -X POST "{{host}}/client/signature?user_type=ENTERPRISE_API" \
  -H "Authorization: Bearer <user-token>" \
  -F "file=@/path/to/signature.png" \
  -F "source=Draw" \
  -F "uuid=p3WjzWLMCDmYiO3" \
  -F "type=SIGNATURE"

Example Successful Response

{
  "status": "success",
  "message": "Signature uploaded successfully.",
  "signature_id": "abc123xyz"
}

Error Responses

• 401 Unauthorized – Authentication failed or missing token.

• 422 Unprocessable Entity – Required fields are missing or invalid.

Usage Notes

• Ensure the file parameter contains a valid image file (PNG recommended).

• The user-token variable must be set in your environment or passed as a header.

• Refer to saved examples for error response payloads.