Create signature

post

https://api.ext-sandbox.fourthline.com/v1/clients/{clientId}/signatures

Use this endpoint to create a signature, including its metadata and the document(s) to be signed.

Important Important: signatureId and workflowId are string identifiers that can be used interchangeably.

Path Params

clientId

string

required

Our unique identifier for the client, returned in the Create workflow response. Whether clientData is required depends on your configuration and integration method. Contact your delivery manager to confirm the fields required for your setup.

Format: uuid string

Example: 790f325a-48c9-4b82-bb53-c0ea128236f0

Body Params

requestData

object

Metadata for the signature flow. Sent as JSON inside multipart/form-data.
Content-Type: application/json

documentsToSign

array of objects

required

List of metadata entries describing each document to be signed. This array is JSON-encoded when sent in multipart/form-data.
Content-Type: application/json

documentsToSign*

files

array of files

required

An array of form data files, one for each document to sign.
Required headers:
Content-Disposition: form-data; name=files; filename=filename.pdf (must match 1 filename in documentsToSign)
Content-Type: application/pdf

Responses

202The signature was created

400The request did not match the specification or a required parameter was missing

404The provided clientId was not found in the system