Language
Merchant-facing text in CIQRA — such as scope descriptions on the consent screen — is Turkish. It is shown here verbatim, because it is what the merchant reads when installing your app.
Build apps for CIQRA stores
A CIQRA app is your own service talking to one store through the CIQRA API. The store’s owner installs it, chooses what it may do, and can remove it at any time. Your app gets a client id and secret, exchanges them for a short-lived token, and calls the API on the store’s own domain.
13operations an app token may call
9 / 52scopes enforced by an endpoint
999operations in the platform API
These numbers are counted from the platform’s API contract every time this site is built. The same is true of the App API reference and the scope table: nothing on them is typed by hand, so when an endpoint opens to apps, it appears here on the next build.
Where to start
Section titled “Where to start”QuickstartFrom credentials to your first API call in four requests.
How an app fits inApps, installations, tokens and stores — the four nouns.
App API referenceEvery operation an app may call, with request and response schemas.
WebhooksSubscribe to store events and verify that they came from CIQRA.
What to read before you promise anything
Section titled “What to read before you promise anything”The API is closed by default: an endpoint accepts app tokens only after it is explicitly opened with a scope. Today that covers the product catalogue, collections, inventory levels, media imports, metaobjects and webhook subscriptions. Orders, customers, prices and most other areas are not yet open to apps, even though their scopes can already be granted. What apps cannot do yet lists every gap, including known defects, before you plan around them.
Team documentation
CIQRA engineers: the full platform API, the database model and the module map are in the internal docs (password required).