FlowRunner
PricingContact
Theme
Start Free

Experian Aperture

Analytics & Data

Experian Aperture is Experian's data quality API for address, email and phone validation. Agents validate and format addresses interactively, verify emails and phone numbers in real time, and run bulk cleansing batches on whole lists.

Verified 15 actions API key available
Experian Aperture website Platform Documentation Capability data verified 2026-08-27
A list hygiene run is scheduled ahead of a major campaign send
The agent assembles the records and calls Create Batch, which stages them without processing anything
Start Batch begins processing, and Get Batch Status is polled until it reports the batch finished
Get Batch Results reads the certainty recorded against every record
The agent separates verified results from unknown ones instead of treating both as a pass
The unknown pile posts to the list owner with counts and sample records
The list owner decides what happens to the unknown addresses before anything is suppressed

What This Integration Enables

Experian Aperture is for teams where the contact detail is the deliverable. If your outcome is a parcel that arrives, an invoice that reaches accounts payable, or a campaign that lands in an inbox, the address, email and phone number on the record are not metadata, they are the product. This connector gives FlowRunner agents Experian's data quality surface in both modes: real time validation at the moment a record is captured, and bulk cleansing over a whole list.

The property that makes this connector worth building a flow around is that Experian answers with a graded verdict rather than a pass or fail. Validate Address returns a confidence, and only a verified match means a single deliverable address was found. Interaction required and multiple matches arrive with a perfectly successful response and mean Experian found candidates that still need resolving. Validate Email works the same way: an unknown certainty means the receiving mail server would not confirm either way, which is not the same as invalid. Treating the graded answer as a binary is how good customers get thrown away and how unverified addresses get stored as verified, and it is precisely the kind of automation exception that deserves a person rather than a default.

Without FlowRunner

A 200 read as a pass Any response that came back without an error gets stored as a good address
Hygiene as an annual project The list is cleansed when someone finally schedules it, and drifts in between
Bad addresses found by bouncing The way a broken contact detail gets discovered is that a send fails or a parcel comes back

With FlowRunner

The confidence is the answer Verified, interaction required and unknown are three different outcomes, and the flow treats them that way
Hygiene as a running process Records are validated at capture and re-validated in scheduled batches without anyone opening a portal
Bad addresses found before the send Validation happens ahead of the campaign or the shipment, not in the bounce report afterwards

Use Case Scenarios

  • Address capture that resolves itself as the customer types

    A checkout or an onboarding form calls Search Address as the customer types, and Experian returns suggestions rather than a single result. When a suggestion stands for many addresses, such as a building of flats, Step Into Suggestion opens it into the more detailed ones inside, and the flow repeats until a single address is reached. Refine Suggestion narrows a returned range when the customer needs to pick one building out of it. Format Address turns the chosen key into Experian's standard seven line global layout, and that is the value the agent writes to the customer record in Shopify and passes to ShipBob for fulfillment. Before the flow serves a new country, List Address Datasets confirms the account is licensed for it, because a country with no dataset is refused rather than returning no match, and the two are easy to confuse.

  • Deliverability work before the campaign, not after it

    Ahead of a send, the agent stages the target segment with Create Batch, which deliberately does not begin processing. Start Batch runs it, Get Batch Status is polled until the work is finished, and Get Batch Results returns the certainty for every address. Verified records flow into the send in Klaviyo. Anything short of verified is held out. List Batches gives the flow a view of what is running across the account, and Stop Batch halts a job that was pointed at the wrong segment, keeping whatever was already validated rather than discarding it.

  • A phone number that is actually reachable

    An inbound lead arrives with a phone number and a claimed country. Validate Phone reports whether the number is live and reachable, along with its line type and network, so a mobile-only campaign does not queue a landline and a voice follow-up does not get routed to a disconnected number. Validate Phone Legacy remains available where an existing integration depends on its response shape. The agent writes the line type onto the lead record in HubSpot, and routes numbers that fail to reach anything into a review queue in Slack rather than silently dropping the lead.

