Skip to main content
To attribute events in the Greip dashboard to a user in your system, pass the user_id query parameter on supported requests (v1 alias: userID). Examples (API v2):
Include your API key on every request:
API v2 does not accept key in the query string or JSON body. See Authentication. When you include user_id, you can identify and track fraudulent activities on the Events page using values such as email, phone, or an internal user id.
Greip Dashboard - Real-time events page

Greip Dashboard - Real-time events page

ImportantYou do not need user_id on Payment Fraud Detection requests. Greip derives the identifier from fields such as customer_email, customer_phone, or customer_id in the payment payload.