API reference
Signals
POST /v1/signals — send observations about users that the tenant's rules turn into cases, priorities or flags.
POST /v1/signals
Signals are observations about users that are not reports: score jumps, implausibly many actions, many new accounts. A signal creates no case; rules of the tenant (dashboard, tab Moderation) turn signals into a case, a higher priority or a flag on the user file. Limenia never sanctions on its own. Requires a plan with signals.
curl -sS -X POST "$LIMENIA_BASE_URL/v1/signals" \
-H "Authorization: Bearer $LIMENIA_API_KEY" -H "Content-Type: application/json" \
-H "Idempotency-Key: signals-6f1c0d2e" \
-d '{"signals":[{"type":"score_jump","externalUserId":"u_112","value":4200,"context":{"level":"7"}}]}'Response 202 Accepted: { "accepted": 1 }.
signals: 1 to 100 entries, all or nothing (one invalid signal rejects the request). A request counts once against the rate limit, so batch.- Each signal:
type(code of an active signal type of the app, created in the dashboard;^[a-z0-9_]{2,40}$),externalUserId(1 to 128),value(optional number),occurredAt(optional, at most 24 hours back and 5 minutes ahead; default the time of receipt),context(optional, at most 4 KB, IDs and technical details only; keys of 1 to 128 bytes, no keys like__x__, no arrays in arrays, at most 10 levels),identifiers(optional, see Identifiers; a signal does not create a user, so identifiers for a user Limenia does not know yet are discarded). - The system types
device_flaggedanddevice_risk(device connector) andban_evasion_cross_app(ban evasion across apps) are created by Limenia; you never send them. - Values from a device can be faked: send signals from your backend where it can check them. Signals are kept briefly (default 30 days).
Errors: 400 validation_failed, signal_type_unknown (field error at /signals/{i}/type); 401; 402 subscription_required; 403 feature_not_in_plan, tenant_not_active; 409 idempotency_key_reused; 429.
Signal types and rules
Create signal types and rules in the dashboard (tab Moderation), then send batches from your backend.
- A signal type has a code (the
typeyou send), a name and an active switch. Types are never deleted, only deactivated. - A rule has one or two conditions (combined with AND), one action and a cooldown per user (default one day).
- Conditions: a number of signals of one type within a time window, optionally with a minimum
value; or a number of different reporters within a time window (reports withsource: systemnever count). - Actions: open a case (as a report with
source: systemat a chosen priority), raise the priority of open cases of the user tohighorurgent, or put a flag on the user file.
- Conditions: a number of signals of one type within a time window, optionally with a minimum
- Rules can be tried out against the signals of the last days before switching them on. A moderator always decides; Limenia never sanctions because of a rule.