How to test Dropbox Sign API callback errors
In this article
Overlay Error
[any letters and/or numbers]+overlayerror@hellosign.com
Here's an example of an Overlay Error callback - note the "event_type" value is "file_error", as well as the "signatures"->"status_code[0]" value.
This error can occur with all Signer Placement options except the Appended Signatures Page.
Component Error
[any letters and/or numbers]+componenterror@hellosign.com
Here's an example of an Component Position error - note the "event_type" value is 'signature_request_invalid', as well as the "signatures"->"status_code[0]" value. This means the Overlay Error is specific to signer, which may help with troubleshooting your form_fields_per_documents.
Text Tag Error
[any letters and/or numbers]+doctagerror@hellosign.com
Here's an example of a Text Tag Error - note the "event_type" value is "signature_request_invalid", though the value for "signatures"->"status_code[0]" is "error_text_tag".
Recipient Declined
[any letters and/or numbers]+declined@hellosign.com
Here's an example of a Declined event - note the "signatures"->"status_code[0]". Also, for this test the "signatures"->"decline_reason[0]" is null, but the signer would be required to fill in a reason, so you'd typically get a string returned for the "decline_reason".
Unknown Error
[any letters and/or numbers]+unknownerror@hellosign.com
Here's an example of an Unknown Error.
Community answers
-
Posted by: AngieB 37 days ago
63
0
-
Posted by: AngieB 92 days ago
101
0
-
Posted by: Nihad1 812 days ago
1184
2
-
Posted by: Keith B.7 3598 days ago
1590
2
-
Posted by: Keith B.7 3600 days ago
5040
6