Testing and go-live

Go-live checklist

Everything to check before your app goes live with Limenia — setup, reports, webhooks, complaints, optional features and operations.

Setup

  • The tenant is active: GET /v1/ping with the production key returns tenantStatus: "active".
  • The API key is only in the backend’s secret store (LIMENIA_API_KEY), not in the app, the repository or logs. Key rotation is practised (create, deploy, revoke).
  • The webhook URL is https, public, without redirects, and the webhook is active. The secret is in LIMENIA_WEBHOOK_SECRET.
  • Supported actions in the dashboard match what the app can carry out.

Reports

  • External IDs are stable and pseudonymous (Firebase UID, Supabase user UUID or RevenueCat App User ID where a connector needs it).
  • The reporter, complaining person, author and device-check user come from the backend login, never from the app.
  • Reported content always includes its author as subject.
  • Every report has a stored idempotency key that stays the same on retries; retries with backoff on network errors, 429 and 5xx, Retry-After respected; a queue resends within 24 hours.
  • reasonCategory codes are agreed with the tenant; suspected abuse of minors uses child_safety.
  • Media URLs are https, fetchable without login, valid for at least an hour, in a supported format and at most 20 MB.
  • No e-mail addresses, IP addresses or similar data in any field. Logs contain IDs only.

Webhooks

  • The signature is verified over the raw body, constant time, 300 s tolerance, clock synced, tested with the test vector; previous secret accepted during rotation.
  • The receiver answers 2xx within 10 s and does heavy work asynchronously.
  • Duplicates are detected by event ID; actions are idempotent; older events do not overwrite newer ones.
  • Every action of Applying actions is handled (reject_submission only with reviews), restore follows restoreScope, unsupported actions are acknowledged with 2xx and logged.
  • The app lifts suspensions itself at suspendUntil.
  • The statement of reasons reaches the affected user as plain text, also when the account is blocked.
  • A reconciliation via GET /v1/subjects/{externalUserId}/status (e.g. at login) catches lost events.

Complaints and reporters

  • The backend accepts complaints, sets appellant.externalUserId from the login and stores appealId per person.
  • appeal.resolved answers reach the person completely as plain text.
  • Reports carry externalReportId (or reportId is stored); on reports.resolved reporters learn the outcome and the appealDeadline.
  • reporterWarning and 403 reporter_suspended are shown to the reporter; trustedFlaggerId is set only from the backend’s own records.

Reviews, signals, connectors (only if used)

  • Review types are active in the dashboard; submitted content is visible only to its author until review.decided; restricted and rejected are handled; GET /v1/reviews/{reviewId} catches lost events.
  • Signal types and rules exist; signals are batched (at most 100), keyed and contain no personal data of third parties.
  • Each connector shows a successful check in the dashboard and the user IDs match its requirement.
  • Ban evasion across apps: the identifier key is only in the backend’s secret store (LIMENIA_IDENTIFIER_KEY), never in the app; your implementation reproduces the check values of the dashboard; identifiers are sent at registration and on every change of e-mail address or phone number; the dashboard shows no identifiers discarded for a wrong format or key version.
  • Device connector: check at registration and every login (also of banned accounts before rejecting), Android tokens forwarded undecoded with a backend-issued request hash, fail-open, never ban on the device flag alone, test mode off in production, privacy texts updated.

Test and operations

  • Send test webhook succeeded, and every supported action was tested end to end in a test app (Testing).
  • Someone watches the Delivery log for failed deliveries and resends them.
  • Someone reads the troubleshooting page before the first incident.