Token permissions

Introduction

When creating an authentication key/token, you must choose which endpoints it will be able to call. At the time of creating the necessary keys to make requests, in Settings - Integrations, it is important to understand that there are two types of API keys that can be created:

Single-branch key: a key created in the instance of a branch with permissions and access only to data from that branch;

Multi-branch key: a key created in a General Admin instance with access only to calls that have the idbranch parameter.

In Settings - Integrations, access the EVO card in the API section:

Clicking on the EVO card presents the screen:

35b447100af4138bcd855009475bfa9e397898d76b489621a3927523b103aa97-image.png

Alphabetical list of all created integration Tokens.

Search field to look up the Token by name.

NEW TOKEN: button to create new Tokens.

Actions: edit and delete the created Tokens.

History of deleted Tokens.

📘 Read this article to learn how to create a new token.

To view or edit the permissions of an existing token, click on the token name or the "edit" icon.

626c2ea0563f8683202ddd5b57b5fdbfb3f83c4d48cf7bd6315e67f1461b4849-image.png

From there, you can add or remove permissions by clicking the arrow to expand and view the referenced endpoints.

0a353101e2ba575291a069ecc840eb3ca881079d2fd3238097ab6fe62674f9ae-image.png

The selected permissions must be related to the data that the key will be able to access.

Permissions by endpoints

All endpoints available in our API Reference are available for permission configuration.

🚧 Endpoints whose method is GET are used for queries and other methods, such as POST, PATCH, PUT, and DELETE are used for editing.

Introduction#

Permissions by endpoints#

Introduction

Permissions by endpoints