Get an audit

Head to head · Calendar read · October 2026 research run

Acuity Scheduling API vs Aurinko Calendar API

Aurinko Calendar API scores 45.6 (E) on agent readiness against Acuity Scheduling API's 42.4 (E), and leads in 5 of 7 scored categories. Acuity Scheduling API leads on reliability and transparency & trust. Both do calendar read.

Acuity Scheduling APISquarespace · HTTP API E42.4/100#678 of 722 Aurinko Calendar APIYoxel, Inc. · HTTP API E45.6/100#654 of 722

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 40
  • Transparency & trust, 54 against 44

Watch for

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

Aurinko Calendar API E

Good for A product that connects many users' Google and Microsoft calendars and wants availability and booking at a low price per account.

Ahead on

  • Schema & documentation, 66 against 56
  • Agent ergonomics, 56 against 44
  • Security & auth, 41 against 27
  • Payments & pricing, 40 against 30
  • Maintenance & community, 20 against 15

Watch for

No status page, incident history or SLA found, and the terms supply the service as is

Score by category

CategoryWeight this runAcuity Scheduling APIAurinko Calendar APIEdge
Reliability16%205840Acuity Scheduling API +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25666Aurinko Calendar API +10
Agent ergonomics13%16.24456Aurinko Calendar API +12
Security & auth14%17.52741Aurinko Calendar API +14
Payments & pricing10%12.53040Aurinko Calendar API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81520Aurinko Calendar API +5
Transparency & trust7%8.85444Acuity Scheduling API +10
Negative events≤1500
Total42.4 · E45.6 · E

Facts side by side

FactAcuity Scheduling APIAurinko Calendar API
KindHTTP APIHTTP API
VendorSquarespaceYoxel, Inc.
Hosted endpointhttps://acuityscheduling.com/api/v1https://api.aurinko.io
TransportsHTTPHTTP
AuthOAuth or keyOAuth
PricingPaidPaid
x402nono
LicenceProprietary service under Squarespace's Developer Terms. The Node.js and PHP SDKs are MITProprietary service under Yoxel's Terms of Services Agreement
Read-only variant documentednono
llms.txtyesyes
Terms last updated2025-12-162022-08-11
Privacy policy last updatedno date given2022-08-11
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity9.2k npm/wknone

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.

Aurinko Calendar API

A public OpenAPI 3.0 spec covers 154 operations, with free/busy, meeting-time suggestion and booking profiles alongside calendar reads and writes, and prices start at $1 an active account a month. No status page, SLA, changelog or official SDK was found, and the application's client secret reaches every connected account.

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

Aurinko Calendar API

  1. Use https://api.aurinko.io/v1. Several cURL examples in the docs print https:/api.aurinko.io with one slash
  2. Send If-Match with the event's etag on PATCH /v1/calendars/{calendarId}/events/{eventId}. A stale value returns 412
  3. Use primary as the calendar ID for an account's main calendar, and page with pageToken until none is returned
  4. Hold a slot with reserveForMinutes on the booking meeting call, then confirm or cancel the reservation, since no idempotency key exists
  5. Retry 429, 408 and 5xx with exponential backoff. Do not retry 404. A 429 can come from Google or Microsoft limits behind the API

Questions

Which is better for AI agents, Acuity Scheduling API or Aurinko Calendar API?

Aurinko Calendar API scores 45.6 (E) on agent readiness against Acuity Scheduling API's 42.4 (E), and leads in 5 of 7 scored categories. Acuity Scheduling API leads on reliability and transparency & trust.

Do Acuity Scheduling API and Aurinko Calendar API need an API key?

Acuity Scheduling API takes an API key or an OAuth sign-in. Aurinko Calendar API uses an OAuth sign-in.

Can an agent call Acuity Scheduling API and Aurinko Calendar API without installing anything?

Yes. Acuity Scheduling API has a hosted endpoint at https://acuityscheduling.com/api/v1 and Aurinko Calendar API at https://api.aurinko.io.

Other comparisons with Acuity Scheduling API or Aurinko Calendar API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report