Skip to main content

Manage secret keys of workspace

Rate limits

This endpoint does not belong to the priority lane. Do not use it within your ticket sales flow.

The secret key of a workspace should be kept secret at all times. If it does get compromised, you can rotate it to a new one. To ensure a smooth transition to the new key, the recommended procedure is

  1. Add a new key
  2. Update anywhere the old key is used with the new key
  3. Delete the old key

Adding a secret key

POST https://api-{region}.seatsio.net/workspaces/{key}/actions/add-secret-key
  • key: the key of the workspace
curl -X POST https://api-{region}.seatsio.net/workspaces/18725661-36d6-4755-905a-28ce82d0c2d5/actions/add-secret-key \
-u anAdminKey: -X POST

Response

{
secretKey: "79425661-36d6-4755-905a-28ce82d0c8c1"
}

Removing a secret key

POST https://api-{region}.seatsio.net/workspaces/{key}/actions/remove-secret-key

Request

{
"secretKey": "The secret key to remove"
}
  • key: the key of the workspace
curl -X POST https://api-{region}.seatsio.net/workspaces/18725661-36d6-4755-905a-28ce82d0c2d5/actions/remove-secret-key \
-u anAdminKey: -X POST -H 'Content-Type: application/json' -d '{"secretKey": "0E2814A1-053C-451D-8C3F-2B7C8D490BB7"}'

Response

{
secretKey: "79425661-36d6-4755-905a-28ce82d0c8c1"
}