API characteristics
Endpoint information
The endpoints differ between Ivanti Neurons for MDM and Ivanti EPMM for certificate-based authentication, and between basic authentication and certificate authentication for Ivanti Neurons for MDM.
The CPS APIs only support usage in the default device space.
The following table summarizes the endpoints:
Authentication | Ivanti Neurons for MDM | Ivanti EPMM |
|---|---|---|
Basic | https://<fully-qualified-hostname>/msa/v1/cps For example, given the fully qualified hostname, na1.mobileiron.com, the endpoint address would be: https://na1.mobileiron.com/msa/v1/cps | For both basic and certificate-based authentication: https://<fully-qualified-hostname>/msa/v1/cps For example, given the fully qualified hostname, acme.mobileiron.com, then the endpoint address would be: https://acme.mobileiron.com/msa/v1/cps |
Certificate | https://cps-<clustername>.mobileiron.com/msa/v1/cps For example, given the cluster name NA1, the endpoint address would be: https://cps-na1.mobileiron.com/msa/v1/cps When using certificate-based authentication, you must include the identity certificate in every API call and when establishing a connection to MQTT. See Example Ivanti Neurons for MDM certificate-based authentication cURL command for how to include the certificate. See Certificate-based authentication workflows for how to set up certificate-based authentication. |
These endpoints listen on port 443.
Example Ivanti Neurons for MDM certificate-based authentication cURL command
curl -X GET 'https://cps-na1.mobileiron.com/msa/v1/cps/version'
--cert <End user's P12 file path>/<End user's P12 filename>.p12:<End user's P12 file password>
--cert-type p12
--cacert <ca-cert.pem file path> P12 in the snippet above refers to p12 authentication certificates. See Certificate-based authentication workflows for how to set up certificate-based authentication.