How to integrate WhatIsMyBrowser into a decision engine

WhatIsMyBrowser.com is a service that parses browser string information from User-Agent headers. The parsed output shows details about the browser, the platform, and other technical attributes.

Browser data is useful for detecting bot traffic and other malicious traffic. Real users tend to update their browsers and use standard releases. Bot traffic often sticks to a specific string or rotates through a fixed set of browsers. Over time, that rotation becomes outdated, which WhatIsMyBrowser indicates in its response data.

1.

Sign up for a WhatIsMyBrowser account and get API key

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 __YOUR_API_KEY__ in the Headers section with your WhatIsMyBrowser API key. This is the highlighted text in the screenshot below.
    WhatIsMyBrowser data source form with the user_agent parameter and highlighted __YOUR_API_KEY__ header value
  • Tell the AI Assistant that WhatIsMyBrowser's API needs only user_agent. Review its proposed connection in Data sources and apply it. JSON and XML responses are available to the decision flow.
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 WhatIsMyBrowser data source to your decision flow

  • If you already have a decision step for data sources, add the WhatIsMyBrowser call in that same step. The decision engine calls all sources in the same step in parallel. That gives you the fastest execution time.
  • If you do not have a decision flow step for external data, add one. Connect the step in your decision flow and open the definition window by double-clicking.
  • In the decision flow step, define the attribute from your data object that contains the User-Agent string to send to WhatIsMyBrowser.
  • WhatIsMyBrowser within a decision step
GO

Run the decision making

  • Release your decision flow, deploy it to an endpoint, and make decisions using data from WhatIsMyBrowser.
Check other data source guides
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 Email Hippo Assess into a decision engine

    How to 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.

  • Why Case Management Matters in Anti-Fraud Work

    Fraud teams need more than detection. They need decision logic, case tracking, and a clear path from alert to resolution. This article explains why case management matters in anti-fraud work, which functions it should support, and how automation removes repetitive tasks and preserves control over the investigation.

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

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