Connect any HTTP API to your decision flow
You have a provider, a contract and a key, but connecting it usually means another engineering ticket. Decisimo lets you define that provider's HTTP API as a data source, then use its response and failure outcome in the decision flow.
Connect any provider through its HTTP API
Define the provider in the portal, read its response in the decision, and give a failed call a meaning your rules can use.
- Connect the provider you choose. Define the provider’s HTTP API in the portal with its address and authentication details; its data source reads JSON and XML responses.
- Use the response in your decision. The response is available to the decision by path, so rules can read any field, and the data-source guide explains what the provider API must support.
- Give failure a defined meaning. A failed call carries an error flag, plus its HTTP status and attempt count; rules decide what that outcome means for the application. See how to design for provider failure.
Worked examples for the providers you use
Each guide shows one provider connected through the same mechanism, so a provider not listed here follows the same approach.
Fraud and identity
- Integrating Fingerprint.com Device Fingerprinting with Decisimo
- How to integrate SEON Antifraud Check into a decision engine
- How to use Trestle IQ Decision Signals for better anti-fraud
- How to integrate Ekata Address Risk API into a decision engine
- How to integrate FraudlabsPro into a decision engine
- How to integrate Maxmind minFraud Insights into a decision engine
- How to integrate Maxmind minFraud Score into a decision engine
- How to integrate Maxmind minFraud Factors into a decision engine
IP and device
Company registry
Geography and address
Your trained model
Questions we get asked
Can you connect a provider that is not in the guides?
Yes. An unlisted provider is connected by configuring its own HTTP API as a data source in the portal. Add its address, parameters and authentication, then use the response in your decision flow. The provider guides show this approach with worked examples.
Who supplies the provider account and credentials?
You keep your contract and key with the provider. Decisimo does not supply the provider data. The portal supports OAuth2 with client credentials and API keys.
How does the provider response reach my decision?
The provider response is written into the decision, and rules can read its fields by path. Your own systems call the Decisimo execution endpoint; see real-time decisioning for that side of the connection.
What happens when a provider call fails?
The output carries an error flag, the HTTP status and the number of attempts. Rules decide what that failed call means for the application, so the outcome belongs in your decision flow.
Connect the provider you already use
Follow a provider guide or connect an unlisted source the same way: define its HTTP API in the portal and add the lookup to a decision flow.