PATCH /api/database/tokens/{token_id}/

Updates the existing database token if it is owned by the authorized user and ifthe user has access to the related workspace.

Servers

Path parameters

Name Type Required Description
token_id Integer Yes

Updates the database token related to the provided value.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
name String No

The human readable name of the database token for the user.

rotate_key Boolean No

Indicates if a new key must be generated.

Default value: false

permissions Object No

Indicates per operation which permissions the database token has within the whole workspace. If the value of for example create is true, then the token can create rows in all tables related to the workspace. If a list is provided with for example [["table", 1]] then the token only has create permissions for the table with id 1. Same goes for if a database references is provided. [['database', 1]] means create permissions for all tables in the database with id 1.

Example:

{
  "create": true// Allows creating rows in all tables.
  // Allows reading rows from database 1 and table 10.
  "read": [["database", 1], ["table", 10]],
  "update": false  // Denies updating rows in all tables.
  "delete": []  // Denies deleting rows in all tables.
 }
permissions.create No
permissions.delete No
permissions.read No
permissions.update No

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.