> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/daxko-engage-pro.md).

# Daxko Engage Pro

{% hint style="info" %}
Formerly VFPnext
{% endhint %}

Integrating with Daxko Engage Pro requires an API key, your Engage Pro subdomain, account number, and club ID.

Follow the below steps to connect with Daxko Engage Pro:

{% stepper %}
{% step %}

### Fetch your API credentials

To get your API key, account number, and club ID, log into Daxko Engage Pro:

1. Click **Developer** in the left-hand menu
2. Select **API Docs**
3. Click **Show API Keys**
4. You will then be able to copy your API key, account number, and club ID

{% embed url="<https://www.vfpnext.com/dashboard/api>" %}
{% endstep %}

{% step %}

### Note your subdomain

Note your Engage Pro subdomain. You'll find this in your URL when logged in. This is needed to connect with your Engage Pro API.
{% endstep %}

{% step %}

### Send your credentials to Perkville

Using a secure method, like [OneTimeSecret](https://onetimesecret.com/), send your credentials to your Perkville Support at <support@perkville.com>.

{% hint style="info" %}
If you want to handle the credentials yourself, let your rep. know and they can give you access to Middle, our integration platform
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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://docs.perkville.com/integrations/integration-reference/daxko-engage-pro.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.
