Getting Started

Revylta scores a lead or signup for fraud/abuse risk in real time. You send us what you know about the visitor (email, IP, user agent), we return a score, a risk level, and the reasons behind it — usually in well under a second.

How an integration fits together

Your backend (or signup page) calls POST /api/v1/score with the visitor's details.
You get back a risk level (low / medium / high) and a block flag you can act on immediately.
Optional: a small browser script reports additional device/behavior signals after the page loads, which sharpens later requests for the same visitor.
Optional: once you know how a lead turned out (converted, chargeback, fraud, etc.) you send that back via the Outcomes API — it's how we keep tuning accuracy for your traffic.

Two ways to integrate

Mode	When to use it	Where to start
Server-side (API)	Your backend already receives the signup/lead and can make an outbound HTTP call.	Score API
Signup page script	You want device/behavior signals captured on the signup page itself, with minimal backend work.	Signup Page Mode

Base URL

https://revylta.com

All endpoints below are relative to this URL. All requests and responses use JSON.

What you'll need

A Server API Key — sent as a header on every backend call. Keep this secret.
A Browser Key (only if you use browser telemetry or the signup script) — safe to expose in front-end code, and restricted to domains you allow.

Ask your Revylta contact for these if you don't have them yet — see Authentication.

Note: Every code sample in these docs uses a placeholder key. Swap in your real key before running them.