\ developers & partners hub Build Powerful Integrations _ Official API documentation for integrating online booking, CRM, scheduling, POS, and business management features into your applications 200+ API endpoints 99.98% Platform uptime 5+ New integrations per day Start Here Browse APIs Get API Key altegio-app — r2-d2 R2D2 Code vibe build r2-unit · ∞ context · maximum beeps ~/altegio-app · ● online Tip: paste an API's docs and I'll wire it up. > build an extension for my business platform — docs at developer.alteg.io ● *beep-boop!* Altegio's docs are chef's-kiss — 200+ typed endpoints, real examples. What should it do? ✳ computing · bloop · whirr > an AI agent that DMs me a daily report ● *whistle* — on it, wiring it up: ⏺ read yesterday's numbers ✓ ⏺ write a tidy summary ✓ ⏺ ping the owner at 9:00 sharp ✓ ● *bee-doo!* Your report-droid is live 🤖 > ask r2-d2 anything… ~/altegio-app · r2-unit · ctx 94% ▶▶ droid mode on · shift+tab to cycle \ quickstarts 01 / 06 New to Altegio? Start Here Pick the route that matches what you are building. Each guide explains exactly which credentials you need and what to do next. API v1, v2 & Online Booking Register, get your Partner Token and User Token, and learn the authorization header used by the live APIs Get credentials Marketplace App Install a draft app on your own test Location, activate it, and make authenticated calls before moderation Install & test Integrations Hub MCP Connect an AI assistant to plan, create, configure, and test your own marketplace application Connect MCP \ api surfaces 02 / 06 Available APIs Four specialized APIs for different integration scenarios Online Booking Public endpoints for booking widgets and client portals. No user authentication required Explore Recommended Business Management v2 Complete business operations API with improved design. New features are released here first. Recommended for new integrations Explore Business Management v1 Full-featured API for all business operations: scheduling, POS, CRM, inventory, finances, loyalty. Maintained for backward compatibility Explore Developer Tools Webhooks, dictionaries, and integration tools for marketplace app developers Explore Coming Soon — October 2026 Business Management v3 Contract prototype only — V3 is not ready and cannot serve API calls today. Paths and schemas may still change before the planned October 2026 release. View prototype \ reference 03 / 06 Getting Started The Altegio API allows third-party developers to perform most operations with platform data. When designing methods, we adhered to the REST architecture. All requests are encrypted with TLS 1.2+ Rate limit: 200 requests/min or 5 requests/sec per IP Base URL: https://api.alteg.io/api API Versioning The API uses URL path versioning. Both V1 and V2 are production-ready. New features may be released in V2 only. V1 endpoints are maintained for backward compatibility. V3 is a contract prototype coming in October 2026 and is not callable yet. V1 ( /v1/... ) — Stable, full-featured API V2 ( /v2/... ) — New endpoints with improved design V3 ( /v3/... ) — Coming soon in October 2026; contract prototype only Authentication API requests are authorized per RFC 6749 . Two authorization modes: Partner only (public endpoints): Authorization: Bearer < partner_token > Partner + User (business data): Authorization: Bearer < partner_token > , User < user_token > Get the Partner Token from your Developer Account . For the User Token, use the installed application's system user or authorize your own Business User . Their Location access and permissions can differ. Date & Time Format "2026-09-21T23:00:00.000-05:00" ISO 8601 format. Durations are in seconds (e.g., 900 = 15 min) \ support 04 / 06 Developer Support Our API team is here to help you build successful integrations. Whether you're troubleshooting an issue or planning a complex implementation, we provide technical guidance to keep your project moving forward. Direct API Support Get answers from engineers who built the API Integration Review Architecture feedback before you ship Priority Response Business-critical issues handled first Contact API Team api@alteg.io Include request URL, headers, body, and response for faster resolution Partner Program Earn with Altegio Connect clients to the platform and receive recurring commissions. Dedicated support, marketing materials, and API access included. Learn more Up to 50% commission \ use cases 05 / 06 What You Can Build Popular integration scenarios powered by Altegio API 🗓️ Booking Widget Embed scheduling into websites, mobile apps, or kiosks 🤖 AI Assistants Build booking agents with the API, or manage your marketplace app with MCP 📊 Analytics Dashboard Build custom reports, BI integrations, data warehouses 🔄 CRM Sync Two-way sync with Salesforce, HubSpot, custom CRMs 📱 White-label Apps Build branded booking apps for your clients 💳 POS Integration Connect payments, receipts, fiscal printers 📦 Inventory Automation Sync stock levels with suppliers, e-commerce 🔔 Custom Notifications Webhooks for real-time events, custom messaging \ data model 06 / 06 Core Entities The API allows you to work with most of the platform's entities. Note that there are inconsistencies in the technical terminology: method and variable names may differ between the user interface and the documentation Locations A Location is an individual business unit that operates within the platform. Each Location belongs to a Chain. For single-location businesses, the platform still creates a single-location Chain. Also known as: company, branch, filial, salon Learn more → Chains A Chain is a group of multiple Locations managed as a single business network. Chain-level settings, service catalogs, and loyalty programs may be inherited by all child Locations while each Location can still override them where needed. Also known as: groups, networks, salon_groups Learn more → Users A User is an account that provides authenticated access to one or more Locations. Access scope is defined by Roles, which are predefined sets of Access Rights. If a User does not have access to a module or method, the API returns HTTP 403. Users can also be linked to Chains for Chain-level requests. Most API methods require the User to be authorised and to have explicit access to the target Location. Also known as: account, login Learn more → Team Members and Positions A Team Member is an individual within a Location who participates in operational processes: provides Services within Appointments, creates or manages reservations, or works with financial and analytical data. Positions are logical groups of Team Members (similar to folders) that help structure staff by departments, functions, or specialisation. Also known as: employee, staff, staff_member, master Learn more → Resources Resources are limited items required to provide Services (rooms, chairs, devices, machines). A Resource cannot be used in parallel for multiple Appointments; it is reserved when a Service linked to that Resource is booked. Also known as: equipment, room Learn more → Schedule & Time Slots A Schedule is a set of time intervals during which a Team Member or Resource is available to provide Services. A Time Slot is a specific available interval within the Schedule that can be booked online for an Appointment with a Team Member. Also known as: timetable, availability Learn more → Appointments & Visits An Appointment is a scheduled time interval during which a specific Team Member provides one or more Services or sells Products to a specific Client. A Visit is a group of one or more Appointments that take place during a single Client presence at a Location. Grouping rules depend on the Location settings. Also known as: record, booking Learn more → Events An Event is a scheduled time slot for a group Service where multiple Clients can book simultaneously. Unlike individual Appointments, an Event has a capacity limit defining the maximum number of participants. Events are used for group classes, workshops, webinars, and any service that can serve multiple Clients at the same time. Also known as: activity, group event Learn more → Clients A Client is an individual who books, receives, or has received Services or Products from a Location. Client data is used for scheduling, communication, and analytics. Also known as: customer, visitor Learn more → Services and Service Categories A Service is a predefined type of work or procedure that can be provided to a Client by a Team Member within a Location. Each Service has key parameters such as duration, price (or price range), and applicable resources. Service Categories are logical groups used to organise Services for configuration, reporting, and client-facing catalogs. Also known as: treatments, procedures Learn more → Products and Product Categories A Product is a tangible or consumable item that can be sold to a Client or used as part of a Service. Product Categories are logical groups used to organise Products for inventory management, reporting, and sales operations. Also known as: goods, items Learn more → Inventories Inventories represent physical or logical Warehouses used to store and track Products and consumables. Inventory operations (receipts, write-offs, transfers) ensure that product usage in Visits is reflected in stock levels and financial reports. Also known as: storages, warehouses Learn more → Suppliers Suppliers and Partners are counterparties used in Inventory and Finance modules to track product purchases, settlements, and mutual transactions with external companies. Also known as: partners, vendors Learn more → Location Accounts Location Accounts are accounts (cash registers or bank accounts) attached to a specific Location. They are used to record payments for Visits, product sales, and other financial operations, and they define how money flows are grouped in financial reports. Also known as: cashdesks, cash registers Learn more → Payment Methods Payment methods define how payments are recorded in the system (cash, card, bank transfer, online acquiring, loyalty instruments). Each method is linked to specific Accounts and can have its own commission and reporting logic. Also known as: payment types Learn more → Payroll Rules Payroll rules define how staff compensation is calculated based on Visits, Products, Memberships, tips, and other metrics. They describe commission schemes, fixed payments, and deductions. Also known as: salary, wages Learn more → Client Cards A Client Card is a unified profile that stores balances, active memberships, gift cards, and participation in loyalty programs for a specific Client across one Location or an entire Chain. Also known as: loyalty cards Learn more → Memberships and their Types A Membership is a prepaid product that gives a Client the right to receive a set number of services or discounts over a defined period. Membership Types define the rules: which services are included, how many visits are available, validity period, and usage restrictions. Also known as: abonements, passes Learn more → Gift Cards and their Types A Gift Card is a prepaid value or service voucher that can be used to pay for Services and Products. Gift Card Types define how gift cards are sold, accounted for, and redeemed, including validity period and usage restrictions. Also known as: certificates, vouchers Learn more → Loyalty Programs Loyalty programs combine bonus accrual, cumulative discounts and referral programs to increase repeat visits and average spend. Any loyalty instrument must be linked to a specific Client Card so that bonuses, discounts, and balances are applied consistently across Visits. Also known as: rewards, bonuses Learn more → Client Accounts Client Accounts are internal balances (deposits) stored on the Client Card. They are used to prepay future Visits, store overpayments, or keep store credit that can be partially or fully redeemed in subsequent Visits and sales. Also known as: deposits Learn more → Subdivisions Subdivisions are higher-level groups used to organise Services across a Chain (for example, "Hair", "Nails", "Spa"). They help structure large catalogs, simplify analytics, and control visibility of Services in online booking. Also known as: departments Learn more → Custom Fields Custom fields are additional attributes configured by the Location to store extra data in Visits or other entities (for example, medical notes, internal IDs). They extend the standard schema without changing the core data model. Also known as: additional fields Learn more → Tags Tags allow users to group Clients, Appointments, or Events. They are used for analytics, targeted communications, and certain loyalty scenarios. Also known as: labels, segments, categories Learn more → Integrations HUB Integrations HUB is a catalog of external applications and services connected to Altegio (telephony, messaging, CRM, loyalty, etc.). It standardises how integrations are discovered, installed, configured, and monetised. Also known as: marketplace, apps Build with Integrations Hub MCP → Learn more →