Testing and go-live

Changelog

Changes of the public API (/v1 and webhook events), newest first.

The current API version is 0.33.0 (2026-10-15). The list contains only versions that changed the public API (the /v1 operations and the webhook events); versions in between changed nothing you can see. All changes within /v1 are additive unless marked otherwise, so ignore unknown fields and handle new enum values (see Versioning).

0.33.0 (2026-10-15)

  • Requests with an API key that does not exist: after many of them from one client address, /v1 answers 429 rate_limited with Retry-After instead of 401. Keys that were used successfully shortly before are not affected.
  • Media URLs: each URL is fetched once per content, a fetch may take 10 seconds in total, and timeouts, connection errors, 429 and 5xx of the source are final after the third attempt. Above a fair-use quota per tenant, media are skipped with the reason quota_exceeded; the report itself is always accepted.
  • Webhooks: after 5 failed deliveries in a row (timeout, connection error, 429 or 5xx) the deliveries of the app pause for 5 minutes and then resume on their schedule; nothing is lost, and a successful webhook test ends the pause at once.

0.32.0 (2026-10-15)

  • POST /v1/reports and POST /v1/reviews check content.context like POST /v1/signals: an empty key, a key longer than 128 bytes or of the form __x__, an array in an array or more than 10 levels answer 400 validation_failed with code invalid at /content/context. Before, such a request failed with 500 or, with an array in an array, was stored.
  • POST /v1/signals: a context key longer than 128 bytes answers 400 validation_failed with code invalid (before: 500).
  • PUT /v1/subjects/{externalUserId} answers 403 tenant_not_active while the tenant is in onboarding or suspended, like the other writing operations, and writes nothing. GET /v1/subjects/{externalUserId}/status keeps answering in every state.

0.28.0 (2026-10-12)

  • New optional identifiers object (keyVersion, email, phone: HMACs, never plain values) for ban evasion across apps (coming soon) on POST /v1/reports and POST /v1/reviews (subject.identifiers), POST /v1/signals (per signal), POST /v1/devices/check and PUT /v1/subjects/{externalUserId}. Identifiers never cause an error and never change a response.
  • PUT /v1/subjects/{externalUserId}: displayName is no longer required; send at least one of displayName and identifiers. Without displayName the stored name is kept.
  • New reserved reasonCategory cross_app_ban for reports Limenia creates itself.

0.22.0 (2026-10-07)

  • POST /v1/reports: new optional goodFaith (the reporter confirmed the report is accurate and complete, Art. 16(2)(d) DSA). Only with source: user.

0.20.0 (2026-10-05)

  • New POST /v1/devices/check for the device connector, with errors invalid_device_token and device_connector_not_configured. Fail-open: when the provider is unreachable the answer is 200 with status: unevaluated.
  • POST /v1/signals rejects the system signal types (device_flagged, device_risk) with signal_type_unknown.

0.19.0 (2026-10-05)

  • statementOfReasons.structured has the new field automation (none, partial, full). automatedDecision is true only with full. Earlier decisions report none.

0.18.0 (2026-10-05)

  • New POST /v1/signals: 1 to 100 signals per request, all or nothing, 202 Accepted. Requires Idempotency-Key. Error signal_type_unknown.

0.16.0 (2026-10-05)

  • POST /v1/reports: new optional trustedFlaggerId (Art. 22 DSA) and, in the response, reporterWarning while a warning against the reporter stands.
  • New error 403 reporter_suspended with suspendedUntil on POST /v1/reports and on complaints of reporters (Art. 23 DSA).
  • statementOfReasons.structured has the new field noticeSource (notice, trusted_flagger, own_initiative).

0.15.1 (2026-10-04)

  • When a complaint against ban_user or suspend_user ends with a milder decision, the ban or suspension is lifted: you get subject.status_changed in addition to decision.created.

0.15.0 (2026-10-03)

  • New POST /v1/integrations/revenuecat/{tenantId}/{appId}, the receiver for RevenueCat webhooks (called by RevenueCat, not by your backend).
  • Reserved reasonCategory codes documented: child_safety and protection_of_minors (urgent, no media copy) and ban_evasion. source: system also covers reports Limenia creates itself.

0.14.0 (2026-10-03)

  • With the RevenueCat connector, statementOfReasons.text can contain generic sentences about purchases.

0.13.2 (2026-10-03)

  • decision.created: new decision.restoreScope (content or account) for restore.
  • PUT /v1/subjects/{externalUserId} and GET /v1/subjects/{externalUserId}/status are never blocked by the plan; an expired suspension is reported as active at once.
  • Field errors (errors) also come with specific codes such as review_type_unknown.

0.13.0 (2026-10-03)

  • POST /v1/reviews requires a plan with reviews (403 feature_not_in_plan) and a subscription that has not expired (402 subscription_required). Reports and complaints are never blocked by the plan.

0.12.1 and 0.12.2 (2026-10-03)

  • decision.created: new decision.reviewId for decisions on review requests, also for a new decision after a complaint against one.

0.12.0 (2026-10-03)

  • New POST /v1/reviews and GET /v1/reviews/{reviewId} for pre-moderation, new webhook event review.decided, new action reject_submission, new error review_type_unknown.

0.11.0 (2026-10-02)

  • New POST /v1/appeals and GET /v1/appeals/{appealId} for complaints, new webhook events appeal.resolved and reports.resolved.
  • decision.created: new appealId and replacesDecisionId. POST /v1/reports: new optional externalReportId.

0.9.0 (2026-10-02)

  • Breaking: API keys start with lm_live_ or lm_test_; the webhook headers are Limenia-Event-Id, Limenia-Event-Type and Limenia-Signature.

0.6.0 (2026-10-01)

  • Webhooks: events decision.created, subject.status_changed and test.ping, signed with HMAC-SHA256.
  • New error code unavailable.

0.4.0 (2026-10-01)

  • First public API: GET /v1/ping, POST /v1/reports, PUT /v1/subjects/{externalUserId}, GET /v1/subjects/{externalUserId}/status, with API keys, idempotency keys and errors as application/problem+json.