Loqate Harmony Documentation
  • GBG Loqate AU & NZ
  • Loqate Harmony API
    • Sign up for free trial
    • Login
    • API Specification
      • Authentication
      • Address
        • Address Validation & Lookup
        • Address by Geocode
        • Address Cleanse
        • Address Parse
        • Geocode Intl
      • Address Insights
        • Australian Insights
          • SEIFA Australia
          • ASGS Australia Statistical Geography Standard
          • Residential / Commercial
          • Deliverable address
      • Suburb Lookup
      • Business Validation and Lookup
      • Email Validation
      • Phone Validation
      • Matching
      • Moved Suppression
      • Deceased Suppression
      • Objects
        • Address Objects
        • Address Type Objects
        • Suburb Objects
        • Parse Objects
        • Email Objects
        • Phone Objects
        • Property Title Objects
        • Match Objects
        • Business Objects
      • Deprecated API services
        • Email Validation v1.1
        • Address v1
        • Address Cleanse v1
        • Address International
        • Address Combined
        • Address Types
    • Guides
      • Best Practices
        • Address Field Mappings
        • Finding an Address
      • User Derived Address
      • Expanded sub-premise reach
      • Parcel Locker Plus
      • Migrating to Address V2
      • Sign up/ Login
      • Support
      • Console
        • Getting your API keys
        • Getting Started
        • Add a Service
        • Dashboard
        • Subscriptions
          • Features
          • Users
          • Subscribed Plans
          • Allowlisting domains
          • Blocklist - Email Validation
        • Reports
        • Invoices
          • Paying Invoices
      • API Latency
    • Demos
      • How to use our demos
      • Address Validation Demo
      • Address by Geocode (Reverse Geocode) Demo
      • Address Cleanse Demo
      • Address Parse Demo
      • Business Validation Demo
      • Email Validation Demo
      • Phone Validation demo
    • Integrations
      • Client Libraries
        • Javascript Library v2.1.0
      • Adobe Commerce (Magento 2) Plugin
        • Magento2 User Guide
      • Woocommerce Plugin
        • Woocommerce Install Guide v2.0.0
        • Woocommerce Settings guide v2.0.0
      • Shopify Plus App
      • Gravity Forms
      • Voxco Survey Software
      • Salesforce CRM
      • Dynamics 365 CRM
      • Batch App - Lightweight
      • Deprecated Integrations
        • Harmony RightAddress c# example
        • Harmony RightAddress cURL example
        • Deprecated JS Library v2.0.1
        • Deprecated JQuery Library v1.8.1
    • Coverage
    • Address Exchange (Beta)
      • ADX Console
        • Searching Addresses in console
        • Create Address in console
        • Create Actions in console
      • ADX API Specification
        • Create Address
        • Get Address
        • Create Address Event
        • Edit Address Event
        • Create/Edit Address Attributes
        • Create/Edit Address Geopoint
        • Get Source Events
      • Reserved Attributes
    • GBG Status
  • Batch / Bulk Data Services
    • Serviced Batch
      • Bulk Address Cleanse
      • Email Serviced Batch
      • Phone Serviced Batch
      • Business Serviced Batch
  • Harmony Suite
    • Harmony Suite Overview
    • Release Notes
      • Version 3.0.0
        • New Features
        • Enhancements
        • Bug Fixes
        • Supported Platforms
    • User Guides
      • Version 3.0.0
        • Welcome to Harmony Suite
        • Glossary of terms
        • Upgrades
          • HSQL Upgrade
        • Email and Phone Validation
          • Prerequisites
          • Phone and Email PDP Configuration Setup
          • Phone Validation using Harmony Batch System
          • Phone Validation using Harmony WS
          • Email Validation using Harmony Batch
          • Email Validation using Harmony WS
          • Guides
            • Understanding Phone Data
            • Understanding Email Data
        • Business Lookup and Validation
          • Prerequisites
          • Business Lookup
          • Business Validation
            • Business Validation using Commercial Name Parser
            • Business Validation Configurations
            • Business Validation using Harmony Batch System
            • Business Validation using Harmony WS
          • Business data update guide
          • Guides
            • Understanding Business Data
            • Understanding Business Verification Code
            • Name Parse Ambiguity
        • Australia Post Parcel Locker Plus Lookup and Validation
          • Prerequisites
          • Australia Post Parcel Locker Plus Lookup
          • Australia Post Parcel Locker Plus Validation
            • PDP Configuration Setup
            • AupostValidation using Harmony Batch System
            • AupostValidation using Harmony WS
          • Guides
            • Knowledgebase Lexical Update
            • Understanding Australia Post Parcel Locker Plus Data
            • Interchangeable terms for Australia Post Parcel Lockers
        • Installation and Upgrade Reference Guide
        • Locate Reference Guide
        • Extensions Reference Guide
        • RealTime Reference Guide
        • Postmaster Reference Guide
        • Rapid Address ANZ Reference Guide
        • Post ANZ Reference Guide
        • Source of Truth Installation Reference Guide
        • Knowledgebase Configuration Reference Guide
        • Web Services Reference Guide
        • Management Console Reference Guide
        • Batch System Match Reference Guide
        • Batch System Cleanse Reference Guide
  • More from GBG
    • GBG GreenID
    • GBG Identity
    • GBG Fraud & Compliance
