KnoCommerce

API keyAnalyticsOrg connection

Org-level connection

KnoCommerce 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

API access depends on your Kno Commerce plan. If the steps below show no API Access screen, ask Kno to enable it.

In Kno Commerce, go to Settings → API Access and create an API client.

Copy the Client ID and Client Secret.

Paste them below as "Client ID|Client Secret" (Client ID, a pipe, then Client Secret).

On Belay exchanges those for a short-lived access token on your behalf and refreshes it automatically — there is nothing further to configure.

Ready to connect?

Permissions (scopes)

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

Scope	Description	Access
`SURVEYS`	Read surveys	Read only
`RESPONSES`	Read survey responses	Read only
`QUESTIONS`	Read benchmark questions	Read only
`ATTRIBUTION`	Read attribution analytics	Read only
`WEBHOOKS`	Manage webhook subscriptions	Read / Write

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 KnoCommerce and update it in On Belay → Integrations → KnoCommerce → 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 →