> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/billing-and-invoicing/integrating-with-maxio-chargify.md).

# Integrating with Maxio Chargify

Sync Maxio Chargify subscription and revenue data into Drivetrain for billing analytics. Covers API key setup and subdomain config.

[Prerequisites](#prerequisites)

[Maxio Chargify Setup](#maxio-chargify-setup)

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

To connect Maxio Chargify to Drivetrain, you need:

* An active Maxio Chargify account
* Admin privileges on Maxio Chargify

### Maxio Chargify Setup <a href="#maxio-chargify-setup" id="maxio-chargify-setup"></a>

1. Login to your Maxio Chargify account and navigate to **Config > Integrations** by clicking on the sidebar menu.
2. Next we need to create a new API key. Click on **New API Key**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-2fa90b6cd28ada8d9c679c6562485349276feca4%2FMaxio-1.avif?alt=media" alt=""><figcaption></figcaption></figure>

3. Make a note of the API Key.
4. You will also need to provide your subdomain name. For instance, if your Maxio Chargify site URL is [https://drivetrain.chargify.com](https://observe.chargify.com/), "drivetrain" is the subdomain name.

{% hint style="info" %}
That’s it! Share the API key and subdomain name with your customer success manager so they can get started!
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.drivetrain.ai/integration-guide/readme/billing-and-invoicing/integrating-with-maxio-chargify.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.