IoneShop Developers

Build on IoneShop

API-first commerce for integrators, ERP/WMS partners, and automation teams. Authenticate with scoped API keys, consume webhooks, sync at scale.

Base: api.ioneshop.cloud/v1Sandbox: sandbox-api.ioneshop.cloudKeys: isk_test_… / isk_live_…OAuth 2.0 — in developmentGraphQL — in development

Platform overview

IoneShop is an API-first, headless, multi-tenant commerce platform for European merchants and enterprises. Integrators build against a stable HTTP contract — not against databases or internal services.

Why API-first

ConcernDirect database / internal accessIoneShop API
Tenant isolationEasy to break; one wrong query = breachEnforced tenant context on every call
Schema evolutionBreaks your ETL on every migrateVersioned /v1, /v2 with deprecation windows
SecretsCredentials sprawlScoped API keys, audit
ScaleUnbounded scans overload shared infraCursor pagination, webhooks, async jobs
ComplianceUncontrolled PII copiesDocumented processing, DSR hooks, audit trails
Supportability“Works on my dump”request_id, rate-limit headers, status page

Partners must not connect to commerce databases. Isolation is a security boundary, not an integration surface. For bulk export use documented sync APIs, webhooks, or Enterprise warehouse feeds under contract.

Currently available vs in development

CapabilityStatus
REST /v1 + API keys (isk_…)Available (public beta)
Webhooks (HMAC-signed)Available
OAuth 2.0 for partner applicationsIn development — use API keys today
GraphQLIn development — use REST /v1 today

Target contracts for OAuth and GraphQL are documented so you can plan; they are not live until announced in the changelog. See also Availability.

Architecture at a glance

flowchart LR
  ERP[ERP / WMS / CRM]
  APP[Partner apps]
  AUTO[n8n / Make / Zapier]
  API[api.ioneshop.cloud]
  WH[Signed webhooks]

  ERP --> API
  APP --> API
  AUTO --> API
  API --> WH
  WH --> ERP
  WH --> AUTO

Partners call HTTPS Partner API hosts only. Storefront and merchant back-office are separate surfaces.

Design pillars

  1. Headless commerce — storefront, merchant tools, and partner systems consume the same capabilities through APIs and events.
  2. Multi-tenant — each shop is an isolated tenant; keys and webhooks never cross tenants.
  3. Enterprise scalability — designed for many shops and large catalogs; pagination and async are mandatory.
  4. Security by default — TLS, least-privilege scopes, encrypted merchant secrets, signed webhooks.
  5. Availability — status page, retries with backoff, idempotency for unsafe writes.

Related