Workspace Token

Workspace tokens provide access to workspace-specific resources via the Webflow Data API.

These tokens are useful for workspace administrators that need access to workspace-level information and audit logs. For access to site data, use a site token instead.

Scopes and endpoints

Create workspace tokens with the following scopes and endpoints.

Workspace tokens use separate scopes and resources than site tokens. For example, workspace tokens don’t have access to the site scope, therefore they can’t access site-specific endpoints like Get Site Information. To ensure you’re using the correct token for your use case, please refer to the scopes and resources documentation.

Creating a workspace token

1. In the left sidebar of your Workspace, select Apps & integrations > Manage. Scroll to the bottom of the page to the Workspace API access section.

   

2. Click “Generate API token”.

3. Enter a name for your API token.

4. Choose the permissions you want the API token to have for each scope. (e.g., no access or read-only).

   

5. Click Generate token.

6. Copy the generated token to your clipboard and save it in a secure location.

Limitations

• Enterprise only. Workspace tokens are only available for Enterprise workspaces.
• API tokens expire after 365 consecutive days of inactivity. Any API call made with the token before expiry will reset the inactivity period.
• Each workspace can have up to 5 tokens. This limit ensures manageable token access and security.
• Limited endpoints. Workspace tokens are designed with different scopes than site tokens. For example, workspace tokens don’t have access to the site scope, therefore they can’t be used to access site-specific endpoints. Please refer to the scopes documentation for more information.

Using a workspace token

Now that you have your workspace token, you can start making requests to the Webflow Data APIs that require a workspace token.

$
curl --request GET \
>
  --url https://api.webflow.com/v2/workspaces/:workspace_id_or_slug/audit_logs \
>
  --header 'accept: application/json' \
>
  --header 'authorization: Bearer YOUR_API_TOKEN'

Example API response

Here’s an example of what a response from the Webflow API might look like:

1
  {
2
  "items": [
3
      {
4
      "eventType": "user_access",
5
      "eventSubType": "login",
6
      "payload": {
7
          "method": "dashboard",
8
          "location": "Ashburn US",
9
          "ipAddress": "54.165.18.93"
10
      }
11
      },
12
      {
13
      "eventType": "user_access",
14
      "eventSubType": "login",
15
      "payload": {
16
          "method": "sso"
17
      }
18
      },
19
      {
20
      "eventType": "user_access",
21
      "eventSubType": "login",
22
      "payload": {
23
          "method": "dashboard"
24
      }
25
      }
26
  ],
27
  "pagination": {
28
      "limit": 10,
29
      "offset": 0,
30
      "total": 3
31
  }
32
  }

Best practices

• Mint tokens for each use case: Instead of reusing tokens, generate a new token for each specific use case to maintain better security and control.
• Rotate tokens periodically: Regularly update and revoke old tokens to maintain security.
• Be Descriptive: Name your tokens something descriptive and meaningful to easily identify their purpose.
• Minimal Scopes: Generate tokens with the minimal scopes needed for your use case. Mint a new one if you need to add new scopes. This limits the potential impact if a token is compromised.

Revoking a workspace token

To revoke a workspace token:

1. In the left sidebar of your Workspace, select Apps & integrations > Manage. Scroll to the bottom of the page to the Workspace API access section.
2. Find your workspace token
3. Click the “Revoke” button

Revoking a site token is an additional security measure for your Webflow site. This process disables the token, preventing any further access or use. You should consider revoking a site token in the following situations:

• Security Concerns: If there’s a potential security issue, revoke the token immediately.
• Administrator Changes: If an administrator leaves or their role changes, revoke their token to maintain security.
• Token Management: Regularly review and revoke tokens that are no longer needed.

Troubleshooting and FAQs