• Overview
• Pre-built connectors
• HTTP connectors
• Data source features

Overview

Data sources let you call third-party APIs. Sperta provides pre-built connectors such as ComplyAdvantage and CRS, as well as HTTP connectors for any JSON APIs.

Connectors can be shared by all workflows under the same environment. Before you delete a connector, please make sure no workflows are using it.

Data source steps use the connection provided by connectors and configure the rest of the request parameters.

There is a timeout of 5 seconds for data sources.

Pre-built connectors

To add a pre-built connector, just add the connector name and credentials.

To create the data source step, you need to create an entity feature as an input feature first. Take a look at Entity features to learn more. For some products, you can also configure some options, such as Inquiry type and Scoring model in the following example:

Make sure to roll out the data source step. Then, you can use the features of the data source in subsequent stages. Use the sources namespace to access the features, e.g., sources.equifax_soft_pull_vantage.credit_score. Please refer to Data Source Features to find out which features are available.

HTTP connectors

HTTP connectors let you connect to any data vendors or internal services that have a JSON API.

The response of JSON APIs needs to be a JSON object instead of a JSON array.

To add a HTTP connector, specify the name, base URL, authentication method, and headers. You can securely store API keys and passwords in the headers since they’re encrypted when stored. You can also configure TLS settings if you’re connecting to an API that requires mTLS.

When creating the data source, you can add the method, path, and request body. The path is an expression that evaluates to a String, and it can include query parameters too. The body is an expression that evaluates to a Map. Just like other expressions, you can use any available features in the path and body.

Sperta doesn’t know the response schema of HTTP data sources. As a result, you need to parse the response in order to use its fields as features in subsequent stages:

• response.body contains the HTTP response body as a JSON. In the previous example, you can access Socure’s email risk score like this: sources.socure_risk.response.body.emailRisk.score.
• response.status_code contains the HTTP response status code as an Integer. For example, sources.socure_risk.response.status_code.

Sperta doesn’t add the response from HTTP data sources to the workflow execution results, but you can build formulas that parse the response to get the features you care about.

Data source features