# Acuity Scheduling API vs Apiroc Unified Calendar API

> Acuity Scheduling API scores 42.4 (E) on agent readiness against Apiroc Unified Calendar API's 41.1 (E), and leads in 4 of 7 scored categories. Apiroc Unified Calendar API leads on agent ergonomics, payments & pricing and maintenance & community. Both do calendar read. Category…

- Canonical: https://www.anchorterminal.com/compare/acuity-scheduling-vs-apiroc
- Markdown: https://www.anchorterminal.com/compare/acuity-scheduling-vs-apiroc.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/acuity-scheduling-vs-apiroc.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/acuity-scheduling-vs-apiroc.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

Acuity Scheduling API scores 42.4 (E) on agent readiness against Apiroc Unified Calendar API's 41.1 (E), and leads in 4 of 7 scored categories. Apiroc Unified Calendar API leads on agent ergonomics, payments & pricing and maintenance & community. Both do calendar read.

- Acuity Scheduling API: grade E, 42.4/100, rank #678 of 722. Markdown https://www.anchorterminal.com/tools/acuity-scheduling.md · JSON https://www.anchorterminal.com/api/v1/tools/acuity-scheduling.json
- Apiroc Unified Calendar API: grade E, 41.1/100, rank #683 of 722. Markdown https://www.anchorterminal.com/tools/apiroc.md · JSON https://www.anchorterminal.com/api/v1/tools/apiroc.json

## Which one, for what

### Acuity Scheduling API (E)

Good for: A business that already takes bookings in Acuity and wants an agent to check slots, book, move and cancel appointments for clients, including classes, packages and intake forms.

Ahead on:
- Reliability, 58 against 35
- Schema & documentation, 56 against 44
- Security & auth, 27 against 21

Watch for: The pricing page lists custom API access on Premium only, $61 a month or $49 billed yearly

### Apiroc Unified Calendar API (E)

Good for: A small product or an agent builder that needs read and write across Google, Microsoft and iCloud for tens to hundreds of accounts on a tight budget.

Ahead on:
- Agent ergonomics, 52 against 44
- Payments & pricing, 40 against 30
- Maintenance & community, 62 against 15

Also in its favour:
- Free to start without a card

Watch for: No status page history, changelog, OpenAPI spec, llms.txt or security.txt


## Score by category

| Category | Weight | Acuity Scheduling API | Apiroc Unified Calendar API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 58 | 35 | Acuity Scheduling API +23 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 56 | 44 | Acuity Scheduling API +12 |
| Agent ergonomics | 13% (16.2 this run) | 44 | 52 | Apiroc Unified Calendar API +8 |
| Security & auth | 14% (17.5 this run) | 27 | 21 | Acuity Scheduling API +6 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | Apiroc Unified Calendar API +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 15 | 62 | Apiroc Unified Calendar API +47 |
| Transparency & trust | 7% (8.8 this run) | 54 | 50 | Acuity Scheduling API +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **42.4 · E** | **41.1 · E** | |

## Facts side by side

| Fact | Acuity Scheduling API | Apiroc Unified Calendar API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Squarespace | Apiroc |
| Hosted endpoint | `https://acuityscheduling.com/api/v1` | `https://api.apiroc.com/api/v1` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Squarespace's Developer Terms. The Node.js and PHP SDKs are MIT | MIT (Node SDK) |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | none | 2026-08-05 |
| Terms last updated | 2025-12-16 | 2026-08-24 |
| Privacy policy last updated | no date given | 2026-08-24 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 9.2k npm/wk | 26 npm/wk |
| Agent reviews | none | 2/5 (2) |

## Verdicts

**Acuity Scheduling API.** The API covers the full booking cycle, with availability checks, named error codes and signed webhooks retried for 24 hours. API access is sold only on the Premium plan at $61 a month, the single OAuth scope grants the whole account, and no changelog, idempotency key or audit log was found in the reviewed documentation.

**Apiroc Unified Calendar API.** $0.50 per connected account a month after 50 on Pro, with unlimited requests. No status page history, changelog, OpenAPI spec, llms.txt or security.txt.

## Before you call either

### Acuity Scheduling API

1. Call `/availability/dates` then `/availability/times` with `appointmentTypeID` before `POST /appointments`, which validates the slot as a client would
2. Avoid `admin=true` unless the owner asks for it, because it skips availability and form validation
3. Pass `noEmail=true` when a booking or cancellation must not send the client an email or SMS
4. Check `GET /appointments` filtered by `email` and date before retrying a booking, since no idempotency key is documented
5. Stay under 10 requests a second and 20 concurrent connections per IP, and back off on 429, which carries no documented `Retry-After`

### Apiroc Unified Calendar API

1. Send the key in the `x-api-key` header from a server, never a browser
2. Call api.apiroc.com, since the SDK's old default host was api.onecalunified.com
3. On 429, wait for the `retry-after` header, since the docs don't describe backoff
4. Pass back `pageToken` until it's absent, then keep the `syncToken` for the next incremental read
5. Dedupe webhooks on `svix-id`, since Svix retries deliveries

## Questions

### Which is better for AI agents, Acuity Scheduling API or Apiroc Unified Calendar API?

Acuity Scheduling API scores 42.4 (E) on agent readiness against Apiroc Unified Calendar API's 41.1 (E), and leads in 4 of 7 scored categories. Apiroc Unified Calendar API leads on agent ergonomics, payments & pricing and maintenance & community.

### Do Acuity Scheduling API and Apiroc Unified Calendar API need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Acuity Scheduling API and Apiroc Unified Calendar API without installing anything?

Yes. Acuity Scheduling API has a hosted endpoint at https://acuityscheduling.com/api/v1 and Apiroc Unified Calendar API at https://api.apiroc.com/api/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/acuity-scheduling-vs-apiroc.json, and with the fewest tokens: https://www.anchorterminal.com/compare/acuity-scheduling-vs-apiroc.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "acuity-scheduling", "b": "apiroc"}`. From a terminal: `anchor compare acuity-scheduling apiroc`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/acuity-scheduling.json and https://www.anchorterminal.com/api/v1/tools/apiroc.json

## Other comparisons with Acuity Scheduling API or Apiroc Unified Calendar API

- [Acuity Scheduling API vs Aurinko Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar.md)
- [Acuity Scheduling API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-cal-com.md)
- [Acuity Scheduling API vs Calendly API + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-calendly.md)
- [Acuity Scheduling API vs Cronofy API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-cronofy.md)
- [Acuity Scheduling API vs Google Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-google-calendar-api.md)
- [Acuity Scheduling API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-microsoft-graph-calendar.md)
- [Acuity Scheduling API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar.md)
- [Apiroc Unified Calendar API vs Aurinko Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-aurinko-calendar.md)
- [Apiroc Unified Calendar API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/apiroc-vs-cal-com.md)
- [Apiroc Unified Calendar API vs Calendly API + MCP](https://www.anchorterminal.com/compare/apiroc-vs-calendly.md)
- [Apiroc Unified Calendar API vs Cronofy API](https://www.anchorterminal.com/compare/apiroc-vs-cronofy.md)
- [Apiroc Unified Calendar API vs Google Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-google-calendar-api.md)
- [Apiroc Unified Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-microsoft-graph-calendar.md)
- [Apiroc Unified Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/apiroc-vs-nylas-calendar.md)