> 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/english/authentication/jwt-authentication/get-access-token.md).

# Get access token

To obtain the Access Token, make a request to the authentication endpoint with your ZapSign user credentials. This endpoint will return both the Access Token and the Refresh Token.

<mark style="color:green;">`POST`</mark> `https://api.zapsign.com.br/api/v1/auth/token/{{`organization\_ID`}}/`

{% hint style="info" %}
You can obtain your organization ID by navigating to **Settings > Integrations > API Token > Organization ID**.
{% endhint %}

```
Request body
{
    "username": "dev@example.com.br",
    "password": "StrongPassword123"
}

```

<figure><img src="/files/0ENoF7YU2NpY2Kcxy7Lw" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="200: OK Authentication successfully completed." %}
{% code overflow="wrap" %}

```json
{
    "refresh": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ0b2tlbl90eXBlIjoicmVmcmVzaCIsImV4cCI6MTcxMDE3ODM0NCwianRpIjoiYjhmZjMwNDJmNjRkNDJmM2FlMzczZmRiNDQ3YTQ2NGEiLCJ1c2Vyb",
    "access": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c"
}
```

{% endcode %}
{% endtab %}

{% tab title="401: Unauthorized Invalid credentials" %}
{% code overflow="wrap" %}

```json
{
    "detail": "No active account found with the given credentials"
}
```

{% endcode %}
{% endtab %}

{% tab title="400: Bad Request Login attempts exceeded." %}

```javascript
{
    "message": "Rate limit exceeded"
}
```

{% endtab %}
{% endtabs %}

After obtaining your Token, you can authenticate to the ZapSign endpoints by including your token in the "Authorization" header of your request, using the prefix "Bearer". Example:

```
  'headers': {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ0b2tlbl90eXBlIjoiYWNjZXNzIiwiZXhwIjoxNzA5ODIwMTQxLCJqdGkiOiIxMGM4YmVhOTkxNDM0ZGU5OWQxNmViMGE2ZTA3MTU1YyIsInVzZXJfaWQiOjEsInR5cGUiOiJwdWJsaWMifQ.GhMKXDyiidHrWCSmU3I9e6-zDm61mBmDqEavir4IW0c'
  },
```

After one hour, you will need to authenticate again. See how to do this in the chapter "[Refresh Your Access Token".](/english/authentication/jwt-authentication/refresh-your-access-token.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zapsign.com.br/english/authentication/jwt-authentication/get-access-token.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.