Skip to content
/
Delete certificate type

Altegio REST API (1.0.1)

This is an official document describing the interaction with the Altegio business managment platform. API allows third-party developers to perform most operations with the Altegio data. When designing methods, we tried to adhere to the REST architecture.

  • All interaction with protocol are transpire by TLS encryption (from 1.2 version)
  • Limits are 200 requests per minute or 5 requests per second per IP address
  • URL API: https://api.alteg.io/api If you encounter difficulties when working with the API, please carefully review the documentation, including the required headers, parameters, and the structure of the request body in the JSON example.

If you're having trouble resolving the issue on your own, feel free to contact us at api@alteg.io. Please include the request URL, headers, request body, and the response you received in your message.

API Versioning

The API uses URL path versioning. Currently available versions:

  • V1 (/v1/...) - Stable, full-featured API - V2 (/v2/...) - New endpoints with improved design Both versions are production-ready. New features may be released in V2 only. V1 endpoints are maintained for backward compatibility. Base URL: https://api.alteg.io/api Example requests: - V1: GET https://api.alteg.io/api/v1/companies - V2: GET https://api.alteg.io/api/v2/companies/{id}/tags

Integration cases with Altegio

  • Data exchange with automation, accounting or CRM software
  • Integration of Online Booking into third-party websites and mobile applications. Allows embedding of Online Booking forms into external platforms, such as business catalogs, branded apps, and other partner services.
  • Data collection and analysis for business intelligence systems / Development of custom reporting and analytics tools
  • Chat bots and virtual assistants for appointment scheduling and client management

General description of data exchange with Altegio

The Altegio integration API includes two groups of methods:

  • Methods that require both user authorization and partner authorization
  • Methods that require partner authorization only (no user authorization)

API Request Authorization

Accessing both the first and second groups of methods requires partner authorization. I.e. passing the partner's unique hash key. API requests are authorized in accordance with RFC 6749 "Resource Owner Password Credentials Grant". When making API requests the HTTP authorization header must include the access key in the following format:

Authorization: Bearer <partner token>

To obtain this key, you need to register in the marketplace – it will be located in the 'Developer account' "Account settings" under "Account details" tab.

To get the user API key, use the auth method, or, if you are creating an integration application, use the key located in an application's settings under the "API Access" section. The key itself must also be sent in the request header (after the partner key, separated by a comma):

Authorization: Bearer <partner token>, User <user token>

Whether user authorization is required to work with specific entities is indicated in the data format descriptions and sample queries. Please note that not all users have access to all methods and data, depending on their assigned access rights.

Date and time

The most of dates in the API are represented as strings in ISO 8601 format. Exluding cases specified otherwise in outdated or deprecated methods.

"2026-09-21T23:00:00.000-05:00"

Service durations and other time-related values are provided in seconds. For example, a 15-minute service should be represented as:

{ "length": 900 }

Core Entities of the Altegio API

The API allows to work with most of the platform's entities. However, please note that there are inconsistencies in the technical terminology: method and variable names, as well as terminology, may differ between the user interface and the documentation

Locations

Locations in the product knowledge base

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

Chains

Chains in the product knowledge base

A Chain is a group of multiple Locations managed as a single business network. Chain-level settings, promotions, service catalogs, and loyalty rules may be inherited by all child Locations while each Location can still override them where needed.

Also known as: groups, networks, salon_groups

Users

Users in the product knowledge base

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, which provide a different set of access rights and are required for certain Chain-level requests. Each User is linked to one Team Member within a Location and may be linked to different Team Members across multiple Locations. Operational context (available Services, Schedule, permissions) depends on the current Location and Team Member binding. Most API methods require the User to be authorised (a valid token obtained) and to have explicit access to the target Location.

Team members and Positions

Team members in the product knowledge base · Positions in the product knowledge base

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 (for example, a professional, cashier, administrator, or accountant). Team Members do not directly define access rights in the API, but they determine the business role and workload of a person inside a Location. Positions are logical groups of Team Members (similar to folders) that help structure staff by departments, functions, or specialisation. In some configurations, Positions are used to filter available reports.

Also known as: employee, staff, staff_member, master

Resources

Resources in the product knowledge base

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.

Schedule & Time Slots

Schedule in the product knowledge base

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.

Appointments & Visits

