Windsor.ai
API keyData & EnrichmentOrg connection
Org-level connection
Windsor.ai 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
Windsor.ai is provisioned at the platform level — no per-org API key required. Your On Belay administrator enables access and links your organization's Windsor account. Once connected, marketing data from your ad platforms is pulled read-only through On Belay for reporting and AI-visibility fieldsets.
Ready to connect?
Sign in to On Belay and open the Integrations page to add Windsor.ai.
Permissions (scopes)
These are the data scopes On Belay can be granted for Windsor.ai. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
connectors:read | Read marketing/ads performance data across connected platforms | Read only |
accounts:read | Read the list of connected ad accounts (data sources) | 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 Windsor.ai and update it in On Belay → Integrations → Windsor.ai → 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 →