Skip to main content
Loqate offers three main integration options:
  • Using Tag: Available for Address Capture, Email Verification and Phone Verification
  • Using APIs: Available for all Loqate products and services
  • Integrations by Platform: Available for Address Capture, Verify, Email Verification and Phone Verification via integrations with tools like Shopify, Adobe Commerce, and Microsoft Dynamics 365
Loqate Core SDKs are now in Early Access (Beta) — our new TypeScript and .NET SDKs are available to try today. They're stable, generated from our live API definitions, and form the first stage of our developer-tools refresh. We'd love your feedback as we continue to expand them.
See the SDK Overview for details.
The main focus of this article is on Tag and API integrations, although information about third-party integrations is also included, with a link to the specific documentation.
These options are not mutually exclusive, so you can use more than one in conjunction if you want. Regardless of which option(s) you choose, you can make changes in the Account Section for security, customisation and certain features.

​
Use cases

Here are a few examples of possible use cases, and which of the Tag or API integration option might be best for each:
Business TypeSpecificsRecommended option
Financial businessStrictly regulatedAPIs
Large ecommerce businessRequires considerable customisationAPIs
Very small businessUses simple web formsTag
Small businessUses cloud-based tools for creating formsTag or APIs

​
Tag Integrations

The simplest way of setting up Address Verification, Email Validation and Phone Validation is by using the Tag method, which uses automatically-generated code snippets that you can insert into your website to set these services up. This method is designed for simple webforms, allowing you to set up standard configurations via your Loqate account. Pros:
  • Speed: you can get started quickly and easily
  • Simplicity: there’s no need for technical know-how, as the functionality comes from the JavaScript solution and CSS
Cons:
  • Customisation: unlike API integrations, you don’t have as much control over how your integration works as it will always be based off the JavaScript and CSS
  • Security: adding JavaScript to your website, while an effective way of adding new functionality, does come with some security considerations, and as such may not be appropriate for all circumstances. See the API Security article for more information
Check out the Tag Setup Guide for simple instructions that walk you through how to get set up with Tag integrations. From an additional security perspective, consider using the Limits functionality to restrict your integration by IP address, service and/or URL. See the API Security article for more details.

​
API Integrations

All Loqate products can be integrated using the APIs, which are also available for Address Verification, Email Verification and Phone Verification for more flexible integrations. Pros:
  • Control: you’re not constrained by any existing integrations or ways of working, and you don’t need to rely on the preset JavaScript or CSS
  • Customisation: you can shape your customer journey however you see fit
Cons:
  • Complexity: API integrations require technical knowledge and resources
  • Speed: it takes time to implement and test API integrations
Check out the API documentation for details of all of the Loqate APIs. You can still take advantage of all of the security functionality available in the Account Section - see the API Security article for more details.

​
Integrations by Platform

As well as the option of creating your own integration using the Tag and/or API methods, there’s also a range of integrations which allow you to access Address Capture, Verify, Email Validation and Phone Validation within various tools. Current integrations include: If you already use any of these tools, you can use the integrations to quickly and easily add Loqate functionality to your site. Check out the Integrations documentation for details of how to get up and running.