Powered by GitBook
On this page
  • CustomerData
  • CustomerDataList
  • MatchRequest
  • MatchRestRequest
  • MatchEntityResult
  • MatchEntityResultList
  • MatchResult
  • MatchResultList
  • MatchResultRestResponse
  1. Loqate Harmony API
  2. API Specification
  3. Objects

Match Objects

PreviousProperty Title ObjectsNextBusiness Objects

Last updated 3 years ago

CustomerData information.

CustomerData container.

MatchRequest object.

Request wrapper for match lookup REST methods.

MatchEntityResult information.

MatchEntityResult container.

MatchResult information.

MatchResult container.

Response wrapper for match lookup REST methods.

CustomerData

The CustomerData object is used when sending data for the match lookup API methods.

id

Type: StringThe identifier for each data set.

addresses

Type: The address list in a data set. Only one address is allowed for one data set.

emailAddresses

Type: The email address list in a data set. Only one email address is allowed for one data set.

phones

JSON Representation

    {
        "id": "c1",
        "addresses": [ { "fullAddress": "level 2, 220 george street, sydney nsw 2000" } ],
        "emailAddresses": [ { "address": "test@mydomain.com" } ],    
        "phones": [ { "fullPhone": "12345678" } ]
    }

With address components:

    {
        "id": "r2",
        "addresses": [ {
            "floorLevelNumber": "2",
            "floorLevelType": "level",
            "streetName": "george",
            "streetNumber": "220",
            "streetType": "street",
            "locality":"sydney",
            "state":"nsw"
        } ], 
        "phones": [ { "fullPhone": "12345678" } ]                 
    }

CustomerDataList

JSON Representation

    {
        "id": "c1",
        "addresses": [ { "fullAddress": "level 2, 220 george street, sydney nsw 2000" } ],
        "emailAddresses": [ { "address": "test@mydomain.com" } ],    
        "phones": [ { "fullPhone": "12345678" } ]
    }

With address components:

    {
        "id": "r2",
        "addresses": [ {
            "floorLevelNumber": "2",
            "floorLevelType": "level",
            "streetName": "george",
            "streetNumber": "220",
            "streetType": "street",
            "locality":"sydney",
            "state":"nsw"
        } ], 
        "phones": [ { "fullPhone": "12345678" } ]                 
    }

MatchRequest

A MatchRequest object is used when sending data from the customer match API methods.

from

to

JSON Representation

    {
        "from": [
            {
                "addresses": [ { "fullAddress": "220 george street, sydney nsw 2000" } ],
                "id": "c1"
            }
        ],
        "to": [
            {
                "addresses": [ { "fullAddress": "220 george street, sydney nsw 2000" } ],
                "id": "r1"
            },
            {
                "addresses": [ { "fullAddress": "level 2, 220 george street, sydney nsw 2000" } ],
                "id": "r2"
            }
        ]
    }
    

MatchRestRequest

A MatchRestRequest object is used when invoking the match lookup REST service methods.

payload

featureOptions

JSON Representation

    {
        "payload": {
            "from": [
                {
                    "addresses": [ { "fullAddress": "220 george street, sydney nsw 2000" } ],			
                    "id": "c1"
                }
            ],
            "to": [
                {
                    "addresses": [ { "fullAddress": "220 george street, sydney nsw 2000" } ],			
                    "id": "r1"
                },
                {
                    "addresses": [ { "fullAddress": "level 2, 220 george street, sydney nsw 2000" } ],			
                    "id": "r2"
                }
            ]
        }
    }
    

MatchEntityResult

The MatchEntityResult object is used when receiving data for the match lookup API methods.

addressPairIdx

Type: List of IntegerThe indexes of the matched addresses.

emailAddressPairIdx

Type: List of IntegerThe indexes of the matched email addresses.

phonePairIdx

Type: List of IntegerThe indexes of the matched phones.

assignedMatchClass

Type: StringThe assigned match class.

confidenceLevel

Type: StringThe match confidence level.

description

Type: StringThe description of the match class.

matchCategory

