API EN: различия между версиями

Материал из WiKi - UserSide
(Новая страница: «en | ru»)
 
([IronBot] Sync EN localization from RU)
 
(не показана 21 промежуточная версия 3 участников)
Строка 1: Строка 1:
[[API_EN|en]] | [[API|ru]]
'''en''' | [[API_UK|uk]] | [[API|ru]]
 
This section describes how to use the built-in ERP "UserSide" API in your own projects.
 
The API does not currently cover all functionality and is being expanded gradually, so this page may change frequently.
 
== Operating principle ==
 
The /api.php file is responsible for interaction.
 
Both GET and POST requests can be used.
 
'''Starting with version 3.21, all requests that write or modify data are processed only through POST.'''
 
Input parameters:
Required:
  key - API key
  cat - request category
Optional:
  skip_internal_api - flag - do not run internal system triggers ''(useful when an API method is called from a trigger and would otherwise trigger itself during normal operation)''
Other additional parameters, depending on the category ''(see below in the relevant categories)''.
For example:
  customer_id - customer id
  is_potential - flag. It can be 1 or 0. Most flags use the '''is''' prefix.
Example request:
api.php?key=apikey&cat=abon&action=msg&usercode=1
 
Returned data:
  If the request performs an action or returns data, the response is returned in JSON format:
  array(
    [Result] => OK / ERROR
    [ErrorText] => Error text, if an error occurred
  )
 
Also check the HTTP response code. For errors or invalid requests, the HTTP code will differ from 200.
 
== Basic setup ==
 
Configure the [[UserSide_API_Key_EN|API Key]].
 
== Categories ==
* [[API_address_EN|address]] - Addresses
* [[API_attach_EN|attach]] - Attachments
* [[API_additional_data_EN|additional_data]] - Additional fields/data for objects
* [[API_advertising_EN|advertising]] - Advertising campaigns
* [[API_billing_EN|billing]] - Billing
* [[API_cable_route_EN|cable_route]] - Cable routes and channels
* [[API_call_EN|call]] - Calls
* [[API_chapter_EN|chapter]] - Custom sections/pages/links
* [[API_commutation_EN|commutation]] - Commutation of objects
* [[API_cross_EN|cross]] - Distribution frames
* [[API_customer_EN|customer]] - Customers. Most actions are relevant for [[Supported_billings|manual billing]]
* [[API_cwdm_EN|cwdm]] - CWDM
* [[API_device_EN|device]] - Equipment
* [[API_employee_EN|employee]] - Employees ''(since 3.16dev2)''
* [[API_fiber_EN|fiber]] - Cable lines
* [[API_gps_EN|gps]] - GPS trackers
* [[API_inventory_EN|inventory]] - Warehouse
* [[API_key_EN|key]] - Keys
* [[API_map_EN|map]] - Coverage maps
* [[API_module_EN|module]] - External requests from modules
* [[API_newin_EN|newin]] - Connection request ''(before 3.18)''
* [[API_node_EN|node]] - Infrastructure facilities ''(communication nodes, splice closures, poles, manholes)''
* [[API_notepad_EN|notepad]] - Notepad
* [[API_operator_EN|operator]] - System operators ''(before 3.16dev2)''
* [[API_owner_EN|owner]] - Owners
* [[API_redirect_EN|redirect]] - Redirects to an object card by attribute
* [[API_service_EN|service]] - Additional services
* [[API_setting_EN|setting]] - Settings
* [[API_sms_EN|sms]] - SMS messages
* [[API_splitter_EN|splitter]] - Splitters
* [[API_staff_EN|staff]] - Staff ''(up to 3.16dev2)''
* [[API_system_EN|system]] - System information and operations
* [[API_tariff_EN|tariff]] - Tariffs
* [[API_task_EN|task]] - Tasks
* [[API_trader_EN|trader]] - Vendors
* [[API_vehicle_EN|vehicle]] - Vehicles
* [[API_vlan_EN|vlan]] - VLAN

Текущая версия от 14:58, 29 мая 2026

en | uk | ru

This section describes how to use the built-in ERP "UserSide" API in your own projects.

The API does not currently cover all functionality and is being expanded gradually, so this page may change frequently.

Operating principle

The /api.php file is responsible for interaction.

Both GET and POST requests can be used.

Starting with version 3.21, all requests that write or modify data are processed only through POST.

Input parameters:
Required:
 key - API key
 cat - request category
Optional:
 skip_internal_api - flag - do not run internal system triggers (useful when an API method is called from a trigger and would otherwise trigger itself during normal operation)
Other additional parameters, depending on the category (see below in the relevant categories). 
For example:
 customer_id - customer id
 is_potential - flag. It can be 1 or 0. Most flags use the is prefix.

Example request:
api.php?key=apikey&cat=abon&action=msg&usercode=1
Returned data:
 If the request performs an action or returns data, the response is returned in JSON format:
  array(
   [Result] => OK / ERROR
   [ErrorText] => Error text, if an error occurred
  )
Also check the HTTP response code. For errors or invalid requests, the HTTP code will differ from 200.

Basic setup

Configure the API Key.

Categories