> For the complete documentation index, see [llms.txt](https://docs.zapsign.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zapsign.com.br/zapsign-api/english/status-code.md).

# 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

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:

| Code | Reference         | Explanation                                                                                                                                                                                                       |
| ---- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 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 [Access Token](/zapsign-api/english/authentication/jwt-authentication/get-access-token.md) 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 [click here.](https://zapsign.co/pricing) |
| 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.                                                                                                                                  |
|      |                   |                                                                                                                                                                                                                   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zapsign.com.br/zapsign-api/english/status-code.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.