Microsoft Clarity

API keyAnalyticsOrg connection

Org-level connection

Microsoft Clarity is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.

Getting your API key

Open your project, then go to Settings → Data Export → Generate new API token

Give the token a name (4–32 characters; letters, numbers, and -_. only — no spaces)

Copy the token — it is shown only once — and paste it below

Limits to be aware of: 10 requests per project per day, only the last 1–3 days of data, response capped at 1,000 rows (no pagination).

Ready to connect?

Permissions (scopes)

These are the data scopes On Belay can be granted for Microsoft Clarity. Your org admin controls which scopes are enabled per group.

Scope	Description	Access
`insights:read`	Read project insights	Read only

Troubleshooting

"Invalid API key" or "Unauthorized" error

Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.

Connected but Claude can't access data

Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.

The key expires or stops working

Some API keys have expiration policies. Generate a new key in Microsoft Clarity and update it in On Belay → Integrations → Microsoft Clarity → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.

Still stuck? We're happy to help.

Contact support →