Type: StringThe match category.

JSON Representation

    {
        "addressPairIdx": [ 0, 0 ],
        "emailAddressPairIdx": [],
        "phonePairIdx": [ 0, 0 ],
        "assignedMatchClass": "H1",
        "confidenceLevel": "10",
        "description": "Household Match Class H1",
        "matchCategory": "MATCH_CLASS"
    }

MatchEntityResultList

JSON Representation

    "entityResults": [ 
        {
            "addressPairIdx": [ 0, 0 ],
            "emailAddressPairIdx": [],
            "phonePairIdx": [ 0, 0 ],
            "assignedMatchClass": "H1",
            "confidenceLevel": "10",
            "description": "Household Match Class H1",
            "matchCategory": "MATCH_CLASS"
        }, 
        {
            . . . .
        }
    ]
    

MatchResult

The MatchResult object is used when receiving data for the match lookup API methods.

fromId

Type: StringThe identifier for Customer Record (CR) data set.

toId

Type: StringThe identifier for Reference Record (RR) data set.

entityResults

JSON Representation

    {
        "fromId": "c1",
        "toId": "r1",
        "entityResults": [ {
            "addressPairIdx": [ 0, 0 ],
            "emailAddressPairIdx": [],
            "phonePairIdx": [ 0, 0 ],
            "assignedMatchClass": "H1",
            "confidenceLevel": "10",
            "description": "Household Match Class H1",
            "matchCategory": "MATCH_CLASS"
        } ]
    }

MatchResultList

JSON Representation

    {
        "fromId": "c1",
        "toId": "r1",
        "entityResults": [ {
            "addressPairIdx": [ 0, 0 ],
            "emailAddressPairIdx": [],
            "phonePairIdx": [ 0, 0 ],
            "assignedMatchClass": "H1",
            "confidenceLevel": "10",
            "description": "Household Match Class H1",
            "matchCategory": "MATCH_CLASS"
        } ]
    },
    {
        "fromId": "c1",
        "toId": "r2",
        "entityResults": [ {
            "addressPairIdx": [ 0, 0 ],
            "emailAddressPairIdx": [],
            "phonePairIdx": [],
            "assignedMatchClass": "G2",
            "confidenceLevel": "8",
            "description": "Address Match Class G2",
            "matchCategory": "MATCH_CLASS"
        } ]
    }

MatchResultRestResponse

payload

status

Type: StringThe status of the request (i.e. 'SUCCESS' or 'ERROR').

messages

Type: String[]Any error messages generated during the REST service method invocation (e.g. '[ "Access is denied" ]')

JSON Representation

    {
        "status": "SUCCESS",
        "messages": [],
        "payload": [
            {
                "fromId": "c1",
                "toId": "r1",
                "entityResults": [ {
                    "addressPairIdx": [ 0, 0 ],
                    "emailAddressPairIdx": [],
                    "phonePairIdx": [ 0, 0 ],
                    "assignedMatchClass": "H1",
                    "confidenceLevel": "10",
                    "description": "Household Match Class H1",
                    "matchCategory": "MATCH_CLASS"
                } ]
            },
            {
                "fromId": "c1",
                "toId": "r2",
                "entityResults": [ {
                    "addressPairIdx": [ 0, 0 ],
                    "emailAddressPairIdx": [],
                    "phonePairIdx": [],
                    "assignedMatchClass": "G2",
                    "confidenceLevel": "8",
                    "description": "Address Match Class G2",
                    "matchCategory": "MATCH_CLASS"
                } ]
            }
        ]
    }
    

Type: The phone list in a data set. Only one phone is allowed for one data set.

An array or list of structures.

Type: The list of CustomerData structures representing the Customer Record (CR) data set. Only one data set is allowed for CR.

Type: The list of CustomerData structures representing the Reference Record (RR) data set. Multiple data sets are allowed for RR.

Type: The MatchRequest object being passed to the REST service method.

Type: An Object containing the values for the feature options available for Match Lookup. Currently is not implemented.

An array or list of structures. Currently will only return one in the list.

Type: The MatchEntityResult list for the corresponding fromId and toId.

An array or list of structures.

A object is returned from the match lookup REST service methods.

Type: The list of MatchResult structures being returned from the REST service method.

AddressList
EmailList
PhoneList
CustomerData
CustomerDataList
CustomerDataList
MatchRequest
FeatureOption
MatchEntityResult
MatchEntityResult
MatchEntityResultList
MatchResult
MatchResultRestResponse
MatchResultList
CustomerData
CustomerDataList
MatchRequest
MatchRestRequest
MatchEntityResult
MatchEntityResultList
MatchResult
MatchResultList
MatchResultRestResponse