Gong
Gong is the Revenue AI platform that captures customer interactions across phone, web conferencing, and email, then applies conversation intelligence and generative AI to coach reps, forecast pipeline, and surface deal risk. Gong exposes a REST API at api.gong.io covering Calls, Users, Stats, Library, Settings, Workspaces, Permissions, Data Privacy, CRM, Logs, Engagement, and webhook-style automation rules, plus an outbound data integrations program for pushing call recordings, transcripts, and metadata into Gong from third-party telephony and conferencing systems.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Gong the way a machine reads it — 17 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Gong scores 36.8/100 (thin), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Gong
Each block below is one kind of artifact we hold for Gong. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Gong Public API
Gong's primary REST API for reading and writing platform data — calls, users, stats, library content, settings, workspaces, permissions, data privacy, CRM data, audit logs, and ...
Gong Calls API
Endpoints for retrieving call metadata, transcripts, media URLs, extensive filtering, and adding new calls (recordings and metadata) from external telephony and conferencing pla...
Gong Users API
Endpoints for listing and managing Gong users, their roles, manager relationships, and metadata used for permissioning and reporting.
Gong Stats API
Aggregated statistics for activity, interaction, and rep-level metrics — used to back dashboards, scorecards, and external BI integrations.
Gong Library API
Endpoints for browsing Gong libraries and folders, retrieving call lists inside a folder, and managing the curated learning content shared across teams.
Gong Settings API
Read and update tenant-level configuration — trackers, scorecards, and tracking settings used by Gong to score calls and surface signals.
Gong Workspaces API
Manage Gong workspaces — the isolation boundary used for multi-tenant or multi-business-unit Gong deployments.
Gong Permissions API
Endpoints for listing and managing permission profiles and access controls applied to Gong users and content.
Gong Data Privacy API
Endpoints supporting GDPR / CCPA workflows — locate, export, and purge personal data stored in Gong on behalf of an individual.
Gong CRM API
Endpoints for reading CRM object schema and data Gong has ingested from connected CRMs (Salesforce, HubSpot, Dynamics), and for pushing engagement activity back into the CRM con...
Gong Logs API
Audit log endpoints for retrieving user activity, configuration changes, and access events used in compliance and SIEM workflows.
Gong Engagement API
Engagement endpoints surfacing email and meeting touchpoints between reps and prospects, used for activity analytics and pipeline hygiene.
Scroll within the panel for all 12 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Gong Io Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Gong Io Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Gong — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/gong-io · machine-readable index on apis.io