API Reference

Risk Screening

Smile Signals provides a powerful Risk Screening solution by delivering real-time risk signals using a person's mobile number or email address, from a wide variety of activities and events, to keep up to date in today's fast-paced financial landscape where accurate and timely risk assessment is crucial for making informed decisions.

The suite of Signals APIs can provide access to hundreds of risk signals, allowing you to pick and choose the signals that make sense for your use case and market segment.

Choose from the current suite of Signals:

SignalStatusDescription
SignalsBetaSmile's first risk screening service contains a preselected 30 of the most common risk signals so you can get started immediately with only your user's mobile number.
FootprintsAlphaObtain valuable insights on your user's digital footprint and online activities.
Multiple Application WarningAlphaDiscover early indications of your user's lending activities.
BlacklistAlphaEnsure your user is not blacklisted.
VerificationAlphaVerification can help you confirm matches between your user provided data and data from pre-verified and/or authoritative sources. Requires user's ID.

Checklist

Integration Steps

There are only a few steps in implementing Smile API's Risk Screening service in your process:

  1. Choose the Signal service you require

    Select from one of Smile's powerful Signals suite according to your requirements and the data you have.

  2. Provide the required input to Smile API

    Using the selected product, send the required input to Smile API, such as the user's phone number, email address, or other data, via the appropriate API endpoint.

    For example, you send the user's mobile number to the /signals endpoint to retrieve risk signal data.

  3. Retrieve the analyzed data

    Once data has been uploaded, our system automatically checks and/or calculates the response based on the service you have requested.

    Once these calculations are complete, the result's payload will be sent to you via webhook, or you may call the appropriate API directly. See the API documentation for more information.