Basic Auth

Setup
Reference

What You'll Need

Credential	What it is
Access Key	Workspace API access key from Gong
Access Key Secret	Secret shown once when the key is created
API Base URL	Gong API host (`https://api.gong.io` or your regional URL from Company Settings)

Overview

Connect Parable to Gong for calls, CRM, meetings, and workspace analytics using HTTP Basic authentication with a workspace-scoped Access Key and Secret.

Conversations & CRM

Call recordings, transcripts, CRM associations, meetings

People & workspace

Users, workspaces, scorecards, trackers, audit logs

Prerequisites

Setup access in . These steps require , or a colleague with equivalent permissions who can create credentials for you.If that is not you, ask your administrator.

Your Gong API Base URL. Most workspaces use https://api.gong.io. Regional endpoints (for example https://us-12345.api.gong.io) appear under Company Settings → Ecosystem → API.

Gong API keys are workspace-scoped. They can expire; Gong notifies workspace admins before rotation.

Setup Guide

Open Gong API settings

Sign in to Gong as a Technical Administrator.
Open Company Settings → Ecosystem → API (or go to app.gong.io/company/api).

Enable required API scopes

Each API key in Gong has scopes toggled individually. Enable only the scopes for the data categories you want Parable to collect.

Scope	Purpose
`api:calls:read:basic`	Call recordings
`api:calls:read:extensive`	Call details & AI insights
`api:calls:read:transcript`	Call transcripts
`api:users:read`	Users & settings history
`api:settings:scorecards:read`	Scorecard definitions
`api:stats:scorecards`	Scorecard responses
`api:settings:trackers:read`	Tracker definitions
`api:workspaces:read`	Workspaces & library folders
`api:logs:read`	Audit logs
`api:crm-calls:manual-association:read`	CRM call associations
`api:stats:user-actions:detailed`	Daily user activity
`api:stats:interaction`	Interaction statistics
`api:stats:user-actions`	Activity aggregates
`api:crm:get-objects`	CRM entities (Accounts, Contacts, Deals)
`api:meetings:integration:status`	Meetings
`api:permission-profile:read`	Permission profiles
`api:crm:integrations:read`	CRM integrations

api:permission-profile:read may need to be enabled by Gong Support on some tiers.

Create API credentials

Click Get API Key.
Copy the Access Key and Access Key Secret. The secret is shown once — store it in a password manager before closing the page.

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

Access Key, Access Key Secret, and API Base URL: Enter the values from Gong (use your regional base URL if applicable).
Click Save & test connection.

Scopes Quick Reference

Scope	Purpose
`api:calls:read:basic`	Call recordings
`api:calls:read:extensive`	Call details & AI insights
`api:calls:read:transcript`	Call transcripts
`api:users:read`	Users & settings history
`api:settings:scorecards:read`	Scorecard definitions
`api:stats:scorecards`	Scorecard responses
`api:settings:trackers:read`	Tracker definitions
`api:workspaces:read`	Workspaces & library folders
`api:logs:read`	Audit logs
`api:crm-calls:manual-association:read`	CRM call associations
`api:stats:user-actions:detailed`	Daily user activity
`api:stats:interaction`	Interaction statistics
`api:stats:user-actions`	Activity aggregates
`api:crm:get-objects`	CRM entities (Accounts, Contacts, Deals)
`api:meetings:integration:status`	Meetings
`api:permission-profile:read`	Permission profiles
`api:crm:integrations:read`	CRM integrations

Verify Your Setup

Use environment variables so secrets do not appear in shell history:

read -rs -p "Access Key: " GONG_KEY && echo
read -rs -p "Access Key Secret: " GONG_SECRET && echo
read -p "API Base URL [https://api.gong.io]: " GONG_BASE_URL
GONG_BASE_URL="${GONG_BASE_URL:-https://api.gong.io}"
curl --silent --user "${GONG_KEY}:${GONG_SECRET}" \
  "${GONG_BASE_URL}/v2/workspaces"
unset GONG_KEY GONG_SECRET GONG_BASE_URL

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 includes requestId, records, and a workspaces array. Prefer curl --netrc-file over curl -u "KEY:SECRET" for one-liners so credentials are not written to shell history.

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
`401 Unauthorized`	Bad Access Key or Secret	Re-generate the key from the API settings page
`401` after a working period	Key expired	Generate a fresh key; Gong rotates keys periodically
`403 Forbidden` on a specific endpoint	Missing API scope	Ask the Gong admin to enable the scope for that data category
`429 Too Many Requests`	Rate limit	Parable backs off using `Retry-After`
Empty data on `calls`	No calls in range	Calls need `fromDateTime` in the last 90 days per request

Common Issues

Cannot find the API page

The Ecosystem → API menu appears only for users with the Technical Administrator role.

Permission Profiles returns 401 / 403

Requires api:permission-profile:read on the key. Some tiers need Gong support to enable the scope.

Release Notes

Connectors

What You'll Need

Overview

Conversations & CRM

People & workspace

Prerequisites

Setup Guide

Scopes Quick Reference

Verify Your Setup

Troubleshooting

Cannot find the API page

Permission Profiles returns 401 / 403

Additional Resources

Gong API docs

API access guide

What You'll Need

​Overview

Conversations & CRM

People & workspace

​Prerequisites

​Setup Guide

​Scopes Quick Reference

​Verify Your Setup

​Troubleshooting

​Cannot find the API page

​Permission Profiles returns 401 / 403

​Additional Resources

Gong API docs

API access guide

Overview

Prerequisites

Setup Guide

Scopes Quick Reference

Verify Your Setup

Troubleshooting

Cannot find the API page

Permission Profiles returns 401 / 403

Additional Resources