Visits in the product knowledge base

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

Events

Events in the product knowledge base

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 with a single Team Member.

Also known as: activity, group event

Clients

Clients in the product knowledge base

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.

Services and Service Categories

Services in the product knowledge base

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.

Products and Product Categories

Products in the product knowledge base

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

Inventories

Inventory in the product knowledge base

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

Suppliers

Suppliers in the product knowledge base

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

Location accounts

Location accounts in the product knowledge base

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

Payment methods

Payment methods in the product knowledge base

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.

Payroll rules

Payroll in the product knowledge base

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.

Client cards

Client cards in the product knowledge base

A Client Card is a unified profile that stores balances, active memberships, certificates, and participation in loyalty programs for a specific Client across one Location or an entire Chain.

Memberships and their Types

Memberships in the product knowledge base

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

Certificates and their Types

Certificates in the product knowledge base

A Certificate is a prepaid value or service voucher that can be used to pay for Services and Products. Certificate Types define how certificates are sold, accounted for, and redeemed, including validity period and usage restrictions.

Loyalty programs

Loyalty programs in the product knowledge base

Loyalty programs combine bonus accrual, cumulative discounts and referral promotions 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.

Client accounts

Client accounts in the product knowledge base

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

Subdivisions

Subdivisions in the product knowledge base

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.

Custom fields

Custom fields in the product knowledge base

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

Tags

Tags in the product knowledge base · Filters in the product knowledge base

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

Integrations HUB

Integrations in the product knowledge base

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.

Download OpenAPI description
index.json
index.yaml
Overview
License
Altegio API Agreement
Terms of Service
Languages
Servers
Mock server
https://developer.alteg.io/_mock/en/
https://api.alteg.io/api/

Authentication B2C

End-customer authentication methods. Get access tokens required for some API operations.

Operations

Online Booking

Public APIs for integrating online booking into third-party websites and mobile applications.

Operations

Client Personal Cabinet

End-customer account. Manage user profile, appointments, and other operations.

Operations

Authentication B2B

SaaS users authentication methods. Get access tokens required for all API operations.

Operations

Locations

Locations in the product knowledge base

Location management. Create, read, update locations and their settings.

Operations

Services

Services in the product knowledge base

Service and service category management. Define services offered by your locations.

Operations

Team Members

Team members in the product knowledge base · Positions in the product knowledge base

Team member management, including positions, service assignments, and team member profiles.

Operations

Clients

Clients in the product knowledge base

Client management including search, bulk operations, files, comments, and visit history.

Operations

Users & Permissions

Users in the product knowledge base

User account management, roles, permissions, and invitations. Control access to location features.

Operations

Appointments

Visits in the product knowledge base

Appointment and visit management.

Key concepts:

  • Appointment (record) — A single scheduled service for a client with a specific team member at a specific time
  • Visit — A container that groups multiple appointments when a client books several services in one session

Example: Client books haircut + coloring → 1 visit containing 2 appointments

This section covers creating, modifying, and managing both individual appointments and visit containers.

Operations

Events

Events in the product knowledge base

Manage Events — scheduled time slots for group Services where multiple Clients can book simultaneously. Create, update, search, and duplicate Events with customizable capacity, duplication strategies, and Team Member assignments.

Operations

Schedule & Resources

Schedule in the product knowledge base · Resources in the product knowledge base

Work schedules, available time slots, resources, and timetable management for team members and facilities.

Operations

Products

Products in the product knowledge base

Product catalog management. Define products available for sale and organize them into categories.

Operations

Inventory

Inventory in the product knowledge base

Stock management including storage locations, inventory documents, stock movements, and consumables tracking.

Operations

Sales

Sales documents and receipts. View and manage point-of-sale transactions.

Operations

Payments

Payment methods in the product knowledge base · Accounts in the product knowledge base

Financial operations including location accounts, payment transactions, and all monetary movements.

Operations

Notifications

Send SMS, Email or other notifications to clients. Configure notification preferences and settings for users and notification types.

Operations

Online Booking Settings

Manage custom booking forms and their configurations for online appointment scheduling.

Operations

Analytics & Reports

Business analytics and statistical reports for business intelligence.

Operations

Tags

Tags in the product knowledge base

Custom tags for clients, appointments, and events.

Operations

