Site map

About document

Response examples are shown in JSON.

In some examples the API base URL is omitted. For example, request URL: unit/list.json?key=yourapikey means that full request URL will be: https://www.mapon.com/api/v1/unit/list.json?key=yourapikey

API general description

Base URL for every HTTP request is:

https://www.mapon.com/api/v1/

API is defined by classes and actions. For example, there are unit class which can have multiple actions. For example, list action which returns car list with current location and other data. URL for such request would look like this:

https://www.mapon.com/api/v1/unit/list.json?key=yourapikey

list is default action for every class, so this means you can also make this request by omitting the /list part:

https://www.mapon.com/api/v1/unit.json?key=yourapikey

Some actions can take arrays as input parameters. For example, unit/list input parameter unit_id has type "int or int array". This means you can either pass single value:

https://www.mapon.com/api/v1/unit/list.json?key=yourapikey&unit_id=14700

Or you can pass multiple values by adding [] to parameter names:

https://www.mapon.com/api/v1/unit/list.json?key=yourapikey&unit_id[]=14700&unit_id[]=14701

Authentication & Authorization

Authentication is done by using API Key. API Keys are managed by company administrators.

API Key can be with unlimited access rights to units and/or actions, but it’s also possible to authorize individual API Key to use just limited list of units and/or actions.

To authenticate, API Key is passed to each HTTP GET request as query parameter key or for a HTTP POST request as form field parameter key. In practice the HTTP request will look similar to this:

https://www.mapon.com/api/v1/unit.json?key=yourapikey

You can also add the API Key to the request header, by setting header key value

Date and time formats

Dates and times are in format defined by ISO 8601 and are in UTC. For example:

2013-02-13T12:17:21Z - datetime
2013-02-13 - date

Request data format

HTTP GET method - all parameters must be added to the url query string, for example:

https://www.mapon.com/api/v1/unit/list.json?key=yourapikey&unit_id[]=14700&unit_id[]=14701

HTTP POST or HTTP DELETE method - parameters must be sent in the request body. Supported content types are: Urlencoded string, JSON

