Nexus GatewayRead a restaurant’s menu, submit orders from its website, and track their status in Nexus Retail.
New to Nexus? Read How it works first: one diagram and the handful of terms every guide uses.
Read the menu
The restaurant publishes its catalog from Retail. Fetch that menu from your backend and use its product IDs, prices and revision to build the cart.
The tenant key lets you discover enabled POS connections with GET /v1/connections. Select a connection ID before fetching its menu. Keep the key on your server.
curl "https://website.api.pionier.ro/v1/connections/$NEXUS_CONNECTION_ID/menu" \
-H "Authorization: Bearer $NEXUS_WEBSITE_KEY"Use https://website.api.pionier.ro with the tenant website key supplied by your Nexus contact. Authentication
Submit an order
Send the selected products, customer details, fulfillment mode and payment declaration. Save the complete request and a unique order ID before sending.
A 201 response confirms that Retail has received the order. Staff still need to accept it.
curl "https://website.api.pionier.ro/v1/connections/$NEXUS_CONNECTION_ID/orders" \
-H "Authorization: Bearer $NEXUS_WEBSITE_KEY" \
-H 'Content-Type: application/json' \
--data-binary @order-pickup.jsonDownload example request. Replace its IDs and revision with your selected connection’s published menu values.
Track the order
Receive the restaurant’s decision and fulfillment updates through webhooks. Register your callback before submitting orders. Use GET to reconcile the latest state after downtime or when webhooks are unavailable. A repeated POST returns the original intake receipt, not current progress.
After a timeout, retry the same connection, ID and request body. A new ID can create a duplicate order.
curl "https://website.api.pionier.ro/v1/connections/$NEXUS_CONNECTION_ID/orders/shop-1001" \
-H "Authorization: Bearer $NEXUS_WEBSITE_KEY"{
"external_order_id": "shop-1001",
"status": "accepted",
"total": 3700,
"currency": "RON"
}Integration guides
Build a cartTurn choices into order lines and calculate the total with tested code.Error recoveryHandle stale carts, rejected selections and uncertain submissions.Launch checklistAgree a test setup with Nexus and verify the full order flow with the restaurant.
Supported in v1
| Capability | Scope |
|---|---|
| Pickup and delivery | Use the fulfillment modes enabled by the published menu. |
| Pricing and product choices | RON, integer quantities, exact variants, bundles, extras, deposits and packaging. |
| Payments | Online payment declarations or cash/card on fulfillment. Your provider handles online capture and refunds. |
| Order progress | Signed webhooks and status polling for reconciliation. |
| Menu changes | Retail synchronizes availability automatically for published menus. Pauses and opening hours apply live; prices and catalog changes require publication. Refresh before checkout even when the revision is unchanged. |
Scheduled fulfillment is supported without a separate restaurant opt-in. Customers can cancel immediate orders before acceptance and accepted scheduled orders before preparation begins. Checkout coupons, restaurant staff tips, delivery updates and external refund reporting are supported. Product promotions, arbitrary fees, fractional quantities, order edits and payment processing are not supported. Your payment provider performs refunds.
Get API access
Ask your Nexus contact for your tenant website API key. All production tenants connect to https://website.api.pionier.ro. Discover enabled POS connections with your key, then select the restaurant location and have the restaurant publish its menu. Coordinate test orders with Nexus and the restaurant before sending them.
Examples use synthetic data. This documentation does not send requests or store credentials.