Gamma 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.
In Gamma, go to Settings → API Keys
Click "Create API key" — the key is shown only once, copy it immediately
Paste it below
Note: Requires a Pro, Ultra, Teams, or Business plan. API generations consume credits from your Gamma account.
Ready to connect?
Go directly to the integrations page in your dashboard.
These are the data scopes On Belay can be granted for Gamma. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
presentations:read | Read presentations | Read only |
presentations:create | Create presentations | Read / Write |
themes:read | Read themes | Read only |
folders:read | Read folders | Read only |
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.
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.
Some API keys have expiration policies. Generate a new key in Gamma and update it in On Belay → Integrations → Gamma → 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 →