How to integrate Email Hippo Assess into a decision engine

Connect Email Hippo Assess to a decision engine, step by step. This guide covers API key setup and explains how to create the data source in Decisimo and add the call to your decision flow so email, IP, and optional identity fields are evaluated during sign-up.

Email Hippo provides a service for verifying and profiling email addresses. It can be used to evaluate users during sign-up, which helps prevent garbage registrations and fraud down the road. Its services also include an IP address input, which helps prevent bot-driven registrations.

First name and last name are optional inputs. Because they are sensitive PIIs, you should decide whether to share customer data with another provider at that depth according to your data protection standards.

1.

Get an account API key from Email Hippo

  • Email Hippo has no gatekeepers restricting account creation, and no one will force you into a demo call. Go to the Email Hippo sign-up page and create your account.

    https://signup.emailhippo.com/signup/
  • After you create your account and log in, open the API Keys Dashboard. Retrieve your API key.
    Email Hippo API Dashboard
2.

Create a data source in Decisimo Portal

  • Select New in Data sources, ask the AI Assistant to configure the provider, then check and apply its proposal.
  • Replace the highlighted __YOUR_API_KEY__ with the API key you obtained from Email Hippo.
    Definition of Email Hippo Assess data source
  • Email Hippo Assess requires one parameter: the email address. You can also provide other relevant parameters:
    • emailAddress
    • ipAddress
    • firstName
    • lastName
  • Connect Email Hippo Assess through the AI Assistant by describing its email and IP parameters, then review and apply the proposal.
3.
Decisimo decision engine

Put these checks into a decision flow

Create rules for credit, fraud or collections, then run them on live decisions.

See pricing

Add Email Hippo Assess data source to your decision flow

  • Already have a decision flow step for data sources? Add the Email Hippo Assess call there. The decision engine calls all sources in that same step in parallel, which ensures the fastest execution time.
  • If your decision flow does not yet include a step for external data, add one. Connect it to your decision flow, then double-click it to open the definition window. In the definition, specify the attributes from your data object that you want to send to Email Hippo Assess.
  • Email Hippo Assess within a decision step
GO

Run the decision making

  • Release your decision flow. Deploy it to an endpoint, then make decisions using data from Email Hippo Assess.
Check other data source guides

Frequently asked questions

How should I handle the Email Hippo API key before releasing the decision flow?

Treat the Email Hippo API key as a secret and enter it in the data-source configuration in place of the setup placeholder. Limit access to people who maintain the integration, and replace the key if it is exposed. Test the configured connection before releasing the decision flow.

Which sign-up fields should I send to Email Hippo Assess?

Send emailAddress for every Assess call. Add ipAddress when sign-up captures it and your fraud policy uses it, since it can help identify bot-driven registrations. Include firstName or lastName only when the expected value justifies sharing that personal data with Email Hippo. Sending more fields means sharing more personal data, not automatically making a better decision.

Where should I place Email Hippo Assess relative to other external data sources?

Place Email Hippo Assess alongside other independent data sources in the same external-data part of the decision flow, so Decisimo can call them in parallel. Keep a source separate if its inputs depend on an earlier result. Parallel calls reduce serial waiting, but the slowest response can still determine the overall wait.

What should I test before sending live sign-ups through Email Hippo Assess?

Test typical sign-ups, missing optional fields, and invalid or incomplete input. Check that the decision rules handle missing or unusable results explicitly rather than treating them as favorable. Also test how the decision flow behaves when Email Hippo is unavailable, then release only after the result handling matches your sign-up policy.

Decisimo decision engine

Put these checks into a decision flow

Create rules for credit, fraud or collections, then run them on live decisions.

See pricing

Related Articles

  • How to integrate WhatIsMyBrowser into a decision engine

    This guide shows how to integrate WhatIsMyBrowser's API into a Decisimo decision engine and add parsed User-Agent data to your decision logic. It covers how to get an API key and create a WhatIsMyBrowser data source in the Decisimo portal. Then, you call that source from a decision flow to flag bot-like User-Agent patterns and other malicious signals.

  • MaxMind minFraud Insights checks and risk scores

    minFraud Insights returns the checks behind its fraud score, including details about the IP, email, addresses, card, phone and device. In live calls, an anonymous cloud IP and a billing address thousands of kilometres from the IP both scored below MaxMind's example accept line while the checks flagged them.

  • Google Places API checks business presence for lender and merchant risk teams

    A Google Places result can show whether a business appears at its declared address, what kind of place it is and how much public review activity it has. Missing fields, service-area businesses and thin review counts can mislead a rule, so null cases belong before numeric comparisons.

  • How to integrate FraudlabsPro into a decision engine

    This guide shows how to connect FraudLabsPro to Decisimo and use it inside your decision logic for eCommerce transaction evaluation. It walks through setup, required API details, and the data fields that help you review, approve, or reject transactions with clearer traceability.

  • MaxMind minFraud Factors: reason codes, pricing, and use

    Factors returns the same score as Score and Insights when the three services are called at the same moment, plus reasons that show what raised or lowered it. The reasons are most useful when a score alone would leave an order inside your accept range.