Operation Definitions
Endpoints
GET /api/v1/menu/SICOM_MENU_ID
Use the Get Menu operation to obtain a full menu in JSON format.
In | Field Name | Type | Required | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
header |
| string | Yes | An authorization token linked to the integrator account | ||||||||||||
URL |
| string | Yes | The
|
Responses
Code | Description |
|---|---|
200 | Success Response. The response body includes a JSON formatted menu object. The menu object format is specific to the partner. |
404 | Error Response. Invalid URL. The |
500 | Server Error |
POST /api/v1/status/PARTNER_ID
Use the Update Status operation to notify Omni whether the menu update succeeded or failed.
In | Field Name | Type | Required | Description |
|---|---|---|---|---|
header |
| string | Yes | An authorization token linked to the integrator account |
URL |
| string | Yes | Identifies the partner. The |
body |
| Yes | The Update Status request information |
Responses
Code | Description |
|---|---|
200 | Success Response |
401 | Authentication Error |
403 | Authentication Error |
400 | Bad Payload |
500 | Internal Server Error |
Data Models
UpdateStatusRequestBody
Field Name | Type | Description |
|---|---|---|
| string | The |
| string | The result of the menu update: |
| string | The reason that the menu update failed. For successful updates, do not set a value for this field. For failed updates, send predefined reason messages. |
The following Sample Request Body examples show generic request bodies for success and failure cases:
Sample Request Body - SUCCESS
{
"reference": "SICOM_Menu_ID",
"status": "SUCCESS",
"reason": null
}Sample Request Body - FAILED
{
"reference": "SICOM_Menu_ID",
"status": "FAILED",
"reason": "Validation error"
}