By default, we treat the request payload as urlencoded string (as if the Content-Type header was set to application/x-www-form-urlencoded or multipart/form-data

If you wish to pass request payload as JSON, then you MUST set the Content-Type header as application/json

Please note that passing request payload as JSON ia only currently supported for POST and DELETE requests

Response formats

Response format is defined by appending format name to the action. For example, to return results in JSON, append ".json" to the action:

https://www.mapon.com/api/v1/unit/list.json?key=yourapikey

Currently API supports responses formatted as JSON or XML.

Limits

Currently we allow 5 concurrent requests.

Errors

If request fails, validation is not passed or any other error occurs, the response will contain following data:

{
    "error": {
            "code": 1004,
            "msg": "Missing API key"
    }
}

Error codes equal and larger than #1000 are API wide (global) errors.

Error codes starting from #1 to #999 are action specific errors. This means that for example error code #1 for action unit/list can mean something else than for action route/list. Action specific error codes are listed to each corresponding action description.

Global error codes

CodeDescription
1000Unknown error
1001Server error
1002Invalid request
1003Invalid format
1004Missing API key
1005API key not found
1006Method not available
1007Method is not yet implemented
1008API key does not have any associated units
1009Use SSL for requests
1010Error sending command to device
1011Request limit reached
1012Company suspended
1013Endpoint needs "unlimited" api key access
1014Invalid JSON data payload

Library

To ease working with API there is a simple PHP wrapper library for making API calls.

You can download it there: https://github.com/mapon-com/client-api-php-sdk

Actions

Alert

List

GET https://www.mapon.com/api/v1/alert/list.json
Triggered alerts

Alert types

GET https://www.mapon.com/api/v1/alert/setup_types.json
Get list of supported & accessible alert types that can be managed from API
Note! Not all alert types that are accessible from interface are supported by API.
Access for alert types are obtained from the permissions of the user that created the API key!

Alert type fields

GET https://www.mapon.com/api/v1/alert/setup_fields.json
Obtain supported fields for given alert type. The same fields are required to be passed when storing alert setups

Get alert setups

GET https://www.mapon.com/api/v1/alert/list_setups.json
Get a list of all created alert setups. IMPORTANT - private alert setups are not obtainable via this endpoint

Save alert setup

POST https://www.mapon.com/api/v1/alert/store_setup.json
Create or update alert setup

Delete alert setup

POST https://www.mapon.com/api/v1/alert/delete_setup.json
Delete a single alert setup

Company

Get

GET https://www.mapon.com/api/v1/company/get.json
Company basic data

Company_clients

Create

POST https://www.mapon.com/api/v1/company_clients/create.json
Create client

List

GET https://www.mapon.com/api/v1/company_clients/list.json
Create client

Preset

List

GET https://www.mapon.com/api/v1/preset/list.json
Lists presets available for company

Preset data

GET https://www.mapon.com/api/v1/preset/one.json
Fetched data for one preset

Available preset permissions

GET https://www.mapon.com/api/v1/preset/availablepermissions.json
Returns available permissions that can be set when creating or editing preset

Delete a preset

POST https://www.mapon.com/api/v1/preset/delete.json
Deletes a preset and creates custom preset entries for each user that was assigned to preset

Create a preset

POST https://www.mapon.com/api/v1/preset/create.json
Creates a new preset

Modify an existing preset

POST https://www.mapon.com/api/v1/preset/edit.json
Modify an existing preset.
If arrays with ID's (fields that are suffixed with _ids) are not passed, those are considered to be deleted.
To keep the array information present, mirror data from Preset data endpoint.

Customlayers

Create / Edit layer

POST https://www.mapon.com/api/v1/customlayers/save.json
Create / Edit layer

List layers

GET https://www.mapon.com/api/v1/customlayers/list.json
Return list of all created custom layers

Delete layer

POST https://www.mapon.com/api/v1/customlayers/delete.json
Delete layer

Customlayers_geometries

Add geometries

POST https://www.mapon.com/api/v1/customlayers_geometries/add.json
Add geometries

Edit geometry

POST https://www.mapon.com/api/v1/customlayers_geometries/edit.json
Edit geometry

List geometries

POST https://www.mapon.com/api/v1/customlayers_geometries/list.json
Returns list of all custom layer geometries

Delete geometry

POST https://www.mapon.com/api/v1/customlayers_geometries/delete.json
Delete geometry

Menu

List

GET https://www.mapon.com/api/v1/menu/list.json
Returns list of all available menus for current company (mostly used alongside presets)

Unit

List

GET https://www.mapon.com/api/v1/unit/list.json
Returns list of all available units and their current state data.

Install *

POST https://www.mapon.com/api/v1/unit/install.json
Allows you create unit

Uninstall *

POST https://www.mapon.com/api/v1/unit/uninstall.json
Allows you remove device from unit

Change device *

POST https://www.mapon.com/api/v1/unit/change_device.json
Change assigned device for the unit

Edit

POST https://www.mapon.com/api/v1/unit/edit.json
Edit unit details

Change Relay *

POST https://www.mapon.com/api/v1/unit/change_relay.json
Change relay state (*special access rights are required to use this endpoint. Contact the support team to grant access). Note: Status "ok" in the response means that the request to change the relay has been made. In order to verify if the relay has been changed call the https://www.mapon.com/api/v1/unit/list.json endpoint with relays as the include parameter.

Custom fields

GET https://www.mapon.com/api/v1/unit/custom_fields.json
Returns unit custom fields and values

Edit Custom fields values

POST https://www.mapon.com/api/v1/unit/save_custom_fields_values.json
Allows edit unit custom fields values

Available vehicle icons

GET https://www.mapon.com/api/v1/unit/available_icons.json
Returns list of available vehicle icons to describe the type of vehicle

Unit_data

Ignitions

GET https://www.mapon.com/api/v1/unit_data/ignitions.json
Returns ignition events

Temperature

GET https://www.mapon.com/api/v1/unit_data/temperature.json
Returns measured temperature points

Digital inputs

GET https://www.mapon.com/api/v1/unit_data/digital_inputs.json
Returns switches states for selected period. Digital inputs are selected so that the digital inputs activity period is in selected period and digital inputs switched on time is no more than 15 days before selected period start.

Digital inputs extended

GET https://www.mapon.com/api/v1/unit_data/digital_inputs_extended.json
Returns switches states details for selected period. Digital inputs are selected so that the digital inputs activity period is in selected period and digital inputs switched on time is no more than 15 days before selected period start.

Ibutton authorization history

GET https://www.mapon.com/api/v1/unit_data/ibuttons.json
Returns ibuttons for selected period

CAN data (for period)

GET https://www.mapon.com/api/v1/unit_data/can_period.json
Returns CAN data for a given period

CAN data (single point)

GET https://www.mapon.com/api/v1/unit_data/can_point.json
Returns CAN data in specific datetime

Historical data (single point)

GET https://www.mapon.com/api/v1/unit_data/history_point.json
Returns historical vehicle data at specific datetime

Fields

GET https://www.mapon.com/api/v1/unit_data/fields.json
Return additional data about unit

Debug info

GET https://www.mapon.com/api/v1/unit_data/debug_info.json
Return various information about unit to help debug problems

Driving time (deprecated)

GET https://www.mapon.com/api/v1/unit_data/drivingtime.json
Please use driving_time_extended instead. Return drivers information about driving time

Driving time extended

GET https://www.mapon.com/api/v1/unit_data/driving_time_extended.json
Return drivers information about driving time

Nexogen driving time

GET https://www.mapon.com/api/v1/unit_data/nexogen.json
Return drivers driving time information for nexogen integration

Humidity

GET https://www.mapon.com/api/v1/unit_data/humidity.json
Returns humidity levels in tanks

Unit_groups

List

GET https://www.mapon.com/api/v1/unit_groups/list.json
Returns list of all available company global unit groups.

Insert/Update

POST https://www.mapon.com/api/v1/unit_groups/save.json
Create new group or update an existing

Delete

POST https://www.mapon.com/api/v1/unit_groups/delete.json
Delete group by ID

List units

GET https://www.mapon.com/api/v1/unit_groups/list_units.json
Returns list of all units attached to this group.

Attach unit

POST https://www.mapon.com/api/v1/unit_groups/attach_unit.json
Attach unit to group

Detach unit

POST https://www.mapon.com/api/v1/unit_groups/detach_unit.json
Detach unit from group

Clear unit

POST https://www.mapon.com/api/v1/unit_groups/clear_unit.json
Detach unit from all group

Unit_commands

Get available commands

GET https://www.mapon.com/api/v1/unit_commands/get_available.json
Get unit available command list

Execute unit command

POST https://www.mapon.com/api/v1/unit_commands/execute.json
Execute unit command

Driver_groups

List

GET https://www.mapon.com/api/v1/driver_groups/list.json
Returns list of all available company driver groups.

Insert/Update

POST https://www.mapon.com/api/v1/driver_groups/save.json
Create new group or update an existing

Delete

POST https://www.mapon.com/api/v1/driver_groups/delete.json
Delete group by ID

List Drivers

GET https://www.mapon.com/api/v1/driver_groups/list_drivers.json
Returns list of all drivers attached to this group.

Add driver

POST https://www.mapon.com/api/v1/driver_groups/add_driver.json
Attach driver to group

Remove driver

POST https://www.mapon.com/api/v1/driver_groups/remove_driver.json
Remove driver from a group

Clear driver

POST https://www.mapon.com/api/v1/driver_groups/clear_driver.json
Remove driver from all groups

Route

List

GET https://www.mapon.com/api/v1/route/list.json
Returns list of stops and routes.

Custom fields

GET https://www.mapon.com/api/v1/route/custom_fields.json
Returns custom fields for specific route

Country crossings

GET https://www.mapon.com/api/v1/route/country_crossings.json
Returns list of countries crossed by unit in requested period (max 31 days).

Fuel

Summary

GET https://www.mapon.com/api/v1/fuel/summary.json
Returns fuel summary in period, Start, end and changes.

Changes

GET https://www.mapon.com/api/v1/fuel/changes.json
Returns list of fuel drains and fuel ups.

Fuel sensor level data

GET https://www.mapon.com/api/v1/fuel/data.json
Returns fuel sensor levels for selected period

Fuel_check

List

GET https://www.mapon.com/api/v1/fuel_check/list.json
Return list of company checks for given period

Add

POST https://www.mapon.com/api/v1/fuel_check/add.json
Add new fuel check

Edit

POST https://www.mapon.com/api/v1/fuel_check/edit.json
Edit existing fuel check.
When editing fuel check that is created by an integration only unit_id parameter can be changed, and in some cases card_name as well

Delete

POST https://www.mapon.com/api/v1/fuel_check/delete.json
Delete existing fuel check

Add fuel card

POST https://www.mapon.com/api/v1/fuel_check/add_card.json
Create a fuel card

Update fuel card

POST https://www.mapon.com/api/v1/fuel_check/update_card.json
Edit existing fuel card

Delete fuel card

POST https://www.mapon.com/api/v1/fuel_check/delete_card.json
Delete existing fuel card

Object

List objects

GET https://www.mapon.com/api/v1/object/list.json
Returns list of company objects

Insert/Update object

POST https://www.mapon.com/api/v1/object/save.json
Create new object or update an existing

Delete object

POST https://www.mapon.com/api/v1/object/delete.json
Delete object by ID

Custom fields

GET https://www.mapon.com/api/v1/object/custom_fields.json
Returns object custom fields and values

Edit Custom fields values

POST https://www.mapon.com/api/v1/object/save_custom_fields_values.json
Allows edit object custom fields values

Get objects groups

GET https://www.mapon.com/api/v1/object/list_groups.json
Returns list of object groups

Insert/Update object group

POST https://www.mapon.com/api/v1/object/save_group.json
Create new object group or update an existing

Delete object group

POST https://www.mapon.com/api/v1/object/delete_group.json
Delete object group

User

Create user

POST https://www.mapon.com/api/v1/user/create.json
Create new user

Update user

POST https://www.mapon.com/api/v1/user/update.json
Updates existing user

Change password

POST https://www.mapon.com/api/v1/user/change_password.json
Changes existing users password

Delete user

POST https://www.mapon.com/api/v1/user/delete.json
Delete user

List users

GET https://www.mapon.com/api/v1/user/list.json
Lists all the company users

Device

SMS History *

GET https://www.mapon.com/api/v1/device/sms_history.json
Get all SMS history (*Special access rights are required to use this endpoint. Contact the support team to grant access)

Get device SMS/TCP commands

GET https://www.mapon.com/api/v1/device/get_commands.json
Get device SMS/TCP commands (*Special access rights are required to use this endpoint. Contact the support team to grant access)

Send SMS Command *

POST https://www.mapon.com/api/v1/device/send_sms_command.json
Send SMS command to device (*Special access rights are required to use this endpoint. Contact the support team to grant access)

Send TCP Command *

POST https://www.mapon.com/api/v1/device/send_tcp_command.json
Send TCP command to device (*Special access rights are required to use this endpoint. Contact the support team to grant access)

Get device list

GET https://www.mapon.com/api/v1/device/list.json
Get list of company devices - installed on vehicles and/or in company storage

Supported device models

GET https://www.mapon.com/api/v1/device/models.json
Obtain a list of supported device models and their attributes

Create new device

POST https://www.mapon.com/api/v1/device/create.json
Create a new device

Driver

Create driver

POST https://www.mapon.com/api/v1/driver/create.json
Create new driver

Update driver

POST https://www.mapon.com/api/v1/driver/update.json
Update driver

Change password

POST https://www.mapon.com/api/v1/driver/change_password.json
Changes existing drivers password

Delete driver

POST https://www.mapon.com/api/v1/driver/delete.json
Delete driver

List drivers

GET https://www.mapon.com/api/v1/driver/list.json
List all company drivers

List drivers Unit groups

GET https://www.mapon.com/api/v1/driver/list_unit_groups.json
List all driver unit groups

Custom fields

GET https://www.mapon.com/api/v1/driver/custom_fields.json
Returns driver custom fields and values

Get driver activity intervals (daily) | BETA

GET https://www.mapon.com/api/v1/driver/daily_activities.json

BETA VERSION This end-point is fully usable but there might be issues. Please contact client support if you encounter any problems.

Get a list of driver activity intervals grouped by days.
Grouping by days happens according to company timezone
Please note that due to technical limitations data will be selected for whole days. For example, if you pass period YYYY-MM-DD 12:00:00 - YYYY-MM-DD 20:00:00, the data will be returned for period YYYY-MM-DD 00:00:00 - YYYY-MM-DD 23:59:59 instead.
Maximum period: 31 days
Can select only a single driver
Data sources: CAN, Tachograph driver files

Reefer

List alerts

GET https://www.mapon.com/api/v1/reefer/alert_list.json
Returns list of alarms

Alert set

POST https://www.mapon.com/api/v1/reefer/set_alert.json
Create new alert

Alert delete

POST https://www.mapon.com/api/v1/reefer/alert_delete.json
Delete alert

Alert change user

POST https://www.mapon.com/api/v1/reefer/alert_change_user.json
Change alert user

Change setpoint

POST https://www.mapon.com/api/v1/reefer/change_setpoint.json
Change refrigerator setpoint temperature

Runmodes list

GET https://www.mapon.com/api/v1/reefer/runmodes.json
Show current and available runmodes for refrigerator

Change runmode

POST https://www.mapon.com/api/v1/reefer/change_runmode.json
Change refrigerator runmode

List temperature data

GET https://www.mapon.com/api/v1/reefer/list_temperature_data.json
Return temperature data for period

Historic point data

GET https://www.mapon.com/api/v1/reefer/historic_point.json
Return the reefer values (either neaerest of previous) at a given point in time

Historic period data

GET https://www.mapon.com/api/v1/reefer/historic_period.json
Get a list of historic reefer data values for a specified period

Tachograph

List driver DDD files

GET https://www.mapon.com/api/v1/tachograph/list_ddd_driver.json
Returns list of driver DDD files. Max period 1 month.

Download driver DDD file

GET https://www.mapon.com/api/v1/tachograph/download_ddd_driver.json
Echo binary data file with Content-Type: application/octet-stream

List vehicle DDD files

GET https://www.mapon.com/api/v1/tachograph/list_ddd_vehicle.json
Returns list of vehicle DDD files. Max period 1 month.

Download vehicle DDD file

GET https://www.mapon.com/api/v1/tachograph/download_ddd_vehicle.json
Echo binary data file with Content-Type: application/octet-stream

Tracking

List

GET https://www.mapon.com/api/v1/tracking/list.json
Get all enabled tracking links

Edit

POST https://www.mapon.com/api/v1/tracking/edit.json
Edit existing tracking link

Create

POST https://www.mapon.com/api/v1/tracking/create.json
Create new tracking link

Delete

POST https://www.mapon.com/api/v1/tracking/delete.json
Delete tracking link

Messaging_channels

List

GET https://www.mapon.com/api/v1/messaging_channels/list.json
List user channels

Messaging_conversations

Create

POST https://www.mapon.com/api/v1/messaging_conversations/create.json
Create conversation.
- If conversation with user/car exists returns existing conversation.
- If type individual and receivers > 1, then multiple conversations created

List

GET https://www.mapon.com/api/v1/messaging_conversations/list.json
List user conversations

Messaging_messages

Send

POST https://www.mapon.com/api/v1/messaging_messages/send.json
Send message to existing conversation

List

GET https://www.mapon.com/api/v1/messaging_messages/list.json
List conversation messages

Driver_behaviour

Units report

GET https://www.mapon.com/api/v1/driver_behaviour/report_units.json
List units driver behaviour data

Drivers report

GET https://www.mapon.com/api/v1/driver_behaviour/report_drivers.json
List drivers behaviour data

Vehicle_inspections

List inspections

GET https://www.mapon.com/api/v1/vehicle_inspections/list.json

Routeplanning_orders

Create order

POST https://www.mapon.com/api/v1/routeplanning_orders/create.json
Create order

Add places to the order

POST https://www.mapon.com/api/v1/routeplanning_orders/add_places.json
Add places to the order

Get order

GET https://www.mapon.com/api/v1/routeplanning_orders/get.json
Get order by id

List orders

GET https://www.mapon.com/api/v1/routeplanning_orders/list.json
List company orders

Delete orders

POST https://www.mapon.com/api/v1/routeplanning_orders/delete.json
Delete given orders

Routeplanning_places

Get place

GET https://www.mapon.com/api/v1/routeplanning_places/get.json
Get place by id

List places

GET https://www.mapon.com/api/v1/routeplanning_places/list.json
List company places

Delete places

POST https://www.mapon.com/api/v1/routeplanning_places/delete.json
Delete given places

Routeplanning_routes

Create/Update

POST https://www.mapon.com/api/v1/routeplanning_routes/save.json
Create or update route

Get route

GET https://www.mapon.com/api/v1/routeplanning_routes/get.json
Get route by id

List routes

GET https://www.mapon.com/api/v1/routeplanning_routes/list.json
List company routes

Send route to assignee

POST https://www.mapon.com/api/v1/routeplanning_routes/send_to_assignee.json
Route will be available on driver application

Set route start address and/or departure date time

POST https://www.mapon.com/api/v1/routeplanning_routes/set_start_address.json
Set route start address and/or departure date time

Set route end address

POST https://www.mapon.com/api/v1/routeplanning_routes/set_end_address.json
Set route end address

Start route optimization

POST https://www.mapon.com/api/v1/routeplanning_routes/optimize.json
Start route optimization. Use this endpoint with the "Check optimization progress" endpoint

Check optimization progress

GET https://www.mapon.com/api/v1/routeplanning_routes/optimize_check_progress.json
Check optimization progress,status. To start optimization see the "Start route optimization" endpoint

Delete routes

POST https://www.mapon.com/api/v1/routeplanning_routes/delete.json
Delete given routes

Ble_tags

Get BLE tag list

GET https://www.mapon.com/api/v1/ble_tags/list.json
Returns a list of BLE tags belonging to company. Only active tags are included.

Get BLE tag historic point data

GET https://www.mapon.com/api/v1/ble_tags/history_point.json
Get BLE tag historic data for single datetime point. Looks for closest (by time) values within 30 day period of the passed datetime.

Get tag scans

GET https://www.mapon.com/api/v1/ble_tags/scans.json
Returns a list of tag scans in period. Maximum period: 31 days.

Get tag locations

GET https://www.mapon.com/api/v1/ble_tags/locations.json
Returns tag location history list in period. Maximum period: 31 days.

Data_forwarding

Extended information about endpoints and data packs can be found here.

Data_forward

List endpoints

GET https://www.mapon.com/api/v1/data_forward/list.json
List all active endpoints

Insert/Update endpoint

POST https://www.mapon.com/api/v1/data_forward/save.json
Create new endpoint or update an existing

Add single unit id to endpoint

POST https://www.mapon.com/api/v1/data_forward/add_unit.json
Add single unit id to endpoint.

Remove single unit id from endpoint

POST https://www.mapon.com/api/v1/data_forward/remove_unit.json
Remove single unit id from endpoint.

Delete endpoint

POST https://www.mapon.com/api/v1/data_forward/delete.json
Delete active endpoint

Purge endpoint queue

POST https://www.mapon.com/api/v1/data_forward/purge.json
Delete all active messages from queue

List endpoint data packs

GET https://www.mapon.com/api/v1/data_forward/list_packs.json

List endpoint all available data packs

Extended information about data packs can be found here.

Reports

Report_make

SRS trip ticket 1

POST https://www.mapon.com/api/v1/report_make/vid1.json
Make "SRS trip ticket 1" report.
In response you will get a process_id. Save it for later to query for process status.

Reefer temperature

POST https://www.mapon.com/api/v1/report_make/reefer_temperature.json
Make "Reefer temperature" report.
In response you will get a process_id. Save it for later to query for process status.

Truck activity report

POST https://www.mapon.com/api/v1/report_make/activity.json
Make "Truck activity report" report.
In response you will get a process_id. Save it for later to query for process status.

Report

Get report status

GET https://www.mapon.com/api/v1/report/status.json
Check if report is ready for download.
Possible statuses:
  • queued - waiting in line to be processed
  • processing - building report
  • finished - report is available for download

Get Ely Report

GET https://www.mapon.com/api/v1/report/ely.json
Get Ely Report data

3rd party applications

Application

Authenticate user by token for iframe

POST https://www.mapon.com/api/v1/application/user_auth_by_token.json
Authenticate user with provided token. In return you will receive user object and api_key which you can use to get in depth user data.

Authenticate application for company

POST https://www.mapon.com/api/v1/application/company_auth_by_token.json

When system administrator from CRM enables application for specific company, there will be a POST request to 3rd party application's end point with field company_token.

Application must call application/company_auth_by_token together with company_token to request company_id and company_api_key which can be stored in 3rd party applications side for later use.

End point for company_token is provided by 3rd party application's developer. In response to this request, we expect to get the following JSON response:

{"status":"ok"}

In case of an error, application will not be enabled for the company and system administrator can retry this process later.

Application_fields

List available fields

GET https://www.mapon.com/api/v1/application_fields/list.json

List all available fields by providing entity type

Update field value

POST https://www.mapon.com/api/v1/application_fields/updatevalue.json

Update field value by providing field id, entity type and entity id.

Update field options

POST https://www.mapon.com/api/v1/application_fields/updateoptions.json

For field type = select. Options must be valid JSON string. Example: {"Canada":{"AB":"ALBERTA","BC":"BRITISH COLUMBIA"},"Mexico":{"AG":"AGUASCALIENTES"}} or {"1":"Canada","2":"USA"}

If field is configured to have options defined per company, provide company_id

Application_menu

List

GET https://www.mapon.com/api/v1/application_menu/list.json
List all menu items

Insert/Update menu item

POST https://www.mapon.com/api/v1/application_menu/save.json

Insert/Update menu item. Edited menu items will be available after 5 minutes frontend cache expire.

You can also update first level menu item by passing parent_id = 0.

Iframe url will be formatted after this structure app_base_url + path + ?user_token=

Delete menu item

POST https://www.mapon.com/api/v1/application_menu/delete.json
Delete menu item. Menu items with parent_id = 0 can't be deleted