Developer Portal v1

Official developer portal

Clear contracts. Safe integrations. Provable runtime.

Start with the correct request pattern, preserve business and branch scope, and build on FoodTech contracts without bypassing accounting, inventory, permissions, or audit trails.

Start the quickstart Explore the API

20Guides

4API references

6SDKs

Your first governed requestRead only

curl --request POST '<environment-base-url>/<verified-path>' \
  --header 'Authorization: Bearer <server-side-token>' \
  --header 'Idempotency-Key: <uuid-v4>' \
  --header 'Content-Type: application/json' \
  --data '{"business_id":"<authorized-business>"}'

Educational example — use only the environment URL and key issued to you.

Designed for real production boundaries

The portal documents contracts and constraints together, because correct integration is more than a successful HTTP status.

Get started

From the first safe request to a testable integration.

Platform contracts

Identity, scope, errors, versions, and module boundaries.

Integrations

Plus, Flowra, Fleetly, LuxPay, and business intelligence.

Reliability

Idempotency, retries, offline behavior, and outbox delivery.

Essential starting paths

The shortest route from an idea to a governed, testable integration.

Browse all

Reviewed

Get started

FoodTech platform overview

Understand how Console, applications, financial services, and analytics connect without breaking module ownership.

7 min

Foundation

Get started

Quickstart: your first governed request

Build a safe placeholder request and prove scope and idempotency before connecting an environment.

8 min

Reviewed

Get started

Environments and activation path

Separate local, sandbox, staging, and production; success in one environment never proves another.

6 min

Reviewed

Platform contracts

Authentication and credential safety

Choose the correct user, device, or partner identity and keep secrets out of clients and logs.

9 min

Reviewed

Platform contracts

Tenant isolation and branch scope

Enforce scope in authentication, queries, policy, and tests—not merely as a UI filter.

10 min

Reviewed

Reliability

Idempotency and retries

Make replay safe by binding a key to the same operation, scope, payload, and result.

11 min

Every surface has a contract and a boundary

Applications do not write across boundaries directly; changes pass through documented gateways with explicit scope keys.

BusinessApiGatewayConsole · trusted scope · audit

PlusConnect drafts, offline state, and sync without duplicating an order or bypassing the Sales/POS gateway.FlowraSync order state to kitchen display and hall surfaces through a fail-closed contract and safe local snapshot.FleetlyScope courier permissions, replay status changes safely, and treat GPS as sensitive data.LuxPayInitiate payment through standalone LuxPay and never treat an unverified redirect or callback as settlement proof.

Building your first FoodTech integration?

Begin in sandbox, prove idempotency and tenant scope, then request activation for the appropriate environment.

Open the sandbox guide