> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/guides/app-reference/acuity-scheduling.md).

# Acuity Scheduling

Middle offers an app connection to Acuity Scheduling that syncs appointments, orders, appointment types, and labels. Middle utilizes Acuity's API-key-based Scheduling API.

{% embed url="<https://developers.acuityscheduling.com/reference/quick-start#get-appointments>" %}

## One-to-one connection

This means that there is a one-to-one between a Middle app connection and an Acuity Scheduling account. If you need to connect more than one Acuity Scheduling account to a single Middle account, you'll need to create multiple app connections and map them accordingly using [workflow triggers](/middle-docs/product/accounts/workflow-triggers.md).

{% hint style="warning" %}
Reach out to the Middle team to explore OAuth2 options. Acuity Scheduling's OAuth2 API allows multi-account connections.
{% endhint %}

## Connecting Acuity Scheduling to Middle

{% stepper %}
{% step %}

### Attain your numeric user ID and API key

These can be found in your Acuity account [under Integrations](https://secure.acuityscheduling.com/app.php?action=settings\&key=api).

{% embed url="<https://secure.acuityscheduling.com/app.php?action=settings&key=api>" %}
{% endstep %}

{% step %}

### Add a new app connection and enter your credentials

{% embed url="<https://docs.middle.app/middle-docs/building-workflows/connect-or-edit-an-app-connection#adding-a-new-app-connection>" %}
{% 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.middle.app/middle-docs/guides/app-reference/acuity-scheduling.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.