Altegio (YCLIENTS)

The API adapter is implemented. Validate your own account and authorized actions before routing production calls.

Before you start

Connect the account belonging to this business and workspace. Vendor subscriptions, API limits and role permissions still apply.

API: Altegio public booking API v1 (YCLIENTS family)

Authentication: Bearer partner token with Accept: application/vnd.api.v2+json

Get access and connect

1. Apply for Altegio developer/partner access and obtain a partner token authorized for the client's location.
2. Save the token, locationId and bookingFormId in Verbatik.
3. Read booking form, services and staff; check live service/staff availability before creating an appointment.
4. If the location requires phone_confirmation, collect its actual SMS verification code from the caller. The provider rejects booking without it; Verbatik does not bypass verification.
5. Existing appointment changes require an additional authorized user token and the corresponding partner/user API contract. Those mutations are not enabled in this public booking adapter.

Account requirements

• Altegio partner token
• Clinic location ID and booking form ID
• Caller SMS verification when required by location
• Confirm compatibility with the client's exact Altegio/YCLIENTS deployment

Permissions

• Partner access to booking form, services, staff, available slots and appointment creation

Grant the subset needed for the actions you enable. API scopes do not override the connected user’s record permissions or vendor validation rules.

Connection fields

• accessToken — API key or authorized access token (required). Secret fields are saved as workspace credentials.
• locationId — Location ID (required).
• bookingFormId — Booking form ID (required).

Available actions

• test_connection — Read. Read the configured booking form and location settings.
• list_services — Read. Read services available for online booking.
• list_staff — Read. Read staff available for online booking.
• check_availability — Read. Read available times for one service/staff combination on a chosen date.
• create_appointment — Write. Create a single appointment using service/staff IDs and a checked time. A verification code is required whenever the location requires phone confirmation.

Verify before going live

Run Test connection and one read action against a known permitted record. Then test each intended write in an authorized sandbox. Check the provider’s own record and the Verbatik receipt. Publish the agent after assigning its tools. If a write has an unknown outcome, reconcile it with the vendor before trying again.

Vendor documentation

• Setup and API documentation
• Additional provider reference