Mercnet Reports API

Mercnet Reports gives back-office and analytics tools read access to a merchant’s sales, orders and demand data — and write access to their catalogue. It is the product for accounting integrations, BI pipelines, inventory tools and multi-store dashboards.

Base URL   https://api.quiqqy.ai/api/v2       (sandbox: https://sandbox.quiqqy.ai/api/v2)
Auth       Partner Bearer token (same platform model)

Scope — what it is and is not

In scope	Out of scope
Reports: sales summaries, order exports, top items, hourly demand, store health, payments	Merchant users and staff
Catalogue: items, categories, menus, availability, prices	Merchant settings and configuration
	POS integrations and webhooks setup (that is Online Ordering)

The API deliberately does not expose users, settings or integrations. A reporting token cannot reconfigure a store — the write surface is the catalogue and nothing else.

Authentication

The same partner tokens as everywhere else on the platform: the merchant authorizes your app once through the authorization-code flow, and you call with Authorization: Bearer <access_token>. Tokens are scoped to the merchant’s organization; every report accepts an optional store_id filter to narrow to one store.

Two surfaces

Reports Sales summary, order export with cursor pagination, top items, hourly demand, store health, payments.

Catalogue Items, categories and menus CRUD, availability and price updates, and how changes propagate.

Money and time

All monetary amounts are integers in the currency’s minor unit. All report ranges are date-based and resolved in the store’s timezone unless you pass one explicitly — details on the Reports page.

Endpoint-level details live in the Mercnet Reports API reference.