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

Материал из WiKi - UserSide
(Новая страница: «en | ru»)
 
Нет описания правки
 
(не показаны 4 промежуточные версии этого же участника)
Строка 1: Строка 1:
[[API_EN|en]] | [[API|ru]]
[[API_EN|en]] | [[API|ru]]
This section describes the possibilities of using the inbuilt API in ERP "UserSide", which allows you to use the integrated functionality in your own projects.
The API does not cover all functionality at the moment and is gradually being developed, so this page will have frequent changes and additions.
== Operating principle ==
The /api.php file is responsible for interaction.
Both GET and POST requests can be used.
Incoming Parameters:
Mandatory:
  key - API key
  cat - category of the request
Optional:
  skip_internal_api - flag - do not include internal system triggers ''(reasonable to use when your API method is a reaction to some trigger and it ends up looping itself during normal operation)''
Other additional parameters, depending on the category ''(see below in the relevant categories)''.
For example:
  customer_id - user id of the customer
  is_potential - flag. It can take the value 1 or 0. Most flags have the prefix '''is'''.
Example request:
api.php?key=apikey&cat=abon&action=msg&usercode=1
Returned data:
  If the query involves some action or information return, information will be returned in JSON format:
  array(
    [Result] => OK / ERROR
    [ErrorText] => In case of an error, the error text
  )
It is also reasonable to check the HTTP code of the response. In case of errors/incorrect requests - HTTP code will be different from 200
== Basic setting ==
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 commutation_EN|commutation]] - Commutation of objects
* [[API cross_EN|cross]] - ODF/Crosses
* [[API customer_EN|customer]] - Users. Most actions are relevant for [[Supported_billings|manual billing]]
* [[API device_EN|device]] - Equipment
* [[API employee_EN|employee]] - Employees ''(since 3.16dev2)'''
* [[API fibre_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
* [[API node_EN|node]] - Communication facilities ''(communication nodes, fiber optical junction boxes, poles, manholes)'''
* [[API notepad_EN|notepad]] - Notepad
* [[API operator_EN|operator]] - system operators ''( before 3.16dev2)'''
* [[API owner_EN|owner]] - Object Owners
* [[API redirect_EN|redirect]] - Redirects to an object card based on some attribute
* [[API service_EN|service]] - Additional services
* [[API setting_EN|setting]] - Setting
* [[API sms_EN|sms]] - SMS messages
* [[API splitter_EN|splitter]] - dividers/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

Текущая версия от 15:13, 30 октября 2023

en | ru

This section describes the possibilities of using the inbuilt API in ERP "UserSide", which allows you to use the integrated functionality in your own projects.

The API does not cover all functionality at the moment and is gradually being developed, so this page will have frequent changes and additions.

Operating principle

The /api.php file is responsible for interaction.

Both GET and POST requests can be used.

Incoming Parameters:
Mandatory:
 key - API key
 cat - category of the request
Optional:
 skip_internal_api - flag - do not include internal system triggers (reasonable to use when your API method is a reaction to some trigger and it ends up looping itself during normal operation)
Other additional parameters, depending on the category (see below in the relevant categories). 
For example:
 customer_id - user id of the customer
 is_potential - flag. It can take the value 1 or 0. Most flags have the prefix is.

Example request:
api.php?key=apikey&cat=abon&action=msg&usercode=1
Returned data:
 If the query involves some action or information return, information will be returned in JSON format:
  array(
   [Result] => OK / ERROR
   [ErrorText] => In case of an error, the error text
  )
It is also reasonable to check the HTTP code of the response. In case of errors/incorrect requests - HTTP code will be different from 200

Basic setting

Configure the API Key.

Categories