Deposits

Client accounts in the product knowledge base

Client deposit account management and operations.

Operations

Loyalty Cards

Client cards in the product knowledge base

Loyalty card management including card types, manual transactions, and card assignments.

Operations

Subscriptions & Certificates

Memberships in the product knowledge base · Certificates in the product knowledge base

Membership and certificate management including creation, freezing, and balance operations.

Operations

Loyalty Programs

Loyalty programs in the product knowledge base

Loyalty programs and loyalty transaction management.

Operations

Salary

Payroll in the product knowledge base

Salary calculations, payroll management, and compensation tracking for team members.

Operations

Custom Fields

Custom fields in the product knowledge base

Additional custom field definitions for extending entity data structures.

Operations

Chain Management

Chains in the product knowledge base

Chain-level operations for managing multiple locations within a business chain.

Operations

Chain Loyalty Programs

Loyalty programs in the product knowledge base

Chain-level loyalty program management including programs, transactions, and message templates.

Operations

Update certificate type

Request

Updates an existing certificate type at the chain level.

All fields from creation are required. Use GET first to retrieve current values, then modify needed fields and send complete object.

Note: Cannot update certificate types that have already been issued.

Security
bearer
Path
chain_idintegerrequired

Chain ID

Example: 706028
type_idintegerrequired

Certificate type ID

Example: 289056
Headers
Acceptstringrequired
Default application/vnd.api.v2+json
Content-Typestringrequired
Default application/json
Authorizationstringrequired

Bearer {partner_token}, User {user_token}

Bodyapplication/jsonrequired
titlestringrequired

Certificate type name

Example: "Gift Certificate 1500"
balancenumberrequired

Certificate face value

Example: 1500
is_multibooleanrequired

true = multiple use, false = single use

Example: true
item_type_idintegerrequired

Usage restrictions (0-4)

Enum01234
Example: 0
is_allow_empty_codebooleanrequired

Allow selling without code?

Example: false
balance_edit_type_idintegerrequired

Balance editability (1 = editable, 2 = not editable)

Enum12
Example: 1
service_idsArray of integersrequired

Specific service IDs (empty if no restriction)

Example: []
salon_idsArray of integersrequired

Location IDs where certificate is valid

Example: [720441]
expirationobjectrequired

Expiration settings

expiration.​type_idintegerrequired

Expiration type: 0 = none, 1 = fixed date, 2 = period from sale

Enum012
Example: 2
expiration.​datestring(date-time)

Fixed expiration date (ISO 8601, required if type_id = 1)

Example: "2026-12-31T23:59:59+00:00"
expiration.​timeoutinteger

Duration value (required if type_id = 2)

Example: 6
expiration.​timeout_unit_idinteger

Duration unit (required if type_id = 2): 1 = day, 2 = week, 3 = month, 4 = year

Enum1234
Example: 3
online_saleobjectrequired

Online sale settings

online_sale.​is_enabledbooleanrequired

Enable online purchase?

Example: false
online_sale.​titlestring

Title for online store

Example: "Gift Certificate"
online_sale.​descriptionstring

Description for online store

Example: "Perfect gift for any occasion"
online_sale.​pricenumber

Online sale price

Example: 1500
category_idinteger or null

Service category restriction (null = no restriction)

Example: null
curl -i -X PUT \
  https://developer.alteg.io/_mock/en/v1/chain/706028/loyalty/certificate_types/289056 \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: YOUR_API_KEY_HERE' \
  -H 'Content-Type: application/json' \
  -d '{
    "title": "Gift Certificate 1500",
    "balance": 1500,
    "is_multi": true,
    "item_type_id": 0,
    "is_allow_empty_code": false,
    "category_id": null,
    "balance_edit_type_id": 1,
    "service_ids": [],
    "salon_ids": [
      720441
    ],
    "expiration": {
      "type_id": 2,
      "date": "2026-12-31T23:59:59+00:00",
      "timeout": 6,
      "timeout_unit_id": 3
    },
    "online_sale": {
      "is_enabled": false,
      "title": "Gift Certificate",
      "description": "Perfect gift for any occasion",
      "price": 1500
    }
  }'

Responses

Certificate type updated successfully

