Developers
Build on runmyhub.
One REST API for catalog, sales, inventory, payroll, time and finance — plus content-addressed offline sync and an MCP server. Anything the app can do, the API can do.
# 1 · Grab a sandbox key in the portal, then call the API
curl -H "x-api-key: $RUNMYHUB_KEY" \
"https://api.runmyhub.com/v1/products?limit=5"
# Public, no key needed — the whole API surface:
curl https://api.runmyhub.com/openapi.jsonWatch: why build on runmyhub
60 seconds — the platform from a developer's view.
Why developers like it
155 REST endpoints
Everything the app can do — catalog, sales, inventory, payroll, reports — reachable programmatically.
OpenAPI & versioned
Date-versioned and contract-tested. No breaking change without a new version.
Sandbox in minutes
In-memory demo with sample data. Test the whole flow — no real money.
Money-safe by design
Idempotency keys, rate limits, signed webhooks and unified error objects.
Quick reference
Grab a sandbox key in the portal, set the header, go — no real money, no SMS. The whole API surface is public at /openapi.json.
API
What you can build
155 endpoints over one tenant-safe data layer. A selection:
Catalog
Products, categories, taxes, attributes, modifiers, price lists, assortments.
Sales
Transactions, receipts, refunds — append-only and idempotent.
Reports & closures
Revenue, bestsellers, Z-closures, CSV/PDF export.
Locations & devices
Regions, shops, tills and device pairing over one hierarchy.
Sync & webhooks
Content-addressed offline sync (Merkle tree) + signed webhooks.
AI & MCP
AI assistant over your data + an MCP server that plugs AI tools in directly.
Also there: an MCP server
Connect your AI tools directly to runmyhub via the Model Context Protocol — your business becomes AI-ready without writing your own integration.
Up and running in minutes
Grab a sandbox key and build against the real API — before you ship a single line to production.