Gong Python API Docs | dltHub

Gong is a revenue intelligence platform that records and analyzes sales conversations and provides programmatic access to calls, transcripts, users, activity, and related metadata via a REST API. The REST API base URL is Region-specific Gong instance host. Common examples: https://{region}.app.gong.io or https://{region}.api.gong.io (e.g. https://us-6852.app.gong.io or https://us-0000.api.gong.io). Use the base URL shown in your Gong Admin > Settings > API section. and All requests require Basic auth with an Access Key (username) and Access Key Secret (password); OAuth2 is available for published apps..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Gong data in under 10 minutes.

---

What data can I load from Gong?

Here are some of the endpoints you can load from Gong:

---

How do I authenticate with the Gong API?

Gong issues an Access Key and Access Key Secret (username/password). Provide these via HTTP Basic Authorization header (Authorization: Basic <base64(access_key:access_key_secret)>). Alternatively create an OAuth2 app in Gong and use the OAuth token endpoints when building public integrations.

1. Get your credentials

1. Log into Gong as a Tech Admin. 2. Go to Admin center > Settings > Ecosystem > API (or Settings > API > Integrations). 3. Click "Get API Key" to generate an Access Key and Access Key Secret. Copy both; Access Key = username, Access Key Secret = password. 4. (Optional) For OAuth2 create an Integration (Create Integration) to obtain Client ID and Client Secret and configure redirect URIs.

2. Add them to .dlt/secrets.toml

Copy
[sources.gong_source]
access_key = "your_access_key_here"
access_key_secret = "your_access_key_secret_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.

---

How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

Copy
dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Gong API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

Copy
python gong_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline gong_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset gong_data
The duckdb destination used duckdb:/gong.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline gong_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.

---

Python pipeline example

This example loads calls and users from the Gong API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def gong_source(access_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "Region-specific Gong instance host. Common examples: https://{region}.app.gong.io or https://{region}.api.gong.io (e.g. https://us-6852.app.gong.io or https://us-0000.api.gong.io). Use the base URL shown in your Gong Admin > Settings > API section.",
            "auth": {
                "type": "http_basic",
                "access_key": access_key,
            },
        },
        "resources": [
            {"name": "calls", "endpoint": {"path": "v2/calls", "data_selector": "data.calls"}},
            {"name": "users", "endpoint": {"path": "v2/users", "data_selector": "data.users"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="gong_pipeline",
        destination="duckdb",
        dataset_name="gong_data",
    )
    load_info = pipeline.run(gong_source())
    print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.

---

How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("gong_pipeline").dataset()
sessions_df = data.calls.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM gong_data.calls LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("gong_pipeline").dataset()
data.calls.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.

---

What destinations can I load Gong data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

401 Unauthorized — caused by missing or incorrect Basic auth credentials. Ensure Authorization header is Basic <base64(access_key:access_key_secret)> and that the Access Key and Secret are active. If using OAuth, ensure token is valid and scopes include the requested API.

Rate limits

429 Too Many Requests — Gong enforces 3 requests per second and 10,000 requests per day. Respect the Retry-After header and implement exponential backoff.

Pagination quirks

Paginated endpoints return data.records with pagination info and a cursor token. Use the cursor in subsequent requests to fetch the next page. Some endpoints return currentPageNumber starting at 0.

Common 4xx/5xx responses

400 Bad Request — malformed query parameters or payload. 403 Forbidden — insufficient scopes/permissions. 404 Not Found — invalid resource id. 500+ — transient server errors; retry with backoff.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack