API Error Handling

The following scenarios could happen and the error responses are provided below:

400: Bad request

• A compromised client is trying to pretend that the same instance of the same application is on a different installation on a device.
• A compromised client has changed the previously assigned installation identifier for the installation on a device.
• A compromised installation on a device is trying to spoof that it already has an installation_id.

401: Unauthorized

• The application has been deactivated, perhaps retired, by the customer.
• The customer has been suspended by the ZSM Server root admin.

404: Not found

• An installation on a device is trying to get a new installation ID for an unregistered application.