Bodyapplication/json
successboolean
Example: true
dataobject
metaArray of arrays
Example: []
Response
application/json
{
  "success": true,
  "data": {
    "id": 289056,
    "title": "Gift Certificate 1500",
    "balance": 1500,
    "is_multi": true,
    "company_group_id": 706028,
    "category_id": null,
    "weight": 1,
    "item_type_id": 0,
    "expiration_type_id": 2,
    "expiration_date": null,
    "expiration_timeout": 6,
    "expiration_timeout_unit_id": 3,
    "balance_edit_type_id": 1,
    "is_allow_empty_code": false,
    "is_serial_number_limited": false,
    "is_archived": false,
    "date_archived": null,
    "online_sale_is_enabled": false,
    "online_sale_title": "Gift Certificate 1500",
    "online_sale_description": "",
    "online_sale_price": 0,
    "online_sale_image": null,
    "released_total": 0,
    "item_type": { … },
    "service_ids": [],
    "salon_ids": [ … ]
  },
  "meta": []
}

Delete certificate type

Request

Deletes a certificate type from the chain.

Warning: This action cannot be undone. Certificate types that have issued certificates cannot be deleted.

Security
bearer
Path
chain_idintegerrequired

Chain ID

Example: 706028
type_idintegerrequired

Certificate type ID to delete

Example: 289056
Headers
Acceptstringrequired
Default application/vnd.api.v2+json
Authorizationstringrequired

Bearer {partner_token}, User {user_token}

curl -i -X DELETE \
  https://developer.alteg.io/_mock/en/v1/chain/706028/loyalty/certificate_types/289056 \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: YOUR_API_KEY_HERE'

Responses

Certificate type deleted successfully

Bodyapplication/json
successboolean
Example: true
datanull
metaArray of arrays
Example: []
Response
application/json
{
  "success": true,
  "data": null,
  "meta": []
}

Create a Chain Promotion

Request

Security
bearer and user
Path
chain_idintegerrequired

Chain ID

Query
includestring

Include additional resources in the answer

Enum"applicable_items""rules""companies""loyalty_card_types""on_changed_notification_template""on_expiration_notification_template"
Headers
Acceptstringrequired

application/vnd.api.v2+json

Content-Typestringrequired

application/json

Authorizationstringrequired

Bearer partner_token, User user_token

Bodyapplication/jsonrequired
company_idsArray of integers(int32)required

Identifiers of locations where the promotion is valid

Example: [49]
good_item_typestringrequired

Type of application to products

Enum"any_allowed""not_allowed""custom_allowed"
Example: "not_allowed"
rulesArray of objects(loyalty_program_rule_request)required

Rules for determining the value of the bonus or discount (only one rule is allowed for fixed promotions)

Example: [{"parameter":10,"value":2.5,"service_id":0},{"parameter":30,"value":7.5,"service_id":0}]
rules[].​parameterinteger(int32)

Rule Threshold (0 for Fixed Stock Types)

Example: 10
rules[].​valuenumber(double)

The value of the discount or bonus

Example: 2.5
rules[].​service_idinteger(int32)

Service ID (only for "Discount by condition" promotion)

service_item_typestringrequired

Type of application to services

Enum"any_allowed""not_allowed""custom_allowed"
Example: "custom_allowed"
titlestringrequired

Share name

Example: "Cumulative discount for some services and not for goods"
typestringrequired

Promotion type

Enum"discount_static""discount_accumulative_visits""discount_accumulative_sold""discount_accumulative_paid""cashback_static_sold""cashback_static_paid""cashback_accumulative_paid""cashback_accumulative_sold""cashback_accumulative_paid_visits""cashback_accumulative_sold_visits"
Example: "discount_accumulative_paid"
value_unitstringrequired

Bonus or discount measurement unit (percentage, fixed amount)

Enum"percent""amount"
Example: "percent"
usage_limitinteger(int32)

Limit on the number of applications (only for cashback)

visit_multiplicityinteger(int32)

Multiplicity of application by visits (only for cashback)

sold_items_multiplicityinteger(int32)

How many services you need to pay to get a discount on promotional services (only for the promotion type "Discount by condition")

expiration_timeoutinteger(int32)

Expiration date of bonuses or discounts

Example: 6
expiration_timeout_unitstring

The unit of measurement for the expiration date of bonuses or discounts

