Fleximotion Developer Portal

One portal for every future API consumer.

This first portal turns the build sequence into something executable: versioned REST contracts, integration rules, webhook conventions, and review expectations that every Fleximotion frontend, backend service, vendor, and automation can share.

6 domain APIs drafted

/v1 versioned from day one

API contracts before apps

Identity

Amoeba

Ops

TMS

Frontends compose. Backends own.

Integration model

Rules that keep systems from drifting.

APIs are authority

Events notify consumers that something changed. Current state is fetched from the owning API.

One owner per entity

Identity owns people, Amoeba owns org units, HR owns prospects, Ops owns operations, TMS owns management work.

Idempotent writes

Every cross-system mutation requires an Idempotency-Key header and audit history.

No database bypass

Frontends and services integrate through documented APIs, never direct writes to another domain database.

REST APIs

Contract explorer

API

POST

/transfer-price-events

Auth

Bearer token or scoped service token.

Operational notes

Use an Idempotency-Key on writes. Store request IDs in logs.

Example request

Example response

Events & webhooks

At-least-once delivery, API-backed truth.

personnel.ready_for_ops_onboarding operator.activated alert.resolved transfer_price_event.published_to_ops

{
  "event_id": "evt_01JZ7QAJ5V6VGZB1WTP3NQ9JGN",
  "event_type": "operator.activated",
  "source_system": "ops",
  "schema_version": "1.0",
  "occurred_at": "2026-06-04T09:00:00Z",
  "idempotency_key": "operator_activated:operator_01JZ7Q...",
  "data": {
    "operator_id": "operator_01JZ7Q...",
    "person_id": "person_01JZ7M..."
  }
}

Build sequence

Contract-first rollout.

Contract foundation + developer portalShared IDs, auth, events, OpenAPI skeletons, docs website.
Identity + AmoebaPeople, users, service tokens, amoeba definitions, initial seed data.
Ops MVPBolt/Uber ingestion, alerts, acknowledgement, mobile PWA, migration tools.
Ops depthCash, closeout, incidents, inspections, P&L, leaderboards, exports.
HR, TMS, analyticsRecruitment workflows, management work system, warehouse and automation.

Auth & service tokens

Human users authenticate through Identity. Cross-system clients use scoped service accounts and pass Authorization: Bearer <token>.

curl -H "Authorization: Bearer $FLEXI_TOKEN" \
  https://api.fleximotion.example/ops/v1/alerts?date=2026-06-04

Errors & idempotency

Mutating requests include Idempotency-Key. Errors always include a stable code, message, request ID, and optional field details.

{
  "error": {
    "code": "validation_failed",
    "message": "target_amoeba_id is required",
    "request_id": "req_01JZ7RQF2H...",
    "details": [{ "field": "target_amoeba_id", "reason": "required" }]
  }
}

Frontend review loop

Every frontend phase should expose a local preview URL, run browser checks on mobile and desktop, and capture screenshots so stakeholders can give feedback while screens are still cheap to change.

npm run dev
npm run test:e2e
# Share localhost URL and verified screenshots for review.

Monnify sandbox

Provision one reserved account per operator, verify signed deposit events, and use scheduled reconciliation as the correctness backstop.

Open the setup and test guide

Analytics console

Compose Foundation, Ops and Payments data into the Phase 4E Net Earnings control room with day/week/month periods, scoped amoeba drilldowns, HE, utilisation, breakeven and leakage signals.

Open the integration guide

Ops operational depth

Phase 4F workflows: deviation reasons, incidents, inspections, maintenance, camera media, expenses, amoeba P&L with central-cost allocation, transfer pricing, leaderboards and the manager escalation queue.

Open the operational depth guide