Skip to main content

Experian API Destination

The Experian API connector enables you to send data to Experian API endpoints as part of your Nexla data flows — for example, submitting batch inquiry requests, uploading records for verification, or pushing data to Experian services. Follow the instructions below to create a new data flow that delivers data to an Experian API destination in Nexla.
experian_api.png

Experian API

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Experian API connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Experian API instance, and click Next; or, create a new Experian API credential for use in this flow.

  3. Configure the destination settings as described in the sections below.

Data Format​

  1. Select the format in which data will be sent to the Experian API endpoint from the Data Format pulldown menu. Experian API endpoints typically accept data in JSON format. Select the format that matches the content type expected by your target endpoint.

Most Experian API endpoints that accept data in the request body expect the Content-Type header to be set to application/json. Nexla sets the Content-Type header automatically based on the selected data format. If the target endpoint requires a different content type, you can override it in the Request Headers field.

API Method​

  1. Select the API method that will be used for calls to the Experian API from the Method pulldown menu. The most common methods for sending data to Experian API endpoints are:
    • POST: For submitting new records, inquiry requests, or data to Experian API endpoints that create new resources or trigger processing
    • PUT: For updating or replacing existing records on Experian API endpoints that support full record updates
    • PATCH: For partial updates to existing records on Experian API endpoints that support incremental updates

API Endpoint URL​

  1. Enter the URL of the Experian API endpoint to which this destination will send data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters.

    Common Experian API base URLs include:

    • Production (US): https://us-api.experian.com
    • Sandbox (US): https://sandbox-us-api.experian.com

    Append the specific API path for your target endpoint (for example, https://us-api.experian.com/businessinformation/businesses/v1/...). Refer to the Experian Global Developer Portal for the complete endpoint reference for each Experian product.

Always test destination configurations using the Experian sandbox environment (https://sandbox-us-api.experian.com) before switching to the production endpoint (https://us-api.experian.com). This avoids unintended writes to your live Experian data.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers may be required for Experian API versioning or other custom requirements.

    You do not need to include the Authorization header in the Request Headers field. Nexla automatically includes the OAuth 2.0 bearer token from your Experian credential in the Authorization header for all API calls.

Exclude Attributes​

Optional
  • If any data fields should be excluded from the records sent to this Experian API destination, enter the field names as a comma-separated list in the Exclude Attributes field. This is useful when your source data contains fields that are not expected by or relevant to the Experian API endpoint.

Record Batching​

Optional

  • If the Experian API endpoint supports batch submissions (sending multiple records in a single API request), you can configure record batching to group multiple records into each API call. This reduces the number of API requests made and can improve throughput.

    Select the appropriate batching algorithm from the Batching Algorithm pulldown menu. If the Experian API endpoint expects individual record submissions (one record per request), leave this setting at its default single-record mode.

Check the Experian API documentation for your specific product to determine whether batch submissions are supported and what the maximum batch size is. Refer to the Experian Global Developer Portal for product-specific limits and requirements.

Response Webhook​

Optional
  • If you need Nexla to track and process the responses returned by the Experian API after data is submitted, configure the Response Webhook settings. This is particularly useful for Experian API endpoints that return asynchronous results, status updates, or processed data in response to submitted records.

Save & Activate the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Experian API destination. Nexla will now begin delivering data to the configured Experian API endpoint according to the configured flow schedule.