Skip to content
/
Validate Booking Paramete...

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

Get a List of Time Slots Available for Booking

Request

The sessions available for booking object has the following fields:

FieldTypeDescription
timestringSession time (17:30 for example)
session_lengthnumberSession duration in seconds
datetimedatetimeDate and time of the session in ISO8601 format (must be passed when creating the appointment)

The following filters are available:

  • service_ids: Array of service IDs. If you need sessions, when can you book these services
Security
bearer
Path
location_idnumberrequired

location ID

datestringrequired

date in iso8601 format. Filter by booking date (eg '2026-09-30')

team_member_idnumberrequired

team member ID. Filter by team member ID Default: 0

Query
service_ids[]string

Service ID. Filter by the list of service identifiers

Headers
Acceptstringrequired

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

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

application/json

Authorizationstringrequired

Bearer partner_token

curl -i -X GET \
  'https://developer.alteg.io/_mock/en/v1/book_times/{location_id}/{team_member_id}/{date}?service_ids%5B%5D=string' \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: YOUR_API_KEY_HERE' \
  -H 'Content-Type: string'

Responses

OK

Bodyapplication/json
successboolean

Execution success status (true)

Example: true
dataArray of objects

Array of objects with data

Example: [{"time":"12:00","seance_length":3600,"datetime":"2026-09-21T23:00:00.000-05:00"},{"time":"13:00","seance_length":3600,"datetime":"2026-09-21T23:00:00.000-05:00"},{"time":"14:00","seance_length":3600,"datetime":"2026-09-21T23:00:00.000-05:00"},{"time":"15:00","seance_length":3600,"datetime":"2026-09-21T23:00:00.000-05:00"},{"time":"16:00","seance_length":3600,"datetime":"2026-09-21T23:00:00.000-05:00"}]
metaArray of objects

Metadata (empty array)

Example: []
Response
application/json
{
  "success": true,
  "data": [
    { … },
    { … },
    { … },
    { … },
    { … }
  ],
  "meta": []
}

Validate Booking Parameters

Request

After generating the appointment parameters, you can validate them to ensure the appointment can be successfully created.

The JSON object containing the Online Booking parameters includes the following fields:

FieldTypeMandatoryDescription
appointmentsArray of objectsYESBooking options (services, team members...)

The appointments array consists of objects that have the following fields:

FieldTypeMandatoryDescription
idnumberYesAppointment ID for post-save feedback (see response to request).
servicesarray of numbersNOArray of IDs of the services the client wants to sign up for
staff_idnumberYESID of the team member the client wants to book with (0 if any team member is selected)
datetimedatetimeYESSession date and time in ISO8601 format (passed for each session in the book_times resource)

In response to the parameter check request, an empty response with the code 201 will be returned if the booking parameters are in order and bookings can be created:

If the response is JSON with an HTTP code other than 201, then the booking parameters are out of order, and bookings cannot be created.

The server may return the following errors during appointment creation:

  1. Selected time slot is already taken. Returned with HTTP status code 422 and error code 433.

  2. No team members available for booking. Occurs if a default team member was selected but none are available. Returned with HTTP status code 422 and error code 436.

  3. Booking time conflict within the same request. One of the selected booking times overlaps with another booking created in the same request. Returned with HTTP status code 422 and error code 437, including the conflicting booking’s id in the appointments array.

  4. Service not available for booking The selected service is no longer available (e.g. removed by the location). Returned with HTTP status code 422 and error code 438.

Security
bearer
Path
location_idnumberrequired

location ID

Headers
Acceptstringrequired

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

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

application/json

Authorizationstringrequired

Bearer partner_token

Bodyapplication/jsonrequired
appointmentsArray of objectsrequired

appointment options (services, team members...)

Example: [{"id":1,"services":[331],"staff_id":6544,"datetime":"2026-09-21T23:00:00.000-05:00"},{"id":2,"services":[99055],"staff_id":6544,"datetime":"2026-09-21T23:00:00.000-05:00"}]
curl -i -X POST \
  'https://developer.alteg.io/_mock/en/v1/book_check/{location_id}' \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: YOUR_API_KEY_HERE' \
  -H 'Content-Type: application/json' \
  -d '{
    "appointments": [
      {
        "id": 1,
        "services": [
          331
        ],
        "staff_id": 6544,
        "datetime": "2026-09-21T23:00:00.000-05:00"
      },
      {
        "id": 2,
        "services": [
          99055
        ],
        "staff_id": 6544,
        "datetime": "2026-09-21T23:00:00.000-05:00"
      }
    ]
  }'

Responses

Created

Bodyapplication/json
successboolean

Execution success status (true)

Example: true
datanull

Always null for this response

metaobject

metadata

Example: {"message":"Created"}
Response
application/json
{
  "success": true,
  "meta": {
    "message": "Created"
  }
}

Create an Online Booking

Request

To create a session appointment, provide a JSON object containing the online booking parameters. The object includes the following fields:

FieldTypeMandatoryDescription
phonestringYESClient's phone number (eg +13155550175)
full namestringYESClient name
emailstringNOPostal address of the client
appointmentsArray of objectsYESBooking options (services, team members...)
codestringNOPhone number confirmation code sent via SMS (only needed if you need to confirm the number)
notify_by_smsnumberNONumber of hours in advance to send an SMS reminder for the appointment (set to 0 to disable reminders).
notify_by_emailnumberNONumber of hours in advance to send an email reminder for the appointment (set to 0 to disable the reminder).
commentstringNOAppointment Comment
api_idstringNOExternal Appointment ID

The appointments array consists of objects that have the following fields:

