How to integrate Ekata Address Risk API into a decision engine

Ekata provides among other services also Address Risk API. The API is a great tool for verifying addresses in different scenarios. It can serve as an addition to traditional antifraud or credit risk evaluation.

In comparison to verification by Google Maps API, Ekata also offers more data. The data shows how and how much an address appears in eCommerce transactions. That includes the first time and last time it appeared, the number of merchants where it appeared, or how much it was used with other attributes.

You can read more about the Ekata Address Risk in one pager here.

1.

Get an account API key from Ekata

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.
  • Place the API Key you have from Ekata in the value of the parameter “api_key”.
    Ekata Address Risk form shows a GET JSON endpoint, api_key, street_line_1, city, postal_code and country_code
  • Ekata needs the main address fields for proper evaluation. The main address fields are:
    • street_line_1
    • city
    • postal_code
    • country_code
  • Tell the AI Assistant the provider and its HTTP call. Check the proposal against the parameters below.
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 Ekata Address Risk data source to your decision flow

  • If you already have a decision step for data sources, you can add the call to Ekata Address Riskwithin the same step. The decision engine will call all the sources in the same step in parallel. Parallel calls ensure the fastest execution time.
  • If you do not have a decision flow step for external data, add one. Connect your decision flow step and by double-clicking, open the definition window. Define in the step the attributes from your data object to be sent to Ekata Address Risk API.
  • Ekata Address Risk API within a decision step
GO

Run the decision making

  • Release your decision flow, deploy to an endpoint and make decisions using data from Ekata Address Risk API.
Check other data source guides

Frequently asked questions

What address information should I send to the Ekata Address Risk API?

Send the street address, city, postal code and country code. Check that these values come from the application data you intend to assess and decide how your rules handle missing or incomplete addresses before release. Incomplete or outdated address details can make the returned risk information less useful.

How should I configure the Ekata data source in Decisimo Portal?

Create a data source and ask the AI Assistant to propose the provider configuration and HTTP call. Review and approve the proposal before applying it, then enter the Ekata API key in the provider configuration and map the required address inputs. Check the request settings against Ekata’s current documentation before testing.

Should I add Ekata to an existing external data task or create a separate one?

Add Ekata to an existing external data task if the other sources are needed at the same point in the decision flow. Sources in the same task are called in parallel, so the total wait depends on the slowest response. Use a separate task when the address check belongs later in the decision flow or depends on an earlier result.

What should I test before releasing a decision flow that uses Ekata?

Test complete and incomplete addresses, confirm the returned data is available to the rules that need it, and define what happens if the call fails or returns no usable result. Check representative decisions before release. Pay particular attention to missing inputs and provider errors, since unclear handling can lead to inconsistent decisions.

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

  • 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.

  • 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.

  • How to use AbuseIPDB for fraud decisions

    AbuseIPDB’s confidence score shows how sure its community is that an address is malicious, while its usage type and Tor flag show what kind of address it is. Read these signals together when shaping fraud decisions for sign-ups, logins, and other flows.

  • Companies House API points card for business credit cutoffs

    Learn how to score a company from its Companies House profile and charges, interpret the register outcomes, and set cut-offs using your own lending results.