Developer docs
Integrate your app with Limenia: send reports from your backend, receive decisions as signed webhooks and meet the DSA obligations. Your content and your users stay in your app; your backend sends what a moderator needs to decide.
Getting started
- Overview
What Limenia does for your app, how a report becomes a decision, and the hard rules of every integration.
- Quickstart
Set up an app in the dashboard, configure your backend, and send your first report and webhook in a few minutes.
- Concepts
The terms of Limenia — tenant, app, API key, user file, content, report, case, decision, complaint, review request, signal, rule, policy, reporter and trusted flagger.
- Choose your path
Pick the integration guide for your app and backend, and see the five things every integration does.
- Overview
Integration guides
- Flutter with Firebase
Complete path for a Flutter app with Firebase Authentication and Cloud Functions as the backend.
- Flutter with Supabase
Complete path for a Flutter app with Supabase Auth and Supabase Edge Functions as the backend.
- Node.js with Express
Complete path for a Node.js backend with Express, based on the reference example.
- Go
Complete path for a Go backend with the standard library only.
- Python with FastAPI
Complete path for a Python backend with FastAPI and httpx.
- PHP with Laravel
Complete path for a Laravel 11 backend with drop-in files for the client, the controllers and the webhook.
- AWS Lambda
Complete path for a Node.js function on AWS Lambda behind a function URL or API Gateway.
- Any other backend
What to build with any HTTP client and HMAC library when there is no example for your stack.
- Flutter with Firebase
API reference
- API basics
Base URL, API keys, versioning, idempotency, errors, rate limits, limits, pagination and timestamps of the /v1 API.
- Reports
POST /v1/reports — report content or a user, with categories, media handling and how reports become cases.
- Users
PUT /v1/subjects/{externalUserId} and GET /v1/subjects/{externalUserId}/status — display names and the sanction status of a user.
- Complaints
POST /v1/appeals and GET /v1/appeals/{appealId} — complaints against decisions (Art. 20 DSA), reporters and misuse.
- Pre-moderation reviews
POST /v1/reviews and GET /v1/reviews/{reviewId} — have content checked before you publish it.
- Signals
POST /v1/signals — send observations about users that the tenant's rules turn into cases, priorities or flags.
- Device checks
POST /v1/devices/check — check the device of a user at registration and login with Play Integrity or DeviceCheck.
- Ban evasion across apps
The optional identifiers field — HMACs of e-mail address and phone number that link the user files of a tenant's apps. Coming soon.
- RevenueCat webhook receiver
POST /v1/integrations/revenuecat/{tenantId}/{appId} — the endpoint RevenueCat calls; not called by your backend.
- OpenAPI specification
The machine-readable description of every /v1 operation and webhook event, and how to use it.
- API basics
Webhooks
- Receiving webhooks
How Limenia calls your webhook — headers, signature check with test vector, retries, ordering, applying actions and showing the statement of reasons.
- Webhook events
Every webhook event with an example payload — decision.created, subject.status_changed, reports.resolved, appeal.resolved, review.decided and test.ping.
- Receiving webhooks
Connectors
- Firebase connector
Let Limenia disable and enable Firebase Authentication accounts directly when moderators suspend, ban or restore a user.
- Supabase connector
Let Limenia ban and unban Supabase Auth users directly when moderators suspend, ban or restore a user.
- RevenueCat connector
Let Limenia revoke promotional entitlements and end web subscriptions of banned users, and detect ban evasion through purchase transfers.
- Device connector
Tie bans to devices without fingerprinting, with Play Integrity Device Recall on Android and Apple DeviceCheck on iOS.
- Store reviews
Collect and answer the reviews of your app in the App Store and Google Play in Limenia — what you set up in App Store Connect, the Play Console and optionally GitHub.
- Firebase connector
Compliance
- DSA
What the Digital Services Act asks of your app, what Limenia does for you and what remains your job — notice and action, statements of reasons, complaints, trusted flaggers and transparency.
- Data protection
What to send to Limenia and what not, how reporters are pseudonymised, how long data is kept and where it is hosted.
- DSA
SDKs and tools
- SDKs and tools
Flutter packages limenia and limenia_device, the example backends, typed clients from the OpenAPI spec, llms.txt and the prompt for coding agents.
- SDKs and tools
Testing and go-live
- Testing
How to test an integration safely — a test app, self-tests a coding agent can run, the dashboard's webhook test and an end-to-end check.
- Go-live checklist
Everything to check before your app goes live with Limenia — setup, reports, webhooks, complaints, optional features and operations.
- Troubleshooting
Common errors when integrating Limenia and how to fix them — API answers, webhook signatures, deliveries, connectors and media.
- FAQ
Short answers to the questions developers ask most when integrating Limenia.
- Changelog
Changes of the public API (/v1 and webhook events), newest first.
- Testing