Skip to main content
Beta Group

Persistent 502s being returned from Co-pilot API

  • March 9, 2026
  • 2 replies
  • 7 views

Issue

When we make bursts of request to the `call-details` API endpoint we receive a 502. Error: Bad gateway.

 

Background 

As part our companies service, we offer integration with Clari Copilot meeting data.

We make API calls to Copilot on our customer’s behalf and use the returned clari data in our application.

However, a bunch of calls across all our customers have experienced persistent 502 errors returned from Copilot's APIs at some point.

 

* We're calling the `call-details` API endpoint - https://api-doc.copilot.clari.com/#tag/call/paths/~1call-details/get

* We're pulling in all our customers' call details over the last 7 days

* Our call pattern are periods of no calls, then a large number of calls for the last few days of data.

* If this fails we retry every hour

* We often get HTTP Status Code: 502. Error: Bad gateway.

 

We assume the quantity of info we're requesting is causing an issue with our call rate, although we are not hitting our rate limits. We receive no rate limit exception back.

 

What we need from you:

 

* Do you know why we're receiving 502:  Bad gateway - Is this just a throttle exception?

* If so, Why aren't we receiving the usual 4XX code when being throttled?

* Is there anything we can do our side to understand why we are receiving a 502.

2 replies

Forum|alt.badge.img+3
  • New Contributor
  • March 10, 2026

Hi Phoebe!

Question for you -  is the  limit set as 100? As the payload keeps increasing in the calls, we can't always return 100 calls in a batch. Can you reduce the limit to 25 and try again?

For context, there is a limitation enforced on the size of the response payload by AWS. In the current API implementation, we can only return up to 6MBs in the response.  If the size of individual calls increase, our ability to respond with a maximum of 100 calls will diminish. Call size could be related to how many topics the calls were tagged with.


  • Author
  • New Contributor
  • March 11, 2026

Great, thank you for the swift response.

Yes, we were hitting with a limit of 100. I’ve reduced it to 25 as you suggested and haven’t seen any issues so far.

Thanks for your help on this.