Quiqqy platform overview

Quiqqy is an ordering platform for restaurants and retail stores. Merchants run storefronts on Quiqqy; you integrate against one of three partner APIs depending on what you are building.

Three products

Product	You are building	Direction	Base URL
Online Ordering API	A POS integration: receive Quiqqy orders into a point-of-sale, push the POS menu to Quiqqy	Quiqqy → your POS (orders), your POS → Quiqqy (menu, status)	https://auth.quiqqy.ai/api/v2
Hub Ordering API	On top of a Hub community — a marketplace of stores under one brand: custom storefronts, ops dashboards, order automation	You → Quiqqy (orders), Quiqqy → you (events)	https://hub-api.quiqqy.ai/api/v2
Mercnet Reports API	Programmatic reporting and catalogue management for merchants on the Mercnet network	You → Quiqqy	https://api.quiqqy.ai/api/v2

All three share one developer account, one console, one authentication model, one webhook transport and one error envelope. Learn those once and they apply everywhere.

How the pieces fit

A merchant’s store lives on Quiqqy. Customers order through a Quiqqy storefront (their own site, a Hub community marketplace, or a QR/table flow). Quiqqy holds the order of record, takes payment, and pushes events out.

• A POS company connects stores with the Online Ordering API: the merchant authorizes the app, the POS pushes its catalogue, and every order arrives as a signed webhook the POS accepts, prepares and completes.
• A Hub builder reads a community’s catalogue and places orders into it; Hub splits each order into one child order per fulfilling store and forwards it.
• A reporting or back-office tool reads sales, order and demand data — and optionally manages the catalogue — through Mercnet Reports.

Environments

Environment	Host	Data
Sandbox	https://sandbox.quiqqy.ai/api/v2	Test stores and test orders only
Production	Per product, table above	Live merchants

Every credential belongs to exactly one environment. Start in sandbox; production access is granted after go-live review.

Note

API access requires an approved developer account and a signed developer agreement. Both are handled in the console — see Getting started.

Start here

Getting started Account, agreement, first app, first call — end to end in one sitting.

Authentication Client credentials, merchant consent and Bearer tokens.

Webhooks Signature verification, retries and the event catalogue.

Errors The envelope, stable codes and what to retry.

API reference

Endpoint-by-endpoint reference, generated from the API definitions: Online Ordering · Hub Ordering · Mercnet Reports