Groove Python API Docs | dltHub

Groove is a customer support platform providing a REST API for managing customers, tickets, messages, and knowledge base content. The REST API base URL is https://api.groovehq.com/v1 and all requests require an access token provided either in the Authorization header or as access_token URL parameter.

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 Groove data in under 10 minutes.

---

What data can I load from Groove?

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

---

How do I authenticate with the Groove API?

Groove REST v1 uses a single account access token. Include it as a Bearer token in the Authorization header (Authorization: Bearer <access_token>) or as access_token query parameter. Requests must be sent with Content-Type: application/json.

1. Get your credentials

1. Sign in to Groove as an admin. 2) Open Account Settings. 3) Navigate to the API section (or Developer/API). 4) Copy the account's private access token shown there. 5) Use that token in Authorization header or access_token query parameter.

2. Add them to .dlt/secrets.toml

Copy
[sources.groove_source]
api_key = "your_groove_access_token_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 Groove 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 groove_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline groove_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 customers and messages from the Groove 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 groove_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.groovehq.com/v1",
            "auth": {
                "type": "bearer",
                "token": api_key,
            },
        },
        "resources": [
            {"name": "customers", "endpoint": {"path": "customers", "data_selector": "customers"}},
            {"name": "messages", "endpoint": {"path": "tickets/:ticket_number/messages", "data_selector": "messages"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="groove_pipeline",
        destination="duckdb",
        dataset_name="groove_data",
    )
    load_info = pipeline.run(groove_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("groove_pipeline").dataset()
sessions_df = data.customers.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM groove_data.customers LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("groove_pipeline").dataset()
data.customers.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 Groove 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

If you receive 401/403 or empty responses, verify you are using an admin account access token. Provide the token either in the Authorization header (Authorization: Bearer ) or as ?access_token= in the URL. Ensure Content-Type: application/json.

Pagination and meta

Most listing endpoints return paginated responses with a top-level collection key (e.g., "customers", "messages", "articles") and a "meta.pagination" object containing current_page, total_pages, total_count, and next_page. Use page and per_page query parameters (per_page max often 50).

422 validation errors

Validation errors return JSON with an "errors" object: { "errors": { "field_name": ["error"] } }. Other error statuses commonly return an empty body.

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