Scheduling & Booking · Integration
Appointo
Add Appointo to your product for your customers, and give your AI agents governed access to it.
Appointo adds appointment booking to storefronts, and its API is served from app.appointo.me/api rather than an api subdomain, authenticating with an APPOINTO-TOKEN request header; without it the response is a 401 carrying an explicit no_api_token_present error code, which makes misconfiguration easy to detect. API access is limited to paid plans, so a customer on the free tier can generate nothing to connect with and the integration has to fail gracefully at connect time rather than mid-workflow. The model separates products, which are the bookable services and their availability rules, from bookings and the individual appointments inside them, and recurring services also produce subscription contracts, so a single customer purchase can span all four objects. Listing endpoints cap at 100 records per page and page with limit and offset, with a status filter of past or upcoming, so a full history sync is a loop rather than a single call. fastn stores each customer's Appointo token on their own connection and keeps the paging and plan constraints handled for you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Appointo account so their bookings appear in your product without CSV exports
Show upcoming appointments alongside the order or customer record your application already holds
Notify staff through your own channels when a booking is made or moved, driven by Appointo data
Report on recurring service revenue by reading subscription contracts rather than reconstructing it from bookings
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which appointments are upcoming this week for a tenant and which have no assigned staff member
Have an agent look up a single booking by id and summarise its history, with the lookup audited per tenant
Let an agent list bookable products and their availability so a human can spot gaps in the schedule
Example prompt
What appointments do we have booked for next week and which services are they for?
Set up Appointo in 4 steps
- 01Enable the Appointo connector from your fastn dashboard.
- 02Have each customer authorise their own Appointo account, so calls run under their credentials rather than a shared key.
- 03Decide which bookings, events and availability your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Appointo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Appointo integration without building it. Your customers connect their own Appointo account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Appointo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Appointo connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Compare with
Often used alongside
Tools the same teams tend to run next to Appointo, across other categories.
Appointo integration FAQ
How do I add an Appointo integration to my product?
Enable the Appointo connector in your fastn dashboard, then let each customer authenticate their own Appointo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Appointo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Appointo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Appointo account and only ever sees their own bookings, events and availability. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Appointo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which appointments are upcoming this week for a tenant and which have no assigned staff member
Who maintains the Appointo integration?
fastn does. When Appointo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create, reschedule or cancel bookings in Appointo automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in Appointo?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the Appointo integration?
A common starting point: let a customer connect their own Appointo account so their bookings appear in your product without CSV exports. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Appointo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Appointo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Appointo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.