{ "aid": "gong.io:main-V2", "name": "Gong API", "type": "Index", "description": "

Overview

\n

\nThe Gong API allows you to:\n

\n
    \n
  1. \nReceive the following information from Gong:\n
      \n
    1. \nYour company's calls in Gong\n
    2. \n
    3. \nYour company's users in Gong\n
    4. \n
    5. \nYour company's user stats in Gong\n
    6. \n
    7. \nYour company's user settings in Gong\n
    8. \n
    9. \nYour company's libraries in Gong\n
    10. \n
  2. \n
  3. \nUpload new or \nupdate \ncall recordings in Gong, in order to support cases where you have an internal system that records \ncalls or obtains them from a third-party entity.\n
  4. \n
  5. \nData Privacy: \nDelete users and all their associated elements.
  6. \n
  7. \nUpload CRM data into Gong. \n
  8. \n
\n

Check here what's your base URL for all API calls.\n

\n

Authentication

\n\n

\nThere are two ways to retrieve credentials to the Gong Public API:\n

\n
  1. Retrieve Manually:
    \n

    \nIn the Gong API Page (you\nmust be a technical administrator in Gong), click \"Create\" to receive an Access Key\n and an Access Key Secret.
    \n

    \n

    \nUse the Basic Authorization HTTP header (as per RFC)\nto access the Public API as shown below:
    \nAuthorization: Basic <token>
    \n

    \n

    \nTo create the basic token, combine the Access Key and the Access Key Secret with \ncolon (:) and then encode in Base64 as following:
    \nBase64(<accessKey> : <accessKeySecret>)

    \n

  2. \n
  3. Retrieve through OAuth
    \n

    \nTo obtain the Bearer token, follow the steps described in the Gong OAuth Guide.\n

    \n

    \nAfter obtaining the token, use the Bearer Authorization HTTP header\n(as per RFC)\nto access the Public API as shown below:
    \nAuthorization: Bearer <token>\n

    \n
\n

Limits

\n\n

\nBy default Gong limits your company's access to the service to 3 API calls per second, and 10,000 API calls per day.\n

\n

\nWhen the rate of API calls exceeds these limits an HTTP status code 429 is returned and a Retry-After header indicates\n how many seconds to wait before making a new request.\n

\nIf required, contact help.gong.io to change these limits.\n

\n\n

Cursors

\n\n

\nSome API calls that return a list are limited in the amount of records they may return, so multiple API calls may be\n required to bring all records. Such an API call also returns a records field, which contains the number of records\n in the current page, the current page number and the total number of records.\n

\n

\nIn cases where the total number of records exceeds the number of records thus far retrieved, the records field will also\n contain a cursor field which can be used to access the next page of records. To retrieve the next page, repeat the API call with\n the cursor value as supplied by the previous API call. All other request inputs should remain the same.\n

\n

Forward Compatibility

\n\n

\nWhen coding a system to accept Gong data, take into account that Gong may, without prior warning, add fields to the JSON output.\n It is recommended to future proof your code so that it disregards all JSON fields you don't actually use.\n\n

", "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/gong.io/main/V2/apis.json", "tags": [ "gong.io", "main" ], "created": "2026-04-10", "modified": "2026-04-10", "specificationVersion": "0.19", "access": "3rd-Party", "maintainers": [ { "FN": "Jentic", "X-github": "jentic", "url": "https://github.com/jentic" } ], "apis": [ { "aid": "gong.io:main-V2", "name": "Gong API", "description": "

Overview

\n

\nThe Gong API allows you to:\n

\n
    \n
  1. \nReceive the following information from Gong:\n
      \n
    1. \nYour company's calls in Gong\n
    2. \n
    3. \nYour company's users in Gong\n
    4. \n
    5. \nYour company's user stats in Gong\n
    6. \n
    7. \nYour company's user settings in Gong\n
    8. \n
    9. \nYour company's libraries in Gong\n
    10. \n
  2. \n
  3. \nUpload new or \nupdate \ncall recordings in Gong, in order to support cases where you have an internal system that records \ncalls or obtains them from a third-party entity.\n
  4. \n
  5. \nData Privacy: \nDelete users and all their associated elements.
  6. \n
  7. \nUpload CRM data into Gong. \n
  8. \n
\n

Check here what's your base URL for all API calls.\n

\n

Authentication

\n\n

\nThere are two ways to retrieve credentials to the Gong Public API:\n

\n
  1. Retrieve Manually:
    \n

    \nIn the Gong API Page (you\nmust be a technical administrator in Gong), click \"Create\" to receive an Access Key\n and an Access Key Secret.
    \n

    \n

    \nUse the Basic Authorization HTTP header (as per RFC)\nto access the Public API as shown below:
    \nAuthorization: Basic <token>
    \n

    \n

    \nTo create the basic token, combine the Access Key and the Access Key Secret with \ncolon (:) and then encode in Base64 as following:
    \nBase64(<accessKey> : <accessKeySecret>)

    \n

  2. \n
  3. Retrieve through OAuth
    \n

    \nTo obtain the Bearer token, follow the steps described in the Gong OAuth Guide.\n

    \n

    \nAfter obtaining the token, use the Bearer Authorization HTTP header\n(as per RFC)\nto access the Public API as shown below:
    \nAuthorization: Bearer <token>\n

    \n
\n

Limits

\n\n

\nBy default Gong limits your company's access to the service to 3 API calls per second, and 10,000 API calls per day.\n

\n

\nWhen the rate of API calls exceeds these limits an HTTP status code 429 is returned and a Retry-After header indicates\n how many seconds to wait before making a new request.\n

\nIf required, contact help.gong.io to change these limits.\n

\n\n

Cursors

\n\n

\nSome API calls that return a list are limited in the amount of records they may return, so multiple API calls may be\n required to bring all records. Such an API call also returns a records field, which contains the number of records\n in the current page, the current page number and the total number of records.\n

\n

\nIn cases where the total number of records exceeds the number of records thus far retrieved, the records field will also\n contain a cursor field which can be used to access the next page of records. To retrieve the next page, repeat the API call with\n the cursor value as supplied by the previous API call. All other request inputs should remain the same.\n

\n

Forward Compatibility

\n\n

\nWhen coding a system to accept Gong data, take into account that Gong may, without prior warning, add fields to the JSON output.\n It is recommended to future proof your code so that it disregards all JSON fields you don't actually use.\n\n

", "image": "", "baseURL": "https://127.0.0.1:8443", "humanURL": "https://github.com/jentic/jentic-public-apis/tree/main/apis/openapi/gong.io/main/V2", "version": "V2", "tags": [ "gong.io", "main" ], "properties": [ { "type": "OpenAPI", "name": "OpenAPI definition", "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/gong.io/main/V2/openapi.json", "mediaType": "application/openapi+json" }, { "type": "GitHubRepo", "url": "https://github.com/jentic/jentic-public-apis/tree/main/apis/openapi/gong.io/main/V2" } ] } ] }