Skip to content
/
Create Recurring Appointm...

Business Management (1.0.0)

Full-featured B2B API for business operations.

Base URL: https://api.alteg.io/api

⚠️ Version Status

V1 will be gradually deprecated. We recommend using V2 API for new integrations. V1 endpoints are maintained for backward compatibility, but new features will be released in V2 only.

Authentication

Requires both partner and user authorization:

Authorization: Bearer <partner_token>, User <user_token>
Download OpenAPI description
openapi.json
openapi.yaml
Overview
License
Altegio API Agreement
Terms of Service
Languages
Servers
Mock server
https://developer.alteg.io/_mock/en/b2b-v1/openapi/
Production
https://api.alteg.io/api/v1/

Authentication B2B

User authentication and session management for B2B integrations

Operations

Locations

Manage business locations (salons, clinics, etc.)

Operations

Services

Service catalog management including categories and team member assignments

Operations

Team Members

Staff management including positions and scheduling

Operations

Clients

Client database management with comments, files, and visit history

Operations

Users & Permissions

User account management and role-based access control

Operations

Appointments

Booking records and visit management

Operations

Leave a Comment

Request

Security
BearerPartnerUser
Path
location_idnumberrequired

location ID

team_member_idnumberrequired

team member ID, specify when creating a review for a team member

Headers
Acceptstringrequired

e.g. application/vnd.api.v2+json

Example: application/vnd.api.v2+json
Content-Typestringrequired

application/json

Authorizationstringrequired

Bearer partner_token, User user_token

Bodyapplication/jsonrequired
marknumberrequired

Rating from 1 to 5

Example: 4
namestringrequired

Username to be displayed on the review page

Example: "Victor"
textstringrequired

Feedback text

Example: "Everything is very bad!"
curl -i -X POST \
  'https://developer.alteg.io/_mock/en/b2b-v1/openapi/comments/{location_id}/{team_member_id}' \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "mark": 4,
    "text": "Everything is very bad!",
    "name": "Victor"
  }'

Responses

Created

Bodyapplication/json
successboolean

Execution success status (true)

Example: true
dataArray of objects

Array of objects with data

Example: [{"id":18437,"salon_id":12345,"type":1,"master_id":8864,"text":"Fine!","date":"2026-09-21T23:00:00.000-05:00","rating":4,"user_id":157169,"user_name":"Victor Sitnikov","user_avatar":"/images/no-master.png","record_id":100001}]
metaArray of objects

Metadata (empty array)

Example: []
Response
application/json
{
  "success": true,
  "data": {
    "type": 1,
    "master_id": 8864,
    "id": 18437,
    "text": "Everything is very bad!",
    "date": "2026-09-21T23:00:00.000-05:00",
    "rating": 4,
    "user_id": 157169,
    "user_name": "Victor",
    "user_avatar": "/images/no-master.png"
  },
  "meta": []
}

Create Recurring Appointments

Request

Creates a recurring appointment series for a client based on an event schedule. Automatically generates future appointments according to the schedule pattern.

Security
BearerPartnerUser
Path
location_idnumberrequired

ID of a location.

Example: 123
schedule_idintegerrequired

ID of a schedule.

Example: 123
Headers
Acceptstringrequired

Should be equal to application/vnd.api.v2+json

Example: application/vnd.api.v2+json
Content-Typestringrequired

Should be equal to application/json

Example: application/json
Bodyapplication/json
client_idnumberrequired

ID of client for creating a client schedule.

Example: 123
schedule_days_idsArray of numbers[ 1 .. 7 ] itemsrequired

IDs of schedule series, min of 1 series, max of 7 series.

Example: [123]
comer_idnumber

ID of client`s comer for creating a client schedule.

Example: 123
curl -i -X POST \
  https://developer.alteg.io/_mock/en/b2b-v1/openapi/company/123/schedules/123/client_schedules \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "client_id": 123,
    "comer_id": 123,
    "schedule_days_ids": [
      123
    ]
  }'

Responses

Created

Bodyapplication/json
successboolean(response_success_true_object)

Response status.

dataobject(timetable_event_schedule_client_schedule)

Data for an existing client schedule in a location.

metaArray of objects or arrays or object(response_meta_empty_object)

Additional response data (empty object or empty array)

Response
application/json
{
  "success": true,
  "data": {
    "id": 123,
    "loyalty_abonement_id": null,
    "final_day": "2022-01-01 12:12:12",
    "days": [ … ]
  },
  "meta": {}
}

Update Recurring Appointments

Request

Updates a recurring appointment series by attaching or detaching schedule days. This creates or removes future appointments accordingly.

Security
BearerPartnerUser
Path
location_idnumberrequired

ID of a location.

Example: 123
schedule_idintegerrequired

ID of a schedule.

Example: 123
client_schedule_idnumberrequired

ID of a client schedule.

Example: 123
Headers
Acceptstringrequired

Should be equal to application/vnd.api.v2+json

Example: application/vnd.api.v2+json
Content-Typestringrequired

Should be equal to application/json

Example: application/json
Bodyapplication/json
schedule_days_idsArray of numbers[ 1 .. 7 ] itemsrequired

IDs of schedule series, min of 1 series, max of 7 series.

Example: [123]
curl -i -X PATCH \
  https://developer.alteg.io/_mock/en/b2b-v1/openapi/company/123/schedules/123/client_schedules/123 \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "schedule_days_ids": [
      123
    ]
  }'

Responses

OK

Bodyapplication/json
successboolean(response_success_true_object)

Response status.

dataobject(timetable_event_schedule_client_schedule)

Data for an existing client schedule in a location.

metaArray of objects or arrays or object(response_meta_empty_object)

Additional response data (empty object or empty array)

Response
application/json
{
  "success": true,
  "data": {
    "id": 123,
    "loyalty_abonement_id": null,
    "final_day": "2022-01-01 12:12:12",
    "days": [ … ]
  },
  "meta": {}
}

Events

Group events and class management

Operations

Schedule & Resources

Timetables, schedules, and resource allocation

Operations

Products

Product catalog and categories

Operations

Inventory

Stock management, storage operations, and tech cards

Operations

Sales

Sales transactions and document management

Operations

Payments

Payment processing, accounts, and KKM transactions

Operations

Notifications

SMS and email notifications to clients

Operations

Online Booking Settings

Configure online booking behavior and forms

Operations

Analytics & Reports

Business analytics, charts, and Z-reports

Operations

Tags

Label management for categorizing entities (deprecated, use v2)

Operations

Deposits

Client deposit accounts and operations

Operations

Loyalty Cards

Loyalty card types, issuance, and manual transactions

Operations

Subscriptions & Certificates

Membership subscriptions and gift certificates

Operations

Loyalty Programs

Discount programs, referral programs, and loyalty transactions

Operations

Salary

Staff salary calculations, payroll, and schemes

Operations

Notification Settings

Configure notification types and user preferences

Custom Fields

Custom field definitions for various entities

Operations

Chain Management

Multi-location chain operations and clients

Operations

Chain Loyalty Programs

Chain-level loyalty programs and transactions

Operations

Fiscalization

Tax system integration and KKM callbacks

Operations

Utilities

License info, phone validation, images, and tips

Operations