Human-in-Loop Highlight

Suppression is the one thing on this page that cannot be undone by trying again. When Validate Email or Get Batch Results returns an unknown certainty, the receiving mail server declined to confirm the mailbox either way. Suppressing on that verdict removes a customer from every future send, and there is no way to discover you were wrong, because the only test that would settle it is sending to the address, which suppression permanently prevents. Corporate mail servers that refuse verification requests as a matter of policy are exactly the accounts a business list is built on. So the agent runs the batch, sorts the results, and stops at the boundary: "The hygiene batch finished. Verified records are cleared for the send and invalid ones are queued for suppression. That leaves the unknown pile, where the mail server would not confirm either way, and a share of those sit on corporate domains we have delivered to inside the last quarter. Suppress the unknowns, hold them for a re-validation pass, or keep mailing them?" The list owner answers in Slack, and the agent applies that decision to every record in the pile. This is the digital andon cord pulled at the right moment. The agent is faster than any person at grading forty thousand addresses. Deciding which uncertain customers stop hearing from you is not a grading problem.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

15 actions

Address

6
  • Validate Address Validates a complete address the way it would appear on an envelope and returns a confidence alongside the formatted result. The confidence is the real answer, not the status. Only a verified confidence means a single deliverable address was matched, and interaction required means Experian found candidates that still need resolving.
  • Search Address Searches for an address as it is being typed, returning suggestions rather than a single result. This is the operation behind an autocomplete box, and the cheaper of the two searches when the address is incomplete.
  • Step Into Suggestion Opens a suggestion that stands for several addresses, such as a building with many flats, and returns the more detailed suggestions inside it. Repeat until a single address is reached.
  • Refine Suggestion Narrows a suggestion with extra information from the user, such as picking one building out of a returned range.
  • Format Address Turns a chosen address key into a fully formatted address in Experian's standard seven line global layout. This is the last step of an interactive search and the value worth storing.
  • List Address Datasets Lists the address datasets the account is licensed for, per country. Worth calling first, because a country the account holds no dataset for is refused rather than returning no match, and the two are easy to confuse.

Email

1
  • Validate Email Checks whether an email address exists and can receive mail, going beyond syntax to a mailbox level check. Read the returned certainty rather than the status. An unknown result means the mail server would not confirm either way, which is not the same as invalid.

Phone

2
  • Validate Phone Checks a phone number and returns whether it is live and reachable, along with its line type and network.
  • Validate Phone Legacy Checks a phone number through Experian's earlier validation route, which is still live and answers a different response shape. Kept for integrations that depend on it.

Bulk

6
  • Create Batch Submits a batch of addresses, emails or phone numbers to be validated together. Creating a batch does not start it, which is what makes it safe to assemble a large batch in stages.
  • Start Batch Begins processing a batch that has been created. Processing is asynchronous, so this answers immediately and the work happens afterwards.
  • Stop Batch Stops a batch that is being processed. Records already validated keep their results, so a stopped batch is partially complete rather than discarded.
  • Get Batch Status Reports how far a batch has got. This is the operation to poll after Start Batch, because results are not available until it reports the batch finished.
  • Get Batch Results Reads the validation results of a finished batch, with the certainty recorded against every record.
  • List Batches Lists the batches on the account for one validation service, with their current state.

Frequently Asked Questions

What can FlowRunner do with Experian Aperture?

FlowRunner agents can run Validate Address, Search Address, and Step Into Suggestion in Experian Aperture, plus 12 more actions.

Does connecting Experian Aperture to FlowRunner require OAuth?

No. Experian Aperture connects to FlowRunner with an API key, no OAuth flow required.

Can Experian Aperture trigger a FlowRunner workflow automatically?

Experian Aperture doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Experian Aperture

Free plan, no card required. Connect in minutes.