Skip to main content
POST

Authorizations

token
string
header
required

Your Youverify API secret key. Never expose client-side.

Headers

token
string
required

API secret token

Body

application/json

TM transaction event (routed by eventCategory).

eventType
enum<string>
required

The kind of event: transaction or account_activity (a login or a card event).

Available options:
transaction
Example:

"transaction"

externalEventId
string
required

Your own unique id for this event. It is the idempotency key: sending the same id again returns the original evaluations instead of starting new ones.

Maximum string length: 128
eventStatus
enum<string>
required

Where the event is in its life. Only a triggering status starts a workflow (a transaction: acknowledged, pending; a login: attempted; a card event: requested, activated, pin_changed); any other status is stored and still updates the aggregates. Which statuses are allowed depends on the kind of event.

Available options:
acknowledged,
pending,
completed,
attempted,
successful,
requested,
issued,
activated,
frozen,
suspended,
unfrozen,
pin_changed,
closed,
canceled,
failed,
reversed
Example:

"acknowledged"

eventCategory
enum<string>
required

Routes the event to the workflows tagged with this category, for example finance or kyc.

Available options:
finance,
kyc,
travel_rule,
user_event,
gambling,
audit_trail_event,
crypto,
insurance,
investment
data
object
required

The transaction: its payment type, amounts, parties and the flags you decide (isInternational, isNight).

schemaVersion
string

Version of this payload schema. Only major version 1 is supported.

Pattern: ^1\.\d+$|^1\.\d+\.\d+$
Example:

"1.2"

lifecycleId
string

Your identifier tying together several events that belong to the same lifecycle, for example one session or one payment.

Maximum string length: 128
metadata
object

Information about the event itself, the same on every event type. Any other key you add is kept and passed on.

Response

Event accepted. evaluations lists any evaluations the event started.

success
boolean
required
Example:

true

statusCode
enum<integer>
required
Available options:
202
Example:

202

message
enum<string>
required
Available options:
Event accepted
Example:

"Event accepted"

data
object
required