ZapSign API
Batch sign via API
Batch sign via API


"user_token": "23d4d2d5-8998-4516-b2f8-6045c4eabc9d", //user token (who is signing)
"3c8f16f8-949b-432a-adea-d1e544bb91be", //signer token of 1st document
"fed91ab3-bb69-46f9-8c2d-9594772b1186" //signer token of 2nd document


{"message":"Documento(s) assinado(s) com sucesso. Lembrete: este endpoint é assíncrono, então aguarde os PDF finais ficarem prontos via webhooks ou confira-os daqui alguns minutos."}

Where do I find the user_token?

Log into the user who will sign the documents and enter their profile:
User profile.
At the bottom of the page, enable signing via API and copy the token.

How to get signer_tokens?

Every signer created at ZapSign has a token. Just copy this ZapSign-generated token after a document is created or after you add a signer. (Please note: it is not the document's token, but the signer's token!)
Note: if you only want to sign one document at a time, just insert an array with only one signer token. E.g.: signer_tokens: ["123-abc-456-def"]

404 errors

If you try to make a request with user_token or signer_tokens that don't exist, you will receive a 404 (not found) response. If this happens, make sure you are actually using the signer's token instead of the document's token, and that you're not reversing with the user_token, etc.

Asynchronous Endpoint

This endpoint is asynchronous, thus, you will request for documents to be signed and you will receive an almost immediate response from ZapSign. As the documents are ready, you will receive the webhooks in your application one at a time. Avoid signing more than 100 documents at once to avoid delays. Make more than one request if appropriate.