To generate and manage authentication tokens, follow the steps below using the wolkvox Manager interface.

How to Create a Token

To create a new token, you must access the integrations settings within wolkvox Manager.

1. Log in to wolkvox Manager.
   1. Click the Configuration icon (gear), located in the top-right menu of the application.
2. In the "Configuration" pop-up window, navigate to and select the main Integrations tab.
3. Within this section, click on the Tokens sub-tab.
4. In the Token Description field, enter a clear name or description to help you identify the token's purpose (e.g., "Sales CRM Integration"). This field is mandatory.
5. Click the Add token button.
6. The new token will immediately be listed in the table below, showing the token itself, its description, today's usage count, and the total consumption limit.

Managing Existing Tokens

Once the tokens are created and listed in the table, you can easily manage them. Right-click on a specific token in the list to display the following options:

• Copy Token: Copies the alphanumeric token value to your clipboard. This is the recommended way to avoid transcription errors.
• Delete: Permanently deletes the selected token. This action cannot be undone.
• Refresh: Updates the list of tokens in the table. This is useful if you don't see a newly created token or want to update the usage counters.

How to Use the wolkvox-token

To authenticate your API requests, you must send the generated token as a header in your HTTP request as follows:

• Header Name: wolkvox-token
• Header Value: [The token you copied from wolkvox Manager]

Important Consideration: Server Maintenance

It's important to note that during maintenance processes, such as server backups, API consumption is temporarily disabled to ensure data integrity.

If you try to consume an API during this interval, you will receive the following response with a 403 Forbidden status code:

{
  "code": "403",
  "error": "Forbidden",
  "msg": "The APIs cannot be consumed at this time, try again later."
}

This is a controlled and expected response. Your application should be prepared to handle this scenario and retry the request later.