Skip to content
Integrări POS

Overview

POS Integration API v3

Section titled “POS Integration API v3”

The operations exposed to integrated POS systems: menu updates, product and attribute changes, order status reporting and temporary store closing.

Every request authenticates through the Authorization header, using the API key generated in the integrations portal. The Bearer prefix is accepted but not required.

Amounts in menu payloads are decimals sent as text (“45.0”), while amounts in order notifications are integers in the currency subunit (5700 = 57.00 RON).

Information

  • OpenAPI version: 3.0.1

Operations

Section titled “Operations”
POST
/api/v3/menu/validate
POST
/api/v3/menu/upload
POST
/api/v3/item/modify/stores/{storeId}/products/{productId}
POST
/api/v3/item/modify/stores/{storeId}/bulk
POST
/api/v3/item/modify/stores/{storeId}/attributes/{attributeId}
GET
/api/v3/menu/checkstatus/{trackingCode}
GET
/api/v3/item/modify/checkstatus/bulk/{trackingCode}
POST
/api/v3/order/stores/orders/status
PUT
/api/v3/order-lifecycle/integrations/orders/{orderId}/accept/{storeId}
PUT
/api/v3/order-lifecycle/integrations/orders/{orderId}/ready_for_pickup/{storeId}
PUT
/api/v3/order-lifecycle/integrations/orders/{orderId}/out_for_delivery/{storeId}
PUT
/api/v3/order-lifecycle/integrations/orders/{orderId}/customer_picked_up/{storeId}
GET
/api/v3/scheduling/stores/{storeId}/closing
PUT
/api/v3/scheduling/stores/{storeId}/closing
DELETE
/api/v3/scheduling/stores/{storeId}/closing

Authentication

Section titled “Authentication”

ApiKeyAuth

Section titled “ApiKeyAuth”

The POS API key, created in the integrations portal under Profile → API keys. Send it as-is or prefixed with Bearer . A missing, unknown or inactive key returns 401.

Security scheme type: apiKey

Header parameter name: Authorization