Bearer Token

Setup
Reference

What You'll Need

Credential	What it is
Personal Access Token	Long-lived token minted from Figma account settings

Overview

Connect Parable to Figma using a Personal Access Token (PAT) sent as a Bearer credential. Parable ingests design assets, version history, team structure, and (Enterprise, opt-in) activity logs.

Design assets

Projects, files, components, variables, and version history

Activity & admin

File comments and org-level activity logs (Enterprise, opt-in)

Prerequisites

Service account required. PATs are tied to the minting user — if that user is removed from the team the token is revoked immediately and ingestion stops. Always mint from a dedicated service-account user on a paid plan (Professional, Organization, or Enterprise).

activity_logs is disabled by default. Enable it only if your organization is on the Enterprise plan with the service-account user having org admin access. Non-Enterprise tenants will receive 402 payment_required on every sync.

Setup Guide

Open Figma Security settings

Sign in to Figma as the dedicated service-account user.
Click your avatar in the top-right and open Settings.
Switch to the Security tab.
Scroll to Personal access tokens.

Generate the token

Click Generate new token.
Set:
- Token name — something traceable, e.g. parable-platform-prod.
- Expiration — choose the longest duration your security policy allows (30 days, 60 days, 90 days, 180 days, or No expiration). Rotate at least every 12 months even if using no expiration.
- Scopes — add the following:

Scope	Purpose
`file_metadata:read`	Projects and files
`file_variables:read`	Design variables
`file_dev_resources:read`	Dev resources
`file_comments:read`	File comments and reactions
`library_assets:read`	Published library assets
`library_content:read`	Library content
`team_library_content:read`	Team-scoped library content
`org:activity_log_read`	Org activity logs (Enterprise only)

Copy the token.

Copy your now!This is the only time it will be displayed. Store it in a secure password manager before closing this page.

Enter values in the form

Personal Access Token: Paste the token from Figma.
Click Save & test connection.

Verify Your Setup

Use an environment variable so the secret never enters shell history:

read -rs -p "Figma PAT: " FIGMA_PAT && echo
curl --silent -H "Authorization: Bearer ${FIGMA_PAT}" https://api.figma.com/v1/me
unset FIGMA_PAT

Success! If you received a 200 OK response with valid data, your credentials are configured correctly. You can now proceed to configure this connector in Parable.

A successful response returns a JSON object with id, email, and handle for the minting user. If you receive 403 Invalid token, regenerate the token in Figma and retry.

Rate Limits: enforces rate limits of .Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

Troubleshooting

Error	Meaning	Solution
`403 Invalid token`	Bad PAT, or PAT was revoked	Re-mint from Figma Settings → Security; confirm minting user is still active
`403 Invalid scope`	PAT missing a required scope	Re-mint with the full scope list above
`404 Not found` on a file or team	Minting user lacks access	Add service-account user to the team, or remove the missing resource
`429 Too many requests`	Rate limit exceeded	Parable respects `Retry-After` and backs off automatically
`Activity logs return empty`	Tap is disabled by default	Enable the `activity_logs` tap in connector settings; requires Enterprise plan and org admin access

Common Issues

Token works in curl but the connector reports invalid

Confirm you copied the full token string — Figma PATs are 40+ characters and may contain hyphens. Trailing whitespace from a paste also fails; re-paste into the connector form.

`activity_logs` returns 402 / `payment_required`

Activity logs are an Enterprise-only feature and are disabled by default. Enable the activity_logs tap only on Enterprise plans with org admin access.

Release Notes

Connectors

What You'll Need

Overview

Design assets

Activity & admin

Prerequisites

Setup Guide

Verify Your Setup

Troubleshooting

Token works in curl but the connector reports invalid

`activity_logs` returns 402 / `payment_required`

Additional Resources

Figma REST API

Personal access tokens

What You'll Need

​Overview

Design assets

Activity & admin

​Prerequisites

​Setup Guide

​Verify Your Setup

​Troubleshooting

​Token works in curl but the connector reports invalid

​activity_logs returns 402 / payment_required

​Additional Resources

Figma REST API

Personal access tokens

Overview

Prerequisites

Setup Guide

Verify Your Setup

Troubleshooting

Token works in curl but the connector reports invalid

`activity_logs` returns 402 / `payment_required`

Additional Resources