If your Gong meetings suddenly stopped importing into Spekit, and Spekit Support has told you the connection is returning a "429 rate limit exceeded" error, the cause sits inside your Gong workspace, not inside Spekit. This article explains what the error means, how to find what is using your Gong API quota, and how to get imports flowing again.
This article is for Gong Technical Admins and Spekit Account Admins. If you are a rep who just wants your calls back, send this to your admin.
What a 429 error actually means
Gong caps API usage at 10,000 requests per day across your entire workspace. Every tool you connect to Gong shares that ceiling. It is not allocated per integration.
When something in your workspace uses up the 10,000 requests, Gong rejects all further calls with a 429 error. This lasts until the limit resets. Spekit's meeting import is one of the things that gets rejected, so imports pause until the quota resets or the tool using it is slowed down.
Why this is not Spekit
Spekit makes a small number of Gong API calls per account. This is typically around 100 requests per day against the 10,000 request limit. There are no background processes on our side pulling extra data.
We check this first on every 429 report. If our usage were the problem, we would tell you.
✅ What that means for you: the quota is being used by another integration in your Gong workspace, or by a custom script someone built against the Gong API. Finding it is the fix.
Step 1: Audit your Gong Access Keys and integrations
Your Gong Technical Admin needs to do this part. In Gong, open:
- Company Settings > Ecosystem > API
- Company Settings > Ecosystem > Integrations
Look for two things:
- Multiple Access Keys. Each Access Key usually means a different tool is connected. If you see keys you do not recognize, or keys left over from a tool you stopped using, those are your first suspects.
- Data-heavy integrations. Anything that tries to sync every meeting at once will use up the quota fast. Common examples:
- BI tools (Tableau, Power BI)
- Sales engagement platforms (Salesloft, Outreach)
- Data warehouses (Snowflake, BigQuery)
✅ Resolution: if you spot an obvious culprit, go to Step 3.
Step 2: Ask your Gong CSM for a usage report
Gong does not give customers a self-serve API usage dashboard. If nothing obvious turns up in Step 1, your CSM or account manager can pull the numbers for you.
Email your Gong representative something like:
"Can you provide a report of our API consumption by Access Key for the last 14 days? We are hitting 429 rate limit errors and need to identify which integration is driving the volume."
The report tells you which Access Key is responsible. From there you can trace it back to the tool.
Step 3: Fix the quota
Once you know what is using the requests, you have two options:
- Dial the offender down. Reduce its sync frequency, narrow its scope, or disable the Access Key if the tool is no longer in use.
- Ask Gong to raise your daily ceiling. Your CSM can tell you whether a higher limit is available on your plan.
Either option gets meeting imports flowing again from Gong into Spekit. Imports resume on their own once the 429 errors stop. There is nothing to reconnect on the Spekit side.
💡 Pro Tip: if you are adding a new integration to Gong, ask the vendor how many API calls it makes per day before you turn it on. A single tool set to full historical sync can use up a 10,000 request ceiling in an afternoon.