Quick Links

Signal Score for Email Integration Guide

The Email Signal API is a high-fidelity intelligence tool designed to provide instant clarity on the risk and authenticity of any email address. By leveraging Equifax historical data, domain reputation analysis, and behavioral patterns, a single API call delivers a comprehensive trust profile to guide your decision-making.

This solution injects identity and risk signals directly into your onboarding and transactional workflows, allowing you to verify real users and mitigate fraud without introducing friction.

For complete data specifications, request parameters, and response flag definitions, refer to the Signal Score for Email API documentation.

Signal Score for Email API endpoints

To get a Signal Score API response, you must submit an email in the API request to the Signal Score for Email API endpoint.

Signal Score for Email API sandbox endpoint

https://api-sandbox.kount.com/email/risk/v2

Signal Score for Email API production endpoint

https://api.kount.com/email/risk/v2

HTTP Request Details

Method: POST

Headers required:

  • Authorization: Bearer <token>

  • Content-Type: application/json

For complete data specifications, request parameters, and response flag definitions, refer to the Signal Score for Email API documentation.

Authentication

To begin using the API, you must generate an API key in Kount 360, which is then used to obtain a temporary bearer token for secure requests.

Generate an API key

In Kount 360, after you have activated your organization, you can generate API keys to send data securely to Equifax. Only users with the Owner role permissions can generate, delete, or edit API keys.

Caution

You must have an initialized client before you can create an API key.

  1. Sign in to Kount 360.

    There are two integration environments: https://app-sandbox.kount.com and https://app.kount.com. Only integrate into the sandbox environment if you are integrating a pre-production environment without production data for testing.

  2. Select Admin, and then Product Configuration.

  3. In System Settings, select API Keys.

    All initialized clients display.

    Note

    You must be the organization Owner to access System Settings.

  4. For the client you want to create an API key for, select Generate API Key.

    The new API key is generated. A prompt displays with the ability to copy the API key and add a description.

  5. Copy the API key, and then store it in a secure location.

    Note

    The API key is not viewable after closing the prompt. You must store it in a secure location for future reference. If the API key is compromised or lost, create a new API key and delete the compromised one.

  6. Enter a description for the store or environment that will be connected to the API key, and then select Confirm.

API keys are organized under each client on the API Keys page. Expand the client to view your API keys, the descriptions, and when client details were created.

Create a bearer token

After you have provisioned your API credentials in the portal, retrieve a temporary bearer token to authenticate calls to the Kount 360 API. Provide the API key in an HTTP POST to a specific login.equifax.com URL.

With a successful exchange, the returned JSON provides a bearer token, which is the access_token property. The exchange also provides an expiration date, the expires_in property, provided in seconds until expiration. The API to retrieve the bearer token depends on if you are calling the sandbox or production environment.

Caution

Tokens issued by login.equifax.com expire after 20 minutes, but client credentials remain valid unless revoked. Minimize calls to the /token endpoint by implementing token expiration handling in your customer applications. Always check if a token has expired before requesting a new one, as excessive calls to the /token endpoint could result in rate limiting.

The values are:

Sandbox

Auth Server URL:

https://login-uat.equifax.com/as/token

API Service Host:

https://api-sandbox.kount.com

Production

Auth Server URL:

https://login.equifax.com/as/token

API Service Host:

https://api.kount.com

After obtaining the bearer token, use it to authenticate requests to the Kount 360 API. Include the token in the Authorization header of your HTTP API request, prefixed with Bearer {bearer token}.

To prevent authentication issues, refresh the token before it expires.

Integration workflow

The standard workflow involves passing an email address to the API the moment a user attempts an action (like signing up or checking out) to evaluate their risk instantly.

Making your first evaluation call

After configuring your environment, make your first evaluation request. This test validates your integration by confirming that your application can connect to the API, submit data for analysis, and receive the resulting response.

Bash

Python

TypeScript

Go

Was this article helpful?
0 out of 0 found this helpful