Getting started

Choose your path

Pick the integration guide for your app and backend, and see the five things every integration does.

Which guide

Is the app a Flutter app? Then pick the guide of its backend: Firebase with Cloud Functions or Supabase with Edge Functions. With another backend, use the Flutter part of those guides (LimeniaTransport) together with the guide of your backend. Without a Flutter app, pick the guide of your backend.

Your stack Guide
Flutter app, Firebase Authentication, Cloud Functions Flutter with Firebase
Flutter app, Supabase Auth, Edge Functions Flutter with Supabase
Flutter app with another backend Flutter part of Flutter with Firebase plus your backend’s guide
Node.js with Express or a similar framework Node.js with Express
Go Go
Python with FastAPI Python with FastAPI
PHP with Laravel PHP with Laravel
AWS Lambda AWS Lambda
Anything else with HTTPS Any other backend

What every integration does

Every path does the same five things. Check them off when you are done:

  1. Forward reports from the app to POST /v1/reports, reporter from the login, Idempotency-Key passed through, retries with backoff (Reports).
  2. Return the user’s own status from GET /v1/subjects/{externalUserId}/status (for the signed-in user only, see Users).
  3. Receive webhooks: raw body, signature check, dedupe by event ID, every event type handled (Webhooks, Webhook events).
  4. Apply the actions to your data (Applying actions) and show the statement of reasons to the affected user.
  5. Forward complaints (POST /v1/appeals, see Complaints), because affected users and reporters have a right to complain. Optionally reviews, signals and device checks.

The example backends

All example backends live in https://github.com/DL3KB/limenia-examples. They use plain HTTP and the platform’s crypto, no SDK, and contain placeholders you must replace: the login stub (it trusts a header X-User-Id and refuses to run with NODE_ENV=production where applicable) and the action functions (remove content, ban user, notify). Each example also includes the device check (/devices/request-hash, /devices/check) and tests against the signature test vector.

If you work with a coding agent, the dashboard has a ready-made prompt for it (see SDKs and tools).