Community OpenAPI document · agent-readyCRMCustomer Successbasic65 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Retrieve Gong calls, transcripts, users, and stats, upload call recordings, and push CRM data through 65 endpoints on the Gong platform.
Use for: Retrieve every Gong call recorded for a specific account in the last 30 days, I want to upload an externally recorded sales call into Gong, Get the talk ratio and activity stats for a sales rep this quarter, List the calls saved into a Gong library folder for new-hire training
Not supported: Does not handle live call dialing, CRM opportunity creation, or video conferencing - use for retrieving Gong calls and stats, uploading recordings, library curation, CRM ingest, and data-privacy erasure only.
The Gong API exposes 65 endpoints for retrieving call recordings, transcripts, user data, statistics, library content, and CRM activity from the Gong revenue intelligence platform. It also lets external systems upload call media into Gong, push CRM context, and erase user data on request for privacy compliance. The API is centred on calls, users, stats, library, and CRM resources, so revenue ops teams can stream Gong's conversational signal into dashboards, coaching tools, and forecasting models.
Install Jentic One Beta
Connect the Gong API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gong API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgong.io%2Fgong" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgong.io%2Fgong" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Gong API.
Retrieve calls in a date range and pull detailed call data with transcripts
Upload externally recorded call media into Gong for analysis and coaching
Read user statistics on activity, talk ratios, and meeting volume
Read and write library folders, calls, and content shared with reps
Push CRM context such as accounts, opportunities, and stages into Gong
Erase a user and all associated personal data for privacy compliance
Use Cases
Patterns agents use Gong API for, with concrete tasks.
★ Conversation Intelligence Pipeline
Revenue operations teams pull Gong call data and transcripts on a schedule to feed downstream analytics and AI summarisation. The API's POST /v2/calls/extensive endpoint accepts rich filters so a job can fetch only the calls relevant to a forecasting or coaching model rather than syncing the full corpus.
Fetch every call from /v2/calls/extensive between 2026-04-01 and 2026-06-30 for the EMEA team and store the transcripts.
External Recording Ingestion
Teams that record calls in tools other than Gong (in-app voice, custom dialers, internal voice systems) push those recordings into Gong via POST /v2/calls and PUT /v2/calls/{id}/media so the same coaching, scoring, and search workflow applies. This is critical for organisations whose dialer is custom-built or governed by a regional vendor.
Upload an MP3 recording for an external call held on 2026-06-09 with metadata for participants and account, then attach the media to the new call ID.
Privacy Erasure Workflow
When an employee or customer exercises their right to be forgotten, the Gong API's data privacy endpoints delete their records so the platform stays compliant with GDPR and similar laws. Combined with Gong's audit endpoints, an automation can produce evidence of erasure for the legal team.
Call POST /v2/data-privacy/erase-data-for-email-address for the email address provided by legal and capture the response for the audit log.
AI Coaching Agent via Jentic
An AI coaching agent can pull a rep's recent calls, score them against a playbook, and write the summary back to Gong's library so the team sees coaching notes alongside the recording. Through Jentic the agent searches for the right call retrieval operation by intent and executes with credentials held in the vault.
Retrieve the last 5 calls for rep user_42, score them, and add the highest-scoring one to the 'Best Discovery Calls' library folder.
Key Endpoints
65 endpoints — the gong api exposes 65 endpoints for retrieving call recordings, transcripts, user data, statistics, library content, and crm activity from the gong revenue intelligence platform.
METHOD
PATH
DESCRIPTION
GET
/v2/calls
Retrieve calls by date range
POST
/v2/calls
Add a new call record
POST
/v2/calls/extensive
Retrieve detailed call data with filters
PUT
/v2/calls/{id}/media
Upload or update call media
POST
/v2/data-privacy/erase-data-for-email-address
Erase user data by email
GET
/v2/permission-profile
Read a permission profile
PUT
/v2/meetings/{meetingId}
Update a Gong meeting
GET
/v2/calls
Retrieve calls by date range
POST
/v2/calls
Add a new call record
POST
/v2/calls/extensive
Retrieve detailed call data with filters
PUT
/v2/calls/{id}/media
Upload or update call media
POST
/v2/data-privacy/erase-data-for-email-address
Erase user data by email
GET
/v2/permission-profile
Read a permission profile
PUT
/v2/meetings/{meetingId}
Update a Gong meeting
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
G
Gong API
- Non-Ready (B-)62/100
34
Foundational Compliance77
Developer Experience & Jentic Compatibility58
AI-Readiness & Agent Experience92
Agent Usability100
Security65
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
34
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: FSignals: 4
0%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
35%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
77
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
37%
Example Density
How richly the API is illustrated with examples.
93%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
58
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C+Signals: 4
80%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
98%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
54%
Summary Coverage
Coverage of summaries across operations/tags/info.
92
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
92%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
65
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
65%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Gong by hand means encoding its access key and secret for basic auth against api.gong.io, handling the v2 call listing and extensive filter bodies, and mapping the recording upload and data-privacy endpoints yourself. Through Jentic you install once, import Gong from the API Directory, store the access key once, and your agent calls it.
Permission scoping
Gong filters calls through request bodies and query parameters rather than a resource in the URL path, so scope the agent to the operations it needs, such as listing calls or retrieving stats. You choose the operations it may call, so ones like erasing data for an email address or uploading call media are not included unless you add them.
Credential isolation
Your Gong access key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'retrieve gong call transcripts' or 'list recent calls', and Jentic returns the matching Gong operation with its filter schema so the agent calls the right endpoint without reading the Gong reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Gong API through Jentic.
What authentication does the Gong API use?
Gong uses HTTP Basic authentication with an access key and secret retrieved from the Gong API Page (technical administrator access required). Through Jentic these credentials are stored encrypted in the vault and scoped to one Gong tenant, and they never enter the agent's context.
Can I upload an externally recorded call into Gong?
Yes. POST /v2/calls creates the call record with participant and account metadata, then PUT /v2/calls/{id}/media attaches the audio or video file. Gong then runs the same transcription, scoring, and search pipeline as for natively recorded calls.
What are the rate limits for the Gong API?
Gong publishes per-tenant rate limits in the Gong API documentation. The OpenAPI spec does not encode exact numbers, so check app.gong.io/company/api before running large historical pulls - POST /v2/calls/extensive is the right endpoint for paginated bulk reads.
How do I retrieve detailed call data through Jentic?
Search Jentic for 'retrieve gong call data with filters', load the schema for POST /v2/calls/extensive, and execute with your filter object. Jentic injects the basic auth credentials at execution so the agent only handles the date range, participants, and which fields to return.
Can the Gong API erase a user's data on request?
Yes. POST /v2/data-privacy/erase-data-for-email-address removes a user and their associated calls and stats so the tenant stays compliant with privacy laws such as GDPR. The endpoint returns confirmation that the agent can persist as evidence.
Does the Gong API let me read CRM data from Salesforce?
No, it works the other way: the CRM endpoints accept account, opportunity, and stage data being pushed into Gong from your CRM so calls can be enriched. To read live CRM records, use the Salesforce API directly and feed the result into Gong's CRM ingest endpoints.
Can I limit what my agent is allowed to do with the Gong API?
Yes. Because your Jentic One instance is self-hosted, you decide which Gong operations the agent may call, and your own rules govern access. Since Gong scopes calls through request bodies and query parameters rather than a resource in the URL path, you grant only the operations the agent needs, such as listing calls or reading user stats. Sensitive operations like POST /v2/data-privacy/erase-data-for-email-address or uploading call media through PUT /v2/calls/{id}/media stay out of reach unless you explicitly add them.
GET STARTED