Enum"day""week""month""year"
Example: "month"
expiration_notification_timeoutinteger(int32)

How many days before the bonus or discount expires, a notification must be sent to the client

Example: 7
params_source_typestring

Where to get the client's history to calculate the size of the bonus or discount (for accumulation promotions or conditional discounts)

Enum"loyalty_card""active_companies""chain"
Example: "chain"
history_start_datestring(date)

From what date to take into account the client's history to calculate the size of the bonus or discount (for accumulative promotions or conditional discounts)

Example: "2026-09-21"
loyalty_card_type_idsArray of integers(int32)

Identifiers of types of cards for which the promotion is valid

Example: [51,29]
on_changed_notification_templateobject(loyalty_notification_message_template_request)

Body of the request to bind the loyalty notification template

Example: {"type":"custom","body":"Your discount has changed"}
on_expiration_notification_templateobject(loyalty_notification_message_template_request)

Body of the request to bind the loyalty notification template

Example: {"type":"big"}
allowed_service_idsArray of integers(int32)

Service and service category identifiers (if application type is set for some services)

Example: [53,92]
allowed_good_idsArray of integers(int32)

Item IDs (if application type is set for some items)

Example: []
allowed_good_category_idsArray of integers(int32)

Product category identifiers (if application type is set for some products)

Example: []
curl -i -X POST \
  'https://developer.alteg.io/_mock/en/v1/chain/{chain_id}/loyalty/programs?include=applicable_items' \
  -H 'Accept: string' \
  -H 'Authorization: YOUR_API_KEY_HERE' \
  -H 'Content-Type: application/json' \
  -d '{
    "title": "Cumulative discount for some services and not for goods",
    "type": "discount_accumulative_paid",
    "service_item_type": "custom_allowed",
    "good_item_type": "not_allowed",
    "allowed_service_ids": [
      53,
      92
    ],
    "allowed_good_ids": [],
    "allowed_good_category_ids": [],
    "value_unit": "percent",
    "usage_limit": 0,
    "visit_multiplicity": 0,
    "sold_items_multiplicity": 0,
    "expiration_timeout": 6,
    "expiration_timeout_unit": "month",
    "expiration_notification_timeout": 7,
    "params_source_type": "chain",
    "history_start_date": "2026-09-21",
    "loyalty_card_type_ids": [
      51,
      29
    ],
    "on_changed_notification_template": {
      "type": "custom",
      "body": "Your discount has changed"
    },
    "on_expiration_notification_template": {
      "type": "big"
    },
    "rules": [
      {
        "parameter": 10,
        "value": 2.5,
        "service_id": 0
      },
      {
        "parameter": 30,
        "value": 7.5,
        "service_id": 0
      }
    ],
    "company_ids": [
      49
    ]
  }'

Responses

OK

Bodyapplication/json
idinteger(int32)

Stock ID

Example: 34
titlestring

Share name

Example: "Cumulative discount for some services and not for goods"
typestring

Promotion type

Enum"discount_static""discount_accumulative_visits""discount_accumulative_sold""discount_accumulative_paid""cashback_static_sold""cashback_static_paid""cashback_accumulative_paid""cashback_accumulative_sold""cashback_accumulative_paid_visits""cashback_accumulative_sold_visits"
Example: "discount_accumulative_paid"
service_item_typestring

Type of application to services

Enum"any_allowed""not_allowed""custom_allowed"
Example: "custom_allowed"
good_item_typestring

Type of application to products

Enum"any_allowed""not_allowed""custom_allowed"
Example: "not_allowed"
value_unitstring

Bonus or discount measurement unit (percentage, fixed amount)

Enum"percent""amount"
Example: "percent"
usage_limitinteger(int32)

Limit on the number of applications (only for cashback)

visit_multiplicityinteger(int32)

Multiplicity of application by visits (only for cashback)

sold_items_multiplicityinteger(int32)

How many services you need to pay to get a discount on promotional services (only for the type of promotion "Discount by condition")

expiration_timeoutinteger(int32)

Expiration date of bonuses or discounts

Example: 6
expiration_timeout_unitstring

The unit of measurement for the expiration date of bonuses or discounts

Enum"day""week""month""year"
Example: "month"
expiration_notification_timeoutinteger(int32)

How many days before the bonus or discount expires, a notification must be sent to the client

