Mobile Application Configuration REST API
It is not required to create a mobile configuration for each deployment group. If a deployment group does not have a specific mobile configuration defined it will automatically inherit form the Default
deployment group.
When a mobile application configuration is updated it will automatically be applied to the mobile device the next time the application is launched or logged into - assuming network connectivity is available.
- Configurations are always associated with a deployment group
- There is always the
Default
deployment group that can not be deleted from the system.
Resource URL Summary
Get a deployment group's mobile application configuration
GET /seiapi/v3/trans/DeploymentGroup/${DeploymentGroupID}/MobileCfg
Update a deployment group's mobile application configuration
PUT /seiapi/v3/trans/DeploymentGroup/${DeploymentGroupID}/MobileCfg
API Specific Parameters
Parameter | Description |
---|---|
| Identifies the Deployment Group. |
Supported HTTP Methods
Method | Description |
---|---|
GET | Returns the mobile application configuration for the deployment group identified by the ${id} URL parameter |
POST | Creates or replaces the mobile application configuration for the deployment group identified by the ${id} URL parameter. Updates are automatically applied to the mobile device on next application launch or login - assuming network connectivity is available. |
HTTP Headers
This API uses the default ServiceMobility HTTP Headers.
HTTP Headers
This API uses the default ServiceMobility HTTP Headers.
HTTP Body
The body contains the mobile application configuration.
HTTP Response
Response Codes
HTTP Code | Description |
---|---|
200 | OK. Request was processed successfully. Even though the request may return a successful code of 200, the body may still contain warning details. |
400 | Syntax error in request. The response body will provide more details on the specific reason. Verify the URI, its parameters, and request body. |
401 | Unauthorized. The credentials are incorrect, please verify and try again. |
404 | Not Found. The URL is incorrect, please verify and try again. |
405 | The specified HTTP method is not supported for this resource. |
409 | Conflict. This error usually occurs when attempting to overwrite an existing object that can not be replaced. |
410 | The specified object does not exists. Please verify the URI. |
500 | An error has occurred within ServiceMobility. Please review the error message details and if necessary, contact customer support. |
Response Body
{ "code": 400, "detail": { "message": "", "params": { "value": "" }, "dataPath": "" } }
Response Object Properties
Property | Type | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
code | integer | The HTTP response code. | ||||||||||||
detail | object | This object provides additional details the system provided while processing the transactions. Usually the details provide additional information on why an error occurred. However, it may also provide warning details even when the requests was successful. For example, the request may have returned a response of 200=OK, but included warnings in the response body of properties that are still being used that are marked for deprecation.
|