API reference

Request fields

The userData fields isCredible understands.

Send whatever you have. Each scenario uses the fields it needs and is skipped when they are missing, so partial data never causes an error. Unknown fields are ignored.

Identity#

FieldTypeDescription
emailstringThe user's email address
userIdstringYour stable ID for the user. Required for per-user history (logins).
accountId / customerIdstringAlternatives to userId
phonestringPhone number, if collected

Network and device#

FieldTypeDescription
ipstringThe client's IP address
deviceIdstringStable device or browser ID (how)
userAgentstringThe User-Agent header
webdriverbooleannavigator.webdriver
browserPluginsstring[]Plugin names
screenResolutionobject{ width, height }
platformstringnavigator.platform
geoLocationobject{ latitude, longitude, country }
previousLocationobjectLocation of the previous login
timeBetweenLocationsnumberSeconds since the previous login

Event#

FieldTypeDescription
accountCreationboolean or ISO dateSet on signups
paymentFingerprintstringCard fingerprint from your processor
loginAttemptsnumberFailed attempts before this login
passwordChangedbooleanThe user just changed their password
sensitiveActionPerformedbooleanA sensitive action is being performed

Usage and behaviour#

FieldTypeDescription
accountAgenumberAccount age (hours for credit checks, days for usage checks)
creditUsage / resourceUsagenumber 0-1 or objectShare of free credits or plan resources used
formCompletionTime, formInteractions, copyPasteEvents, hesitationPatterns, navigationFlow, referralSourceSignup form behaviour (details)

Each built-in scenario documents its inputs in the dashboard, with sample data you can test.