Coming soon

Developers

A commerce API you can build on without surprises.

Everything the admin does goes through the same REST API you get: one contract-first OpenAPI 3.1 document, RFC 7807 errors, integer cents and an isolated database per store.

Open the API reference View openapi.json

Developers

REST API

Contract-first, not documentation-later.

The OpenAPI 3.1 document is the source of truth: request and response schemas are typed and validated against it, and the interactive Scalar reference at api.inaishop.com/docs is rendered from that same document — so the docs cannot drift from the API.

  • OpenAPI 3.1 contract, public at api.inaishop.com/openapi.json
  • Errors as RFC 7807 problem details — machine-readable, always
  • Every monetary amount is an integer in cents — no floats

Webhooks v2

Nineteen events, delivered the way you would build it.

Subscribe to order, product, customer, payment, subscription, cart, review and inventory events. Retries back off on your terms — exponential or linear — any delivery can be replayed, and every request carries a W3C traceparent header for end-to-end tracing.

  • Configurable retries: exponential or linear backoff
  • Replay any delivery after your endpoint was down
  • W3C traceparent header on every delivery

All 19 events

  • order.created
  • order.updated
  • order.cancelled
  • order.fulfilled
  • order.refunded
  • product.created
  • product.updated
  • product.deleted
  • customer.created
  • customer.updated
  • payment.succeeded
  • payment.failed
  • payment.refunded
  • subscription.created
  • subscription.cancelled
  • subscription.renewed
  • cart.abandoned
  • review.created
  • inventory.low

The rest of the surface

Scopes, metafields, agents and a sandbox.

The pieces around the API that make an integration livable — all shipping today.

  • API keys with 14 scopes, default-deny

    Keys carry granular scopes — products, orders, customers, catalog, webhooks, analytics, settings and invoices, read and write. Whatever you did not grant is denied, and that default-deny behaviour is itself verified by tests.

  • Metafields

    Attach your own structured data to products and customers — integration state lives on the record it belongs to, not in a side database.

  • An agentic surface

    MCP server (6 tools), signed UCP manifest at /.well-known/ucp.json, ACP checkout, AP2 mandates, llms.txt and agent-feed.jsonl — your integration can simply be an AI agent.

  • Sandbox stores

    Develop against a sandbox tenant that resets every day — break things freely, demo safely, never touch production data.

We're about to open

We're putting the finishing touches on the official launch of InAI Shop. Leave your email and we'll let you know the moment sign-ups open.

Double opt-in. Unsubscribe in one click.