Signature Request Problems

Diagnose signature request failures by validating the request body, headers and identifiers.

Checklist

1. mode

   Confirm mode is present and uses a valid value. The documented example uses email.

2. message

   Confirm message is present.

3. templates

   Confirm templates is an array with at least one template request.

4. Each template_id

   Verify each template_id exists for your account via List Templates.

5. Each signer name and email

   Confirm every signer has both name and email.

6. JSON syntax

   Validate the request body is well-formed JSON with the documented field names.

7. Authorization

   Confirm the Authorization: Bearer <BEARER_TOKEN> header is correct.

8. Content-Type

   Set Content-Type: application/json on requests with a body.

9. Idempotency-Key

   Include an Idempotency-Key header for create operations.

If a create may have succeeded but the response was lost

When a create request times out or the response is lost, the request may still have been created. In that case:

1. Do not immediately create another request

   Creating again could duplicate the signature request.

2. Inspect logs

   Check your server logs for the request and any response headers that arrived.

3. Reuse the same idempotency key

   For the same logical retry, send the identical request with the same Idempotency-Key. See Idempotency.

4. Retrieve status when the identifier is known

   If you have the request identifier, check its status before creating again.

Related