FieldTypeMandatoryDescription
idnumberYesAppointment ID for post-save feedback (see response to request).
servicesarray of numbersNOArray of IDs of the services the client wants to sign up for
staff_idnumberYESID of the team member the client wants to book with (0 if any team member is selected)
datetimedatetimeYESSession date and time in ISO8601 format (passed for each session in the book_times resource)
custom_fieldskey-value objectNOCustom field values that are returned with the appointment

Custom fields in the appointments array

When custom appointment fields are created (see the "Custom Fields" section), you can pass custom values for them during appointment creation. These fields are unique to each location. Once the custom fields are set up, their values can be included in the optional custom_fields parameter. This should be passed as a key–value object, where each key corresponds to the code of the custom field. Example:

  • location created an custom appointment field with code="my_custom_field" type="number", and a second field code="some_another_field" type="list"
  • When creating an appointment, another attribute was passed in the appointments array element: "" appointments: [{ ... }, { ... custom_fields: { "my_custom_field": 123, "some_another_field": ["first value", "second value"] } }]"
  • When this appointment is received by the GET method later, the same value of custom fields will be returned in the response

In response to the request to create an appointment, an array of objects will come (the number of objects is equal to the number of objects in the appointments array) with the following fields:

FieldTypeDescription
idnumberThe appointment ID as passed in the original appointments array
record_idnumberThe unique identifier of the appointment created in the system
record_hashstringA temporary ID used for deleting the appointment immediately after creation

Errors to be handled:

  1. Incorrect SMS verification code. Returned with HTTP status 422 and error code 432. The SMS verification code entered by the user is invalid.

  2. Selected time slot is already taken. Returned with HTTP status 422 and error code 433. The selected appointment time is unavailable. The response includes the id of the conflicting appointment from the appointments array.

  3. User is blacklisted. Returned with HTTP status 403 and error code 434. The user with the specified phone number is blacklisted and cannot book an appointment.

  4. Invalid phone number format. Returned with HTTP status 422 and error code 431. The user's phone number is not in a valid format.

  5. Missing client name. Returned with HTTP status 422 and error code 435. The client's name was not provided.

  6. No available team members. Returned with HTTP status 422 and error code 436. No team members are available at the selected time (commonly occurs when using a default team member setting).

  7. Overlapping appointments in request. Returned with HTTP status 422 and error code 437. One of the selected times overlaps with another appointment in the same request. The response includes the id of the conflicting appointment from the appointments array.

Security
bearer
Path
location_idnumberrequired

location ID

Headers
Acceptstringrequired

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

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

application/json

Authorizationstringrequired

Bearer partner_token

Bodyapplication/jsonrequired
fullnamestringrequired

Client name

Example: "James Smith"
phonestringrequired

Customer phone

Example: "+13155550175"
emailstring

Postal address of the client

Example: "j.smith@example.com"
codenumber

SMS confirmation code for verifying the phone number. This field is required if the location has phone_confirmation = true

Example: 38829
commentstring

Commentary on the post

Example: "test appointment!"
typestring

Appointment source

Example: "mobile"
notify_by_smsnumber

Specifies how many hours before the visit an SMS reminder should be sent to the client. Set to 0 if no reminder is needed.

Example: 6
notify_by_emailnumber

Specifies how many hours before the visit an email reminder should be sent to the client. Set to 0 if no reminder is needed.

Example: 24
api_idnumber

Appointment ID from external system

Example: 777
appointmentsArray of objects

Appointment options (session, services, team member)

Example: [{"id":1,"services":[331],"staff_id":6544,"datetime":"2026-09-21T23:00:00.000-05:00","custom_fields":{"my_custom_field":123,"some_another_field":["first value","next value"]}},{"id":2,"services":[99055],"staff_id":6544,"datetime":"2026-09-21T23:00:00.000-05:00","custom_fields":{"my_custom_field":456,"some_another_field":["next value","last value"]}}]
curl -i -X POST \
  'https://developer.alteg.io/_mock/en/v1/book_record/{location_id}' \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: YOUR_API_KEY_HERE' \
  -H 'Content-Type: application/json' \
  -d '{
    "phone": "+13155550175",
    "fullname": "James Smith",
    "email": "j.smith@example.com",
    "code": 38829,
    "comment": "test appointment!",
    "type": "mobile",
    "notify_by_sms": 6,
    "notify_by_email": 24,
    "api_id": 777,
    "appointments": [
      {
        "id": 1,
        "services": [
          331
        ],
        "staff_id": 6544,
        "datetime": "2026-09-21T23:00:00.000-05:00",
        "custom_fields": {
          "my_custom_field": 123,
          "some_another_field": [
            "first value",
            "next value"
          ]
        }
      },
      {
        "id": 2,
        "services": [
          99055
        ],
        "staff_id": 6544,
        "datetime": "2026-09-21T23:00:00.000-05:00",
        "custom_fields": {
          "my_custom_field": 456,
          "some_another_field": [
            "next value",
            "last value"
          ]
        }
      }
    ]
  }'

Responses

Created

Bodyapplication/json
successboolean

Execution success status (true)

Example: true
dataArray of objects

Data (array of objects)

Example: [{"id":1,"record_id":2820023,"record_hash":"567df655304da9b98487769426d4e76e"},{"id":2,"record_id":2820024,"record_hash":"34a45ddabdd446d5d33bdd27fbf855b2"}]
metaArray of objects

Metadata (empty array)

Example: []
Response
application/json
{
  "success": true,
  "data": [
    { … },
    { … }
  ],
  "meta": []
}

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

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