Skip to main content
POST
/
v2
/
watch
/
event
Dispatch events
curl --request POST \
  --url https://api.prelude.dev/v2/watch/event \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "events": [
    {
      "target": {
        "value": "<string>"
      },
      "label": "<string>"
    }
  ]
}
'
{
  "status": "success",
  "request_id": "<string>"
}
Use this endpoint to send custom fraud signals from your application: user actions you label yourself (for example account.banned, payment.chargeback) together with a confidence level. Events let you capture fraud patterns that are specific to your product. They are weighted when Prelude scores traffic alongside network and phone intelligence. Events are not the same as Feedback: feedback is optional and only describes steps in your own phone verification funnel. Many customers use Events alone (plus Predict at gates) without Feedback. Use both when you operate your own verification flow and also emit product fraud labels.

​
Confidence

Each event must include a confidence value: how much you trust that the label truly reflects fraud or abuse for that user. Allowed values, from lowest to highest trust in the signal, are:
ValueTypical use
minimumWeak or noisy signal — use when you are unsure the event indicates fraud
lowSome suspicion, not enough to act alone
neutralInformational; no strong lean either way
highStrong product-side signal of abuse
maximumDefinitive action in your systems (for example a confirmed account.banned)
Prelude weights events when scoring a phone number: higher confidence increases influence; minimum signals contribute lightly and mainly help filter traffic you already distrust. See Introduction — Event confidence for the full pipeline behavior.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
​
events
object[]
required

A list of events to dispatch. A maximum of 100 events can be sent in a single request.

Maximum array length: 100

Response

OK

​
status
enum<string>
required

The status of the events dispatch.

Available options:
success
Example:

"success"

​
request_id
string
required

A string that identifies this specific request. Report it back to us to help us diagnose your issues.

Example:

"3d19215e-2991-4a05-a41a-527314e6ff6a"