Status Code
ZapSign uses standard HTTP status codes. 4xx errors occur when there is an issue with the request sent by the client to ZapSign, while 5xx errors indicate potential server problems
Last updated
Was this helpful?
ZapSign uses standard HTTP status codes. 4xx errors occur when there is an issue with the request sent by the client to ZapSign, while 5xx errors indicate potential server problems
Last updated
Was this helpful?
Our application always returns a 200 status code for successful responses. Below, we outline the common errors that may occur and how to address them:
400
BAD REQUEST
ZapSign processes all requests in JSON, so formatting errors such as missing commas, malformed base64, etc., can cause this error.
401
UNAUTHORIZED
The server did not authorize the request. Your may be incorrect.
402
PAYMENT REQUIRED
The client does not have an API plan. In the production environment, it is mandatory to have a monthly plan to use the API. Navigate to Settings > Plans and Pricing or
403
FORBIDDEN
The server did not authorize the request. Check if the API token used corresponds to the environment you want to use.
404
NOT FOUND
The server could not find the resource or is unwilling to disclose its existence. Check the URL used or the template ID if you are using Templates.
406
NOT ACCEPTABLE
Check if you are sending your request in JSON format. Remember to verify strings and booleans throughout the body
429
TOO MANY REQUESTS
The client has exceeded the allowed request limit within a specific time period.