| GET | /api/skus/{SkuGuid} | Get a Sku. |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| SkuGuid | path | Guid | Yes | Guid of the Sku. |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| SkuGuid | body | Guid | No | |
| Name | form | string | No | |
| BillingMetric | form | string | No | Allowable Values
|
| Quantity | body | Integer | No | |
| UnitPrice | body | Decimal | No | |
| Description | form | string | No | |
| Status | form | string | No | Allowable Values
|
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /api/skus/{SkuGuid} HTTP/1.1
Host: api.secure-messaging.com
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{
"responseStatus": {
"errorCode": "String",
"message": "String",
"stackTrace": "String",
"errors": [
{
"errorCode": "String",
"fieldName": "String",
"message": "String",
"meta": {
"String": "String"
}
}
],
"meta": {
"String": "String"
}
},
"skuGuid": "00000000000000000000000000000000",
"name": "String",
"billingMetric": "String",
"quantity": 0,
"unitPrice": 0,
"description": "String",
"status": "String"
}