Business Management (2.0.0)
Business Management requests use a Partner Token and, when business data is involved, a User Token:
Open the Altegio Marketplace and click Developer account. Complete the developer registration. Your Partner Token then appears automatically under Account settings → Account details.
Choose how you will obtain the User Token:
- Application system user: create an application in Developer Account. Under API Access, enter the system user's User ID, save it, copy the generated User Token, and configure the application's credentials, access rights, and connection settings. Then install and activate the application on a test Location. The token can access that Location only after the installation is active.
- Your own Business User: call the v1 user authorization endpoint with your Altegio login and password. Use
data.user_tokenfrom the response. No application installation is needed, but that Business User must already have access to the Location.
Send both values in the same header:
Authorization: Bearer <partner_token>, User <user_token>
An application's system user and your own Business User can have different Locations and permissions. A request that works with one token may therefore return 403 with the other. See How to Get API Keys for the complete beginner walkthrough.
Next-generation B2B API with improved design and consistency.
Base URL: https://api.alteg.io/api/v2
This API is in active development. New features and improvements are released here first. We recommend using this API for all new integrations.
Every request must include:
Accept: application/vnd.api.v2+jsonRequests without the v2 media type return 400. A charset parameter is accepted.
Location-scoped resources use /locations/{location_id}/....
Positions and Tags preserve the literal company_id path parameter name for SDK compatibility, but its value is the Location identifier. The legacy /companies/{company_id}/positions and /companies/{company_id}/tags paths remain accepted as compatibility aliases.
Legacy path segments are accepted as compatibility aliases of the canonical ones: companies (locations), staff (team_members), records (appointments), activities (events), goods (products), good_categories (product_categories), attendance_good_items (attendance_product_items), and salon_groups (chains). A request through a legacy segment reaches the same handler and additionally returns Deprecation: @1782864000 (2026-07-01T00:00:00Z), Sunset: Mon, 01 Mar 2027 00:00:00 GMT, and Link: <https://developer.alteg.io/en/b2b-v3/openapi>; rel="deprecation" (RFC 9745, RFC 8594). Canonical URLs do not return these headers.
Use canonical names such as location_id, chain_id, team_member_id, appointment_id, and product_id for top-level query-string and request-body parameters. V2 accepts the corresponding legacy names in both directions for compatibility, but canonical names are recommended for new integrations.
Alias expansion is not recursive: nested request fields must use the literal names shown by each endpoint. Responses are not transformed and retain their literal wire fields and JSON:API resource type values; response schemas and examples show those exact names.