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.
Flutter packages
| Package | What it does |
|---|---|
limenia |
API models and validation, a report queue with retries, the user’s own status, and ready-made widgets in package:limenia/ui.dart: report sheet, complaint form, statement of reasons, notice for restricted accounts. Flutter 3.35 or newer. |
limenia_device |
Optional plugin for the device connector: gets a Play Integrity or DeviceCheck token. Flutter 3.24 or newer, Android minSdk 24, iOS 15. |
flutter pub add limenia
flutter pub add limenia_device # only with the device connector- Both packages run in the app and never talk to Limenia directly: you implement
LimeniaTransportagainst your backend, which holds the API key. See Flutter with Firebase and Flutter with Supabase. - Pure Dart programs without Flutter (e.g. a Dart server) stay on
limenia0.11.x, which has no widgets. - Source code and issues: https://github.com/DL3KB/limenia-flutter (Apache 2.0).
Example backends
https://github.com/DL3KB/limenia-examples (Apache 2.0) has one complete backend per stack: Node.js with Express, Firebase Cloud Functions, Supabase Edge Functions, AWS Lambda, Go, Python with FastAPI and PHP with Laravel. Each one forwards reports, returns the user’s status, runs the device check and receives verified webhooks, with tests against the signature test vector. They use plain HTTP and the platform’s crypto, no SDK. Start from the integration guide of your stack.
Typed clients from the OpenAPI spec
There is no official server SDK package. The OpenAPI specification is complete enough to generate typed clients. For TypeScript, for example with openapi-typescript and openapi-fetch:
npx openapi-typescript https://limenia.eu/openapi/v1.yaml -o src/limenia.gen.ts
npm install openapi-fetchimport createClient from "openapi-fetch";
import type { paths } from "./limenia.gen";
const limenia = createClient<paths>({
baseUrl: process.env.LIMENIA_BASE_URL ?? "https://app.limenia.eu",
headers: { Authorization: `Bearer ${process.env.LIMENIA_API_KEY}` },
});
const { data, error, response } = await limenia.POST("/v1/reports", {
params: { header: { "Idempotency-Key": "report-7f3c9a" } },
body: {
source: "user",
reasonCategory: "spam",
reporter: { externalUserId: "u_829" },
subject: { externalUserId: "u_112" },
},
});
if (error) console.error(response.status, error.code); // problem+json, see API basics
else console.log(data.reportId, data.caseId);Other languages: use the OpenAPI generator of your choice. Keep retries, idempotency keys and the webhook signature check as described in API basics and Receiving webhooks; generators do not add them.
Documentation for coding agents
| File | Content |
|---|---|
| https://limenia.eu/llms.txt | Index of this documentation for language models (llmstxt.org) |
| https://limenia.eu/docs/integration.md | Every page of this documentation in one Markdown file |
| https://limenia.eu/llms-full.txt | All pages and the OpenAPI specification in one file |
| https://limenia.eu/openapi/v1.yaml | The OpenAPI specification |
Prompt for coding agents
The dashboard has a card Prompt for your coding agent on the app tab Connection and in the setup wizard. Pick your stack, copy the prompt and paste it into Claude Code, Cursor or Copilot. The prompt names the app, the base URL, the stack and the connectors switched on, tells the agent to read this documentation and to follow the hard rules, and lists what to build. It never contains the API key: put the key into LIMENIA_API_KEY of your backend first, and do not paste it into the chat.