Skip to main content
Answer

Gong API is not recognising my filters or my cursor and just gives me first page everytime

  • October 4, 2024
  • 4 replies
  • 206 views

Forum|alt.badge.img

I am trying to download all my detailed call records and call transcripts using the Gong API through postman. 

When I use the ‘GET’ function to get the calls, i am able to use the standard process of adding the cursor as a parameter to get the further pages. 

However, when I use the ‘POST’ function to get detailed call reports or transcripts, i enter the cursor into the body and it just returns the first page again every time. 

Ive tried so many workarounds, like using filters to get a date range of call reports or transcripts, but even the filters don’t work! 

It is driving me absolutely crazy! I’ve tried literally everything. 

 

Best answer by Will Knibbs

i managed to fix the workaround by removing the underscores from my filters. 

this allows me to complete the task i was doing, so i’m happy. 

still no idea why the cursor wouldn’t work, but whatever.

4 replies

Forum|alt.badge.img
  • Author
  • Community Newbie
  • Answer
  • October 4, 2024

i managed to fix the workaround by removing the underscores from my filters. 

this allows me to complete the task i was doing, so i’m happy. 

still no idea why the cursor wouldn’t work, but whatever.


Molly Kipnis
Forum|alt.badge.img+2
  • Community Manager
  • October 8, 2024

@Will Knibbs So strange! Thanks for following up here with your solve. Apologies for the difficulties, but glad it works now! 


I am having issues with https://api.gong.io/v2/calls/extensive
It does not use the filter correctly and cursor in the URL returns duplicate cursors randomly.

 

 "filter": {

    "__callIds": "[3105739402913056502]"

  },


PeterBFerrigan

Hi ​@Pradnya Hivale ,

Yes, unfortunately its a known issue. You might try these solutions that have worked for me:

  • When setting filters in the POST body, avoid using field names with underscores (e.g., change "__callIds" to "callIds").

  • Always retrieve and immediately use the cursor value from each response for pagination.

  • If POST-based pagination or filtering fails entirely, try the equivalent GET endpoints, as some users find that cursor-based pagination is more reliable there.

Note: Cursors are short-lived; design your extraction process to handle result pages in quick succession.

​​​​​​​-Peter