Skip to main content

Sending Orders

Sending orders through Connect API includes:

  1. Construct order payload: Prepare the order data following the specifications outlined in the POS Order External API Example.

  2. Add tokens for authorization: Include the generated token in the authorization header of the request.

  3. Add required HTTP headers: Fill in the necessary HTTP headers X-COMPANY-ID and X-SITE-IDs.

  4. Send order request: Use the Connect API POST /ds/pipeline/pos.order endpoint to send the order to Portal API.

Important notes:

  • The Connect API only accepts orders with a last_modified timestamp that is newer than the existing record. Orders with an older timestamps are skipped to prevent outdated data. For more information, see Order Conflict Resolution.

  • Reduce the load on the system by posting each order to the Portal API only once, after the order has been tendered and all items bumped from the Kitchen Management API monitors. This reduces the opportunity for order conflicts. Order updates can be posted when required. When an order is updated, update the order’s time.last_modified element before posting the order.

See also: