Gong
Gong is the revenue intelligence platform that captures and analyzes customer interactions across calls, emails, and meetings. APIs expose calls, transcripts, deals, users, and analytics.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Gong the way a machine reads it — 145 machine-readable artifacts across 26 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 47.4/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 26
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 Calls API
List calls, retrieve metadata, transcripts, recordings and trackers.
Gong Users API
Read user, manager and team data.
Gong CRM Integration API
Push CRM-style account, contact, deal and engagement data into Gong.
Gong Engagement Data API
Read activity, scorecards, trackers, and library content.
Gong Library API
Access and organize library folders and shared call collections.
Gong Audit Logs API
Operations for retrieving audit log data
Gong Calls API
Operations for managing and retrieving call data
Gong CRM Data API
Operations for uploading and retrieving CRM data
Gong CRM Integration API
Operations for registering and managing CRM integrations
Gong CRM Schema API
Operations for managing CRM object schemas
Gong Data Privacy API
Operations for data privacy management and compliance
Gong Digital Interactions API
Operations for posting digital interaction data
Gong Engagement Events API
Operations for reporting customer engagement events
Gong Flows API
Operations for managing Engage flows
Gong Folders API
Operations for managing flow folders
Gong Library API
Operations for browsing and retrieving library content
Gong Meetings API
Operations for managing meetings
Gong Permission Profiles API
Operations for managing permission profiles
Gong Prospects API
Operations for managing prospects in Engage flows
Gong Recordings API
Operations for managing call recordings and media
Gong Scorecards API
Operations for retrieving scorecard configurations
Gong Statistics API
Operations for retrieving activity and performance statistics
Gong Trackers API
Operations for retrieving tracker configurations
Gong Transcripts API
Operations for retrieving call transcripts
Gong Users API
Operations for managing and retrieving user data
Gong Workspaces API
Operations for managing workspaces
Scroll within the panel for all 26 ·
Open Collections 12
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Gong Auditing API
OPEN COLLECTIONGong Calls API
OPEN COLLECTIONGong CRM API
OPEN COLLECTIONGong Data Privacy API
OPEN COLLECTIONGong Engage API
OPEN COLLECTIONGong Engagement API
OPEN COLLECTIONGong Library API
OPEN COLLECTIONGong Meetings API
OPEN COLLECTIONGong Permissions API
OPEN COLLECTIONGong Settings API
OPEN COLLECTIONGong Stats API
OPEN COLLECTIONGong Users API
OPEN COLLECTIONScroll 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.
Gong Plans Pricing
PLANSRate 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 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 Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Gong Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Gong API Rules
SPECTRALJSON Schema 97
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AggregatedActivityRequest
JSON SCHEMAAggregatedActivityResponse
JSON SCHEMAAnsweredScorecard
JSON SCHEMAAnsweredScorecardsRequest
JSON SCHEMAAnsweredScorecardsResponse
JSON SCHEMAAssignProspectsRequest
JSON SCHEMAAssignProspectsResponse
JSON SCHEMAAuditLogEntry
JSON SCHEMAAuditLogsResponse
JSON SCHEMABaseResponse
JSON SCHEMAGong Call
JSON SCHEMACallParty
JSON SCHEMACallsResponse
JSON SCHEMACallTranscript
JSON SCHEMACallTranscriptRequest
JSON SCHEMACallTranscriptsResponse
JSON SCHEMACoachingMetricsResponse
JSON SCHEMAContentShareEventRequest
JSON SCHEMAContentViewEventRequest
JSON SCHEMACreateMeetingRequest
JSON SCHEMACreatePermissionProfileRequest
JSON SCHEMACrmEntitiesUploadRequest
JSON SCHEMACrmEntitiesUploadResponse
JSON SCHEMACrmEntitySchemaResponse
JSON SCHEMACrmEntitySchemaUploadRequest
JSON SCHEMACrmIntegrationRegistrationRequest
JSON SCHEMACrmIntegrationRegistrationResponse
JSON SCHEMACrmIntegrationsResponse
JSON SCHEMACrmObjectsResponse
JSON SCHEMACustomActionEventRequest
JSON SCHEMADailyActivityRequest
JSON SCHEMADailyActivityResponse
JSON SCHEMADataDeletionResponse
JSON SCHEMADataReference
JSON SCHEMADetailedCall
JSON SCHEMADigitalInteractionRequest
JSON SCHEMADigitalInteractionResponse
JSON SCHEMAEmailDeleteRequest
JSON SCHEMAEmailReferencesResponse
JSON SCHEMAErrorResponse
JSON SCHEMAExtensiveCallsRequest
JSON SCHEMAExtensiveCallsResponse
JSON SCHEMAGong Engage Flow
JSON SCHEMAFlowContentOverrideRequest
JSON SCHEMAFlowFolder
JSON SCHEMAFlowFoldersResponse
JSON SCHEMAFlowsResponse
JSON SCHEMAIntegrationSettingsRequest
JSON SCHEMAInteractionStatsRequest
JSON SCHEMAInteractionStatsResponse
JSON SCHEMALibraryCall
JSON SCHEMALibraryFolder
JSON SCHEMALibraryFolderCallsResponse
JSON SCHEMALibraryFoldersResponse
JSON SCHEMAManualAssociationResponse
JSON SCHEMAGong Meeting
JSON SCHEMAMeetingAttendee
JSON SCHEMAMeetingIntegrationStatusRequest
JSON SCHEMAMeetingIntegrationStatusResponse
JSON SCHEMAMeetingResponse
JSON SCHEMANewCallAddingRequest
JSON SCHEMANewCallAddingResponse
JSON SCHEMANewCallParty
JSON SCHEMANewCallRecordingResponse
JSON SCHEMAPermissionProfile
JSON SCHEMAPermissionProfileResponse
JSON SCHEMAPermissionProfilesResponse
JSON SCHEMAPermissionProfileUsersResponse
JSON SCHEMAPhoneDeleteRequest
JSON SCHEMAPhoneReferencesResponse
JSON SCHEMAGong Prospect
JSON SCHEMAProspectsFlowsRequest
JSON SCHEMAProspectsFlowsResponse
JSON SCHEMAGong Scorecard
JSON SCHEMAScorecardQuestion
JSON SCHEMAScorecardsResponse
JSON SCHEMASpecificCallResponse
JSON SCHEMATracker
JSON SCHEMATrackersResponse
JSON SCHEMAGong Call Transcript
JSON SCHEMAUnassignProspectsRequest
JSON SCHEMAUnassignProspectsResponse
JSON SCHEMAUpdateMeetingRequest
JSON SCHEMAUpdatePermissionProfileRequest
JSON SCHEMAUploadStatusResponse
JSON SCHEMAGong User
JSON SCHEMAUserAggregatedActivity
JSON SCHEMAUserCallAccessRequest
JSON SCHEMAUserCallAccessResponse
JSON SCHEMAUserCallAccessUpdateRequest
JSON SCHEMAUserInteractionStats
JSON SCHEMAUserResponse
JSON SCHEMAUserSettingsHistoryResponse
JSON SCHEMAUsersFilterRequest
JSON SCHEMAUsersResponse
JSON SCHEMAGong Workspace
JSON SCHEMAWorkspacesResponse
JSON SCHEMAScroll within the panel for all 97 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Gong Structure
JSON STRUCTURESecurity Posture 3
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/gong · machine-readable index on apis.io