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,
/v1answers 429rate_limitedwithRetry-Afterinstead 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/reportsandPOST /v1/reviewscheckcontent.contextlikePOST /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 400validation_failedwith codeinvalidat/content/context. Before, such a request failed with 500 or, with an array in an array, was stored.POST /v1/signals: acontextkey longer than 128 bytes answers 400validation_failedwith codeinvalid(before: 500).PUT /v1/subjects/{externalUserId}answers 403tenant_not_activewhile the tenant is in onboarding or suspended, like the other writing operations, and writes nothing.GET /v1/subjects/{externalUserId}/statuskeeps answering in every state.
0.28.0 (2026-10-12)
- New optional
identifiersobject (keyVersion,email,phone: HMACs, never plain values) for ban evasion across apps (coming soon) onPOST /v1/reportsandPOST /v1/reviews(subject.identifiers),POST /v1/signals(per signal),POST /v1/devices/checkandPUT /v1/subjects/{externalUserId}. Identifiers never cause an error and never change a response. PUT /v1/subjects/{externalUserId}:displayNameis no longer required; send at least one ofdisplayNameandidentifiers. WithoutdisplayNamethe stored name is kept.- New reserved
reasonCategorycross_app_banfor reports Limenia creates itself.
0.22.0 (2026-10-07)
POST /v1/reports: new optionalgoodFaith(the reporter confirmed the report is accurate and complete, Art. 16(2)(d) DSA). Only withsource: user.
0.20.0 (2026-10-05)
- New
POST /v1/devices/checkfor the device connector, with errorsinvalid_device_tokenanddevice_connector_not_configured. Fail-open: when the provider is unreachable the answer is 200 withstatus: unevaluated. POST /v1/signalsrejects the system signal types (device_flagged,device_risk) withsignal_type_unknown.
0.19.0 (2026-10-05)
statementOfReasons.structuredhas the new fieldautomation(none,partial,full).automatedDecisionistrueonly withfull. Earlier decisions reportnone.
0.18.0 (2026-10-05)
- New
POST /v1/signals: 1 to 100 signals per request, all or nothing,202 Accepted. RequiresIdempotency-Key. Errorsignal_type_unknown.
0.16.0 (2026-10-05)
POST /v1/reports: new optionaltrustedFlaggerId(Art. 22 DSA) and, in the response,reporterWarningwhile a warning against the reporter stands.- New error 403
reporter_suspendedwithsuspendedUntilonPOST /v1/reportsand on complaints of reporters (Art. 23 DSA). statementOfReasons.structuredhas the new fieldnoticeSource(notice,trusted_flagger,own_initiative).
0.15.1 (2026-10-04)
- When a complaint against
ban_userorsuspend_userends with a milder decision, the ban or suspension is lifted: you getsubject.status_changedin addition todecision.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
reasonCategorycodes documented:child_safetyandprotection_of_minors(urgent, no media copy) andban_evasion.source: systemalso covers reports Limenia creates itself.
0.14.0 (2026-10-03)
- With the RevenueCat connector,
statementOfReasons.textcan contain generic sentences about purchases.
0.13.2 (2026-10-03)
decision.created: newdecision.restoreScope(contentoraccount) forrestore.PUT /v1/subjects/{externalUserId}andGET /v1/subjects/{externalUserId}/statusare never blocked by the plan; an expired suspension is reported asactiveat once.- Field errors (
errors) also come with specific codes such asreview_type_unknown.
0.13.0 (2026-10-03)
POST /v1/reviewsrequires a plan with reviews (403feature_not_in_plan) and a subscription that has not expired (402subscription_required). Reports and complaints are never blocked by the plan.
0.12.1 and 0.12.2 (2026-10-03)
decision.created: newdecision.reviewIdfor decisions on review requests, also for a new decision after a complaint against one.
0.12.0 (2026-10-03)
- New
POST /v1/reviewsandGET /v1/reviews/{reviewId}for pre-moderation, new webhook eventreview.decided, new actionreject_submission, new errorreview_type_unknown.
0.11.0 (2026-10-02)
- New
POST /v1/appealsandGET /v1/appeals/{appealId}for complaints, new webhook eventsappeal.resolvedandreports.resolved. decision.created: newappealIdandreplacesDecisionId.POST /v1/reports: new optionalexternalReportId.
0.9.0 (2026-10-02)
- Breaking: API keys start with
lm_live_orlm_test_; the webhook headers areLimenia-Event-Id,Limenia-Event-TypeandLimenia-Signature.
0.6.0 (2026-10-01)
- Webhooks: events
decision.created,subject.status_changedandtest.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 asapplication/problem+json.