INTEGRATION OPTIONS

Trustfull products integrate into your system through either backend API calls, frontend SDK components, or a combination of both. The table below provides a high-level view of the technical integration model required for each product.

Product	API	Web SDK
Trustfull Phone	✅	❌
Trustfull Email	✅	❌
Trustfull IP	✅	❌
Trustfull Onboarding	✅	❌
Trustfull Session	✅	✅
Trustfull Login	✅	✅
Trustfull Domain	✅	❌
Email Disposable	✅	❌
Phone Validation	✅	❌
Phone Disposable	✅	❌
IP Proxy Detection	✅	❌
Phone Data Breaches	✅	❌
Phone Portability	✅	❌
Phone to Name	✅	❌

How Trustfull APIs Work

Most Trustfull products follow a simple backend integration model: your system sends input data (e.g. phone, email, IP, domain, or user information) to the Trustfull API, which orchestrates data enrichment, evaluates risk, and returns a structured response including signals, features, and a score.

The diagram below illustrates this standard flow shared across products such as Phone, Email, IP, Domain, and Onboarding. As shown in the table, Trustfull Login and Trustfull Session follow a different integration pattern, combining backend APIs with a JavaScript SDK for client-side signal collection: see the dedicated Login and Session pages for full integration details.

FAQ

Where do I get the OpenAPI (Swagger) definition?

The OpenAPI definitions are published alongside the API Reference.

The /swagger endpoint on the API itself is a development-only tool and is not available in staging or production.

If you need the raw specification file for client code generation, contact support and we will provide an export.