Get actionable insights into consumer behavior by integrating with Kount Consumer Insights, built on the Kount 360 platform. Integrate to gain access to the REST API endpoint, view your account in the portal, manage users, and more.
Create an API Key
Log in to Kount 360 to create your administrator password, retrieve your client ID, and create an API key. Set up your credentials before you authenticate or access the REST API.
- Open the Kount 360 Account Activation email sent to the administrator email address you provided Kount.
- Select Activate Account.
- From the welcome page, create your password, select a security image, and then select Create my Account to be redirected to the Kount 360 login page.
If you are not redirected to the Kount 360 login page automatically, navigate to the appropriate environment:
Sandbox
https://app-sandbox.kount.com/login
Production
https://app.kount.com/login
- Sign in to the Sandbox environment. The Production environment can only be accessed after a successful authentication with the sandbox environment.
- On the navigation menu, select Developer, and then Clients.
- Select New Client.
- Enter a name for the new client, and then select OK.
- In the New Client prompt, copy the API key and save it in a secure location.Note: Use the copy button to copy the API key. If you close the window without copying the API key, you must create a new API key using the options (...) menu. You are only allowed two active API keys per client.
- Select OK.
- On the Clients screen, locate the client you created to view the Client ID.
If desired, save the Client ID in a secure location. If you did not save the API key previously, you must select the arrow to preview and copy the API key before proceeding.
Authenticating with Kount 360
After you have provisioned your client ID and credentials in the self-service portal, retrieve a temporary bearer token.
Provide the client credentials in an HTTP POST to a specific login.kount.com URL, referred to as the “ISSUER” URL, which you will receive from Kount. With a successful exchange, the returned JSON provides a special bearer token, as well as an expiration date expires_in
. The expiration date is provided in seconds until expiration.
The API varies depending if you are calling the Sandbox or Production system. The values are:
Environment | Auth Server URL | API URL |
Sandbox | https://login.kount.com/oauth2/ausdppkujzCPQuIrY357/v1/token | https://api-sandbox.kount.com |
Production | https://login.kount.com/oauth2/ausdppksgrbyM0abp357/v1/token | https://api.kount.com |
The following provides example posts in popular languages:
Specifications for the Consumer Insights API
Endpoints:
Sandbox
api-sandbox.kount.com/identity/evaluate/v1
Production
api.kount.com/identity/evaluate/v1
Method: POST
Header Authorization: Bearer <token>
Header Content-Type: application/json
Standard Request Data Elements
Attribute | Type | Parameters | Description | Required/Optional |
clientId | string (clientId) ^[a-zA-Z0-9]{1,64}$ | Kount's unique identifier for a Client | Required | |
usecase | string | Use Case determines response payload (can be any comma-separated combination of payerInsights, walletInsights, fraudInsights, inputvalidation) | Required | |
deviceId | string (deviceId) ^[\w-]{0,64}$ | Device identifier | Optional | |
phoneNumber | string (phoneNumber) | Phone number for a Client’s user | Optional | |
emailAddress | string <email> (emailAddress) ^.+@.+\..+$ | Email address for a Client’s user | Optional | |
firstName | string (firstName) | First name for a Client’s user | Optional | |
lastName | string (lastName) | Last name for a Client’s user | Optional | |
address | object (v1Address) | Optional | ||
line1 | string (line1) ^[\w-]{0,256}$ | Street address - Line 1 | Optional | |
line2 | string (line2) ^[\w-]{0,256}$ | Street address - Line 2 | Optional | |
city | string (city) ^[\w-]{0,256}$ | Street address - City | Optional | |
state | string (state) ^[\w-]{0,256}$ | Street address - State/Province | Optional | |
postalCode | string (postalCode) ^[\w-]{0,20}$ | Street address - Postal Code | Optional | |
plus4 | string (plus4) ^[\w-]{0,4}$ | Street address - Last 4 Digits of a full 9-Digit US Postal code | Optional | |
countryCode | string (countryCode) ^[A-Z]{0,2}$ | Street address - Country | Optional | |
payment | object (v1Payment) | Optional | ||
paymentType | string (paymentType) ^[A-Z_]{1,12}$ | Enum: "APAY" "CARD" "PYPL" "CHEK" "NONE" "TOKEN" "GDMP" "GOOG""BLML" "GIFT" "BPAY" "NETELLER" "GIROPAY" "ELV" "MERCADE_PAGO""SEPA" "INTERAC" "CARTE_BLEUE" "POLI" "SKRILL" "SOFORT" "AMZN""SAMPAY" "ALIPAY" "WCPAY" "CRYPTO" "KLARNA" "AFTRPAY" "AFFIRM""SPLIT" "FBPAY" | Optional | |
paymentToken | string (paymentToken) ^[\w-]{0,64}$ | Payment token submitted by merchant for order (credit card, payer ID, routing/transit, MIC`R, and account number). | Optional |
Receive data from Consumer Insights
For additional support, review the API help documentation. Expand each section to review the responses available and associated fields.