Troubleshoot

Unfortunately postcode recodes are not supported at this time.

Unfortunately counties are not supported at this time.

Global Intuitive does not use the older layouts functionality. All addresses are returned in both a 7 line global format as well as each individual address component. The 7 line layout is designed to be displayed to the user upon selection of an address, whilst the individual address components are for storing in relevant database fields.

Results are ordered alphabetically by locality first.

Follow these steps to diagnose and solve your issue:

  • Firstly check that you are not having network or firewall connectivity issues by entering the URL in to an up to date browser. Make sure that the URL is correctly formatted. If the URL does not work then you should check your configuration so that you have access to https://api.edq.com/capture.

  • If you have ruled out connectivity issues then you may be experiencing issues with TLS compatibility. TLS 1.2 and SHA-256 support is required of the client by https://api.edq.com. If your client does not know about, use or support these then you will see problems. In .NET you will get the following exception WebExceptions - Underlying connection closed. This is a result of .NET 4.5 and below defaulting to use TLS 1.1.To solve this problem in .NET, either recompile in .NET 4.6 or above (which defaults to TLS 1.2) or add the following line to your program:
    ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12

In order to use our services, you need to ensure that certain IP addresses and address ranges (listed below) are accessible to you (i.e. not blocked by your firewalls).

  • 167.107.82.39
  • 45.60.31.210
  • 45.60.32.212
  • 45.60.33.210
  • 45.60.34.212
  • 45.60.35.210
  • 45.60.36.212
  • 45.60.37.210
  • 45.60.38.212
  • 45.60.39.210
  • 45.60.40.212
  • 107.154.0.0/16
  • 45.60.0.0/16
  • 45.223.0.0/16

Azure connectivity issues

If you're connecting to our APIs from Azure, you may experience intermittent timeouts or a lack of response from the Experian endpoints.

Unfortunately, this is a known issue with Microsoft Azure. Please contact us if you experience this.