Skip to main content
PUT
Update tag

Authorizations

Authorization
string
header
default:App
required

This is the most secure authorization type and the one with the most flexibility.

API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.

You can manage your API keys from GUI, or programmatically with dedicated API.

API key Authorization header example:

Path Parameters

tagId
string<uuid>
required

Unique identifier of the tag.

Body

application/json
name
string
required

New name for the tag.

Minimum string length: 1
Pattern: ^[^,]+$
Example:

"email-api"

Response

Tag updated successfully

id
string<uuid>
required

Unique identifier of the tag.

Example:

"c56a4180-65aa-42ec-a945-5fd21dec0538"