multi_import

The exchange/multi_import method allows you to create units from a ZIP archive and import their messages. To create such an archive, use the exchange/multi_export method.

To use the method, the Import/Export service must be enabled for the account. Each WLP file in the archive counts as one use of the service.

In Wialon Local, this method is available starting from version 2304.

svc=exchange/multi_import&params={
  "userId": <uint>
}

The method is a resource-intensive request, so the limit on simultaneous resource-intensive requests during one session applies to it. If the limit is reached, the error 1003 with the LIMIT api_concurrent reason is returned. For the list of resource-intensive requests, see Limitations.

To load the archive, use a POST request with multiple contents (multipart/form-data). If several files are attached, only the first one is processed. For example:

Request URL: https://hst-api.wialon.com/wialon/ajax.html?svc=exchange/multi_import&sid=SESSION_IDENTIFIER
Request Method: POST
Content-Type: multipart/form-data; boundary=----WebKitFormBoundarylvunQiir9AesO8qB

------WebKitFormBoundarylvunQiir9AesO8qB
Content-Disposition: form-data; name="params"

{"userId":123456}
------WebKitFormBoundarylvunQiir9AesO8qB
Content-Disposition: form-data; name="file"; filename="multi_export.zip"
Content-Type: application/zip


------WebKitFormBoundarylvunQiir9AesO8qB--

The archive must contain the following files:

For each WLP file in the archive, a new unit is created. Existing units aren’t updated. The unit properties from the file are applied to the new unit.

The device type is defined by its ID or name from the file. If the device type isn’t found, the device type with ID 899 (Wialon Retranslator) is set. If the server has no device type with this ID, the unit isn’t created.

The messages from the WLB file are imported only if the creator has the Import messages access right to the new unit.

If a unit can’t be created, it’s skipped, and no error is returned.

If the request is completed successfully, the following response is returned:

{
  "error": 0
}

If the request fails, an error code is returned.