Integration guides

Any other backend

What to build with any HTTP client and HMAC library when there is no example for your stack.

Implement the five steps of Choose your path with your HTTP client and HMAC library, following the API reference and Webhooks. Port the signature check from one of the examples (for instance Go or Python) and test it against the test vector before going live.

Checklist for your own implementation

  • Configuration: read LIMENIA_BASE_URL, LIMENIA_API_KEY and LIMENIA_WEBHOOK_SECRET from the environment or your secret store (see Quickstart).
  • HTTP client: Authorization: Bearer $LIMENIA_API_KEY, Content-Type: application/json, a client timeout of about 30 seconds, and retries with backoff on network errors, 429 and 5xx (see Retries).
  • Idempotency: one stored Idempotency-Key per logical request on POST /v1/reports, POST /v1/appeals, POST /v1/reviews and POST /v1/signals (see Idempotency).
  • People from your login: reporter, complaining person, author and device-check user come from your session, never from the request body of the app.
  • Webhook receiver: read the raw body (at most 1 MiB is plenty), verify the signature before parsing, deduplicate by event ID, answer 2xx within 10 seconds, handle every event type (see Webhook events).
  • Reconciliation: GET /v1/subjects/{externalUserId}/status at login catches lost events.

A minimal report call with curl:

Shell
curl -sS -X POST "$LIMENIA_BASE_URL/v1/reports" \
  -H "Authorization: Bearer $LIMENIA_API_KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: report-7f3c9a" \
  -d '{"source":"user","reasonCategory":"spam","reporter":{"externalUserId":"u_829"},"subject":{"externalUserId":"u_112"},"content":{"externalContentId":"comment_5521","contentType":"comment","text":"Text of the reported comment"}}'

Generate a typed client from the OpenAPI specification if your language has a generator.