Resource URL Summary
Description
GET /seiapi/v3/trans/DiagScript/${id}
Description
PUT /seiapi/v3/trans/DiagScript/${id}
Description
DELETE /seiapi/v3/trans/DiagScript/${id}
API Specific Parameters
| Parameter | Description |
|---|---|
| Identifies the ID of the mobile diagnostic script. Valid values are:
|
Supported HTTP Methods
| Method | Description |
|---|---|
| GET | Returns the mobile diagnostic script identified by the ${id} URL parameter |
| PUT | Replaces the mobile diagnostic script identified by the ${id} URL parameter |
| DELETE | Removes the mobile diagnostic script identified by the ${id} URL parameter |
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 diagnostic script definition.
All diagnostic scripts must use an HTTP Content-Type of text/plain.
HTTP Response
Response Codes
| HTTP Code | Description |
|---|---|
200 | OK. Request was processed successfully.
|
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.
|