Developers
Build an integration for an eMatjarak store: a scoped API key, a GraphQL API, and signed webhooks.
Build for an eMatjarak store
A merchant can hand you a key to their own store. With it you get their catalogue, their orders and their customers over GraphQL, plus signed webhooks when things change. That is the whole surface — and this page is honest about where it ends.
ReadAuthentication and rate limits
Every request carries two headers: the key that says who you are, and the store token that says which store you are talking about. Both come from the merchant.
ReadWebhooks
The merchant registers your URL and picks the events they want. We POST a signed JSON body to it and retry on failure. Verify the signature before you trust anything in the body.
ReadAPI reference
The API is GraphQL over a single endpoint. What follows is the SUPPORTED surface — the operations we commit to keeping stable for integrations.
ReadThemes and plugins
Beyond API integrations, the platform itself is extended with storefront themes and server plugins — new payment methods, shipping calculators, storefront designs. These ship inside the platform codebase and deploy with it. There is no theme or plugin upload, no marketplace, and no per-store install of third-party code — this page says what IS possible and where the full guides live.
Read