The API surfaces
Storefront APILive
https://api.matgrk.com/v1
The store-facing API behind custom storefronts and mobile apps: catalogue, search, cart, checkout, shopper accounts and orders.
Admin APIIn development
The management side of a store: products, categories, stock, orders, invoices, offers, promotions and API keys.
Data hub APIIn development
Connections, mappings, flows and runs — moving catalogue, stock, order and customer data between matgrk and your systems.
Insights APIIn development
The reports, custom queries, schedules and exports behind the dashboard’s analytics.
ERP integrationDesign preview
For ERP partners: onboard your customers, feed their catalogues, sync stock, and receive delivered orders.
WebhooksIn development
HMAC-signed order and payment events. They flow between matgrk services today; subscribing your own endpoint is planned.
Quick start
1. Get an API key
Every store gets its own credential with its own rate limit. The key (
mk_live_…) is shown once when it is issued and matgrk keeps only a hash of it. Key management from the dashboard is coming; today a key is issued for your store on request through support.2. Exchange it for tokens
The key itself is only ever sent to the two token endpoints — every other call uses the short-lived access token.
Request curl -X POST https://api.matgrk.com/v1/auth/anonymous \ -H "X-Api-Key: mk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"transport": "bearer", "scope": ["catalogue:read"]}'Response { "data": { "transport": "bearer", "accessToken": "eyJhbGciOi…", "refreshToken": "eyJhbGciOi…", "expiresIn": 900, "scope": ["catalogue:read"] } }3. Call the API
curl https://api.matgrk.com/v1/catalogue/products \ -H "Authorization: Bearer ACCESS_TOKEN"
Good to know
- All requests are HTTPS and all bodies are JSON.
- Every response is an envelope:
{ "data": … }on success,{ "error": … }on failure — see conventions. - A credential belongs to exactly one store, and so does every token minted with it.