Verify Overview

The Verify endpoint checks a full address (submitted through a form or provided by an express checkout provider, etc.)  against our authoritative database to confirm its validity.   When issues are detected, the API provides options so the end user can review and correct their address before proceeding.  It ensures addresses are accurate and standardized, helping you improve user experience, reduce failed deliveries, and minimize support queries. The Verify API currently supports addresses in Ireland and the United Kingdom.

The Verify endpoint responds with one of four actions:

1. Accept
   In most cases addresses are automatically verified and corrected (for example, by filling in a missing postcode) without requiring user interaction. We return an address object that is formatted to match your form requirements (field lengths, required fields, etc.).

2. Suggest
   The matched address differs sufficiently from the entered address that the end user should be prompted to confirm it. You should present the end user with a dialog and ask them to choose either the suggested address or their original entered address.
   
   The example below shows a sample Suggest dialog where the matched address has a different city and postcode to the entered address.
   

   

3. Confirm
   There are two main reasons why an address should be confirmed:

   • No Match Found: The input looks like a complete address, but we could not find a match.

   • Problem with the Address: The input appears to be incomplete or missing required information (for example, a missing apartment number).

   In both scenarios, you should present the end user with a dialog that shows the address, highlights the problem, and displays our message explaining the issue. Provide options for the user to either edit the address or proceed with their original entry.

   

4. Reject
   You can set up rules to reject certain addresses, for example PO boxes or geographic restrictions like Isle of Man or Northern Ireland addresses. If we detect one of these addresses, we return a Reject action. You should present the end user with a dialog displaying our message that explains why the address is rejected, and prompt them to enter an alternative address.

   

You can access reports in the account center to view a breakdown of verification success, actions, amendments made to addresses, and the reasons why end users have been shown a dialog.

See the Verify Address documentation for full details.

You can sign up for a free trial and start immediately, with up to 150 address verifications included during the trial period.  This includes both Verify API calls and addresses you enter manually in the Account Center. 

For a quick, low‑effort way to see how Verify could improve your address quality, we also provide a separate Check endpoint. It is designed to be integrated into your existing checkout flow in a “fire and forget” manner (similar to web analytics). You pass it the same parameters as Verify, but it does not return any response data. Instead, it silently records results into your account reports. From there, you can review breakdowns of verification success, actions taken, amendments made, and reasons why dialogs would be shown to end users.

Unlike the trial limit of 150 verifications for Verify, the Check endpoint does not have any usage limit. If you are on a paid subscription, Check usage also does not count against your purchased lookup allowance.

See the Check Address documentation for full details.