> For the complete documentation index, see [llms.txt](https://docs.simplebooth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplebooth.com/customization-guide/experience-designer/post-capture/data-capture/open-api-integration.md).

# Open API Integration

The API integration works in conjunction with [Data Capture](/customization-guide/experience-designer/post-capture/data-capture.md) to collect information from participants and deliver it directly to your own server, database, or CRM.

This option is intended for custom marketing or specialized data workflows. Because it involves connecting Simple Booth to external systems, it requires development resources to implement.

***

#### How it Works

Once configured, the API integration removes the need for manual data exports and ensures your lead generation or marketing workflows stay updated throughout your event.

After a participant submits their information via the Data Capture form, the API automatically triggers a request to your server. This transfer happens in the background, so the guest experience is uninterrupted while your database or CRM is updated in near real-time.

***

#### API Setup

To begin integrating your data capture with your own internal systems, follow the setup steps in our [**API Tokens guide**](https://docs.simplebooth.com/account-management/account-management/api-tokens#creating-an-api-token).

{% hint style="info" %}
The API is designed for technical users. If you do not have a developer and need a more "plug-and-play" solution, consider using our [Mailchimp](/customization-guide/experience-designer/post-capture/data-capture/mailchimp-integration.md) integration instead.
{% endhint %}

***

{% hint style="success" %}

## **Plan Availability**

✅ Pro, Select 

❌ Lite, Core, Plus
{% 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://docs.simplebooth.com/customization-guide/experience-designer/post-capture/data-capture/open-api-integration.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.