Example: 7
params_source_typestring

Where to get the client's history to calculate the size of the bonus or discount (for accumulation promotions or conditional discounts)

Enum"loyalty_card""active_companies""chain"
Example: "chain"
history_start_datestring(date)

From what date to take into account the client's history to calculate the size of the bonus or discount (for accumulative promotions or conditional discounts)

Example: "2026-09-21"
on_changed_notification_template_idinteger(int32)

Notification template ID when changing bonus or discount

Example: 55
on_expiration_notification_template_idinteger(int32)

Identifier of the notification template when a bonus or discount burns

Example: 84
loyalty_card_typesArray of objects(loyalty_card_type)

Type of cards for which the promotion is valid (on request)

Example: [{"id":51,"title":"Card type 1"},{"id":29,"title":"Card type 2"}]
on_changed_notification_templateobject(loyalty_notification_message_template)

Loyalty notification template

Example: {"id":55,"type":"custom","body":"Your discount has changed","message_type":"loyalty_discount_changed"}
on_expiration_notification_templateobject(loyalty_notification_message_template)

Loyalty notification template

Example: {"id":84,"type":"big","body":"Detailed text about discount burning","message_type":"loyalty_discount_expiration"}
rulesArray of objects(loyalty_program_rule)

Rules for determining the value of the bonus or discount (only one rule is allowed for fixed promotions) (on request)

Example: [{"id":94,"parameter":10,"value":2.5,"loyalty_program_id":34,"loyalty_type_id":3,"service_id":0},{"id":74,"parameter":30,"value":7.5,"loyalty_program_id":34,"loyalty_type_id":3,"service_id":0}]
companiesArray of objects(company)

Locations where the promotion is valid (on request)

Example: [{"id":49,"title":"Location","country":"United States","country_id":5,"city":"New York","city_id":83,"phone":"+13155550175","timezone":"America/New_York","address":"Location address","coordinate_lat":40.73061,"coordinate_lng":18.63}]
applicable_itemsArray of objects(loyalty_entity_attendance_item)

Related entities for selective application of the promotion (on request)

Example: [{"id":53,"title":"Service category 1","is_service":true,"is_category":true},{"id":92,"title":"Service category 2","is_service":true,"is_category":true}]
Response
application/json
{
  "id": 34,
  "title": "Cumulative discount for some services and not for goods",
  "type": "discount_accumulative_paid",
  "service_item_type": "custom_allowed",
  "good_item_type": "not_allowed",
  "value_unit": "percent",
  "usage_limit": 0,
  "visit_multiplicity": 0,
  "sold_items_multiplicity": 0,
  "expiration_timeout": 6,
  "expiration_timeout_unit": "month",
  "expiration_notification_timeout": 7,
  "params_source_type": "chain",
  "history_start_date": "2026-09-21",
  "on_changed_notification_template_id": 55,
  "on_expiration_notification_template_id": 84,
  "loyalty_card_types": [
    { … },
    { … }
  ],
  "on_changed_notification_template": {
    "id": 55,
    "type": "custom",
    "body": "Your discount has changed",
    "message_type": "loyalty_discount_changed"
  },
  "on_expiration_notification_template": {
    "id": 84,
    "type": "big",
    "body": "Detailed text about discount burning",
    "message_type": "loyalty_discount_expiration"
  },
  "rules": [
    { … },
    { … }
  ],
  "companies": [
    { … }
  ],
  "applicable_items": [
    { … },
    { … }
  ]
}

Fiscalization

Fiscal integration for tax compliance. Manage fiscal transactions, print fiscal receipts, and configure tax systems.

Operations

Utilities

Utility endpoints for validation, GDPR, image management, licensing, and tips configuration.

Operations

Marketplace

Integrations in the product knowledge base

Application marketplace integration for third-party applications.

Integration workflow:

  • Partner provides domain name, registration URL, and callback URL
  • User authorizes and is redirected to partner registration page
  • Partner redirects back to Altegio after successful registration
  • Partner confirms service activation via payment callback
Operations

Webhooks

Webhook configuration for receiving real-time event notifications from Altegio.

Operations

VoIP Integration

VoIP integration for managing phone calls and call history within Altegio.

Operations

Dictionaries

Reference data including countries, cities, business types, and industry classifications.

Operations