> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/sales/acuity-scheduling/faq.md).

# FAQ

<details>

<summary>What authentication method does Acuity Scheduling use in Coupler.io?</summary>

Acuity Scheduling uses API key authentication. You'll need your **User ID** and **API key**, both found under **Integrations > API** in your Acuity account settings. There's no OAuth flow — just copy and paste these two values into Coupler.io when setting up your data flow.

</details>

<details>

<summary>How far back can I pull appointment data?</summary>

You can pull appointment history as far back as your Acuity account has records — there's no hard limit on historical data. Use the date picker to set your start date when configuring the data flow. Keep in mind that very large date ranges can be slow on the first run or may trigger rate limits, so it's worth starting with a shorter window and expanding it once the initial sync succeeds.

</details>

<details>

<summary>Can I export intake form responses?</summary>

Yes — form data is available through the **Forms** entity, which returns your form definitions and field configurations. To link form responses to specific appointments, add both Appointments and Forms as sources in your data flow and use a **Join** transformation on client email or appointment ID.

</details>

<details>

<summary>Does Coupler.io support all Acuity calendars, or just the main one?</summary>

Coupler.io pulls data from all calendars under the connected account by default. The key requirement is that you authenticate with the **main account owner's** credentials — staff-level API keys may not have access to all calendars.

</details>

<details>

<summary>Can I combine Acuity data with data from another source like a CRM or payment tool?</summary>

Yes. In Coupler.io, you can add multiple sources to a single data flow. For example, you can bring in Acuity appointments alongside Stripe payments or HubSpot contacts, then use a **Join** transformation to match records by email address. This gives you a unified view of bookings and revenue without any manual work.

</details>

<details>

<summary>Can I send Acuity data to an AI tool like ChatGPT or Claude?</summary>

Yes — Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your appointment or client data directly to these tools for analysis, summaries, or recommendations.

</details>

<details>

<summary>Why do my appointment counts look different from what Acuity shows in its dashboard?</summary>

The most likely cause is your start date setting. Coupler.io only returns appointments from the start date you set, while Acuity's dashboard may show a different time range by default. Check that your start date matches the period you're comparing against. Also note that Acuity's dashboard may apply its own filters by calendar or status that Coupler.io doesn't replicate automatically.

</details>

<details>

<summary>Does Coupler.io sync Acuity data in real time?</summary>

No — Coupler.io syncs on a schedule you define (e.g., every hour, daily). Real-time webhooks are not supported for this source. For most use cases, an hourly or daily refresh is sufficient to keep your reports and dashboards up to date.

</details>

{% hint style="info" %}
For details on what fields are available in each entity, see the [Data Overview](/sources/category/sales/acuity-scheduling/data-overview.md) article. For help with connection errors or missing records, check the [Common Issues](/sources/category/sales/acuity-scheduling/common-issues.md) article.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/sales/acuity-scheduling/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.