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
  • Phone Validation JSON Payload
  • Understanding Phone Data with Various Samples
  • Understanding Phone Validation Exceptions
  1. Harmony Suite
  2. User Guides
  3. Version 3.0.0
  4. Email and Phone Validation
  5. Guides

Understanding Phone Data

This section includes all the enriched information returned by Phone Validation PDP along with some potential exception messages.

Phone Validation JSON Payload

Below is the explanation for the response of Phone Validation.

countryCode

Any country code associated with the supplied phone number (e.g. '+61', '+64', '+44').

areaCode

Any area code associated with the supplied (non-mobile) phone number (e.g. '02').

localNumber

The local part of the supplied number (e.g. '12345678')

operatorName

The mobile operator associated with the supplied number (e.g. 'Vodafone Australia')

  • Phone numbers marked with a 'connected|Network confirmed connection' phoneStatus will display the actual provider name (e.g. 'Vodafone Australia') under the 'operatorName' field.

  • Phone numbers marked with a 'disconnected|Network confirmed disconnection' phoneStatus will display 'Unknown' under the 'operatorName' field.

  • Phone numbers with an 'indeterminate' status will not display any 'operatorName' in the JSON response.

phoneStatus

The current status of the mobile phone with the supplied number (e.g. 'connected|Network confirmed connection', 'disconnected|Network confirmed disconnection', 'indeterminate').

exception

An exception message outlining the errors that occurred during validation will be shown for phone numbers with following status.

  • Phone numbers with 'indeterminate' phone status. (e.g. 'Number prefix missing', 'Network is forbidden', 'Invalid destination address.').

JSON Representations for connected, disconnected and indeterminate phone status.

    //connected|Network confirmed connection
    
    {
    "ciqPartyDocument": {
        "pdpchangeContext": {},
        "options": {
            "exposeAttributes": "7"
        },
        "phone": {
            "countryCode": "61",
            "numberType": "61",
            "localNumber": "0412345678",
            "phoneQuality": 7,
            "extraAttributes": {
                "MediaType": "61",
                "phoneStatus": "connected|Network confirmed connection",
                "operatorName": "Vodafone Australia"
            }
        },
        "locationInParties": 0,
        "containedInParties": false
    }
}
    
    
//connected|Network confirmed connection validated as another country
{
    "ciqPartyDocument": {
        "pdpchangeContext": {},
        "options": {
            "exposeAttributes": "7"
        },
        "phone": {
            "countryCode": "44",
            "localNumber": "1234567878",
            "phoneQuality": 7,
            "extraAttributes": {
                "exception": "Validated as another country - GB",
                "phoneStatus": "connected|Network confirmed connection",
                "operatorName": "MNO - 3 (Hutchison 3G UK Ltd)"
            }
        },
        "locationInParties": 0,
        "containedInParties": false
    }
}
// disconnected|Network confirmed disconnection
{
    "ciqPartyDocument": {
        "pdpchangeContext": {},
        "options": {
            "exposeAttributes": "7"
        },
        "phone": {
            "numberType": "61",
            "localNumber": "0412222222",
            "phoneQuality": 5,
            "extraAttributes": {
                "MediaType": "61",
                "phoneStatus": "disconnected|Network confirmed disconnection",
                "operatorName": "Unknown"
            }
        },
        "locationInParties": 0,
        "containedInParties": false
    }
}
// indeterminate
{
    "ciqPartyDocument": {
        "pdpchangeContext": {},
        "options": {
            "exposeAttributes": "7"
        },
        "phone": {
            "localNumber": "441112223333",
            "phoneQuality": 5,
            "extraAttributes": {
                "exception": "Number prefix missing",
                "phoneStatus": "indeterminate"
            }
        },
        "locationInParties": 0,
        "containedInParties": false
    }
}

Understanding Phone Data with Various Samples

Harmony Batch Output.

Phone numbers with an Output_phoneStatus as 'connected' are validated.

Phone numbers with an Output_phoneStatus as 'disconnected' or 'indeterminate' cannot be validated.

  • Numbers not presented in international format '+##' (e.g., Records 4 and 7).

  • Landline numbers (Record 9).

  • Disconnected mobile numbers (Record 10).

  • Other invalid data (Record 8).

Understanding Phone Validation Exceptions

{
    "ciqPartyDocument": {
        "pdpchangeContext": {},
        "options": {
            "exposeAttributes": "7"
        },
        "containedInParties": false,
        "locationInParties": 0,
        "phone": {
            "localNumber": "+44 123 456 7865",
            "phoneQuality": 5
        }
    },
    "exceptions": [
        {
            "cause": {
                "cause": {
                    "code": "H143",
                    "category": "PDP",
                    "description": "HostedPhoneValidation - ROAD error: Missing API user or password for hosted phone validation",
                    "message": "H143 : HostedPhoneValidation - ROAD error: Missing API user or password for hosted phone validation",
                    "localizedMessage": "H143 : HostedPhoneValidation - ROAD error: Missing API user or password for hosted phone validation"
                },
                "code": "H143",
                "category": "PDP",
                "description": "HostedPhoneValidation - ROAD error: Missing API user or password for hosted phone validation",
                "message": "H143 : HostedPhoneValidation - ROAD error: Missing API user or password for hosted phone validation",
                "localizedMessage": "H143 : HostedPhoneValidation - ROAD error: Missing API user or password for hosted phone validation"
            },
            "code": "H143",
            "category": "PDP",
            "description": "HostedPhoneValidation - ROAD error: Missing API user or password for hosted phone validation",
            "inputData": "+44 123 456 7865",
            "inputType": "PHONE_DATA",
            "message": "H143 : HostedPhoneValidation - ROAD error: Missing API user or password for hosted phone validation",
            "localizedMessage": "H143 : HostedPhoneValidation - ROAD error: Missing API user or password for hosted phone validation"
        }
    ]
}

{
    "exceptions": [
        {
            "code": "H112",
            "category": "PARSER",
            "description": "No pattern matched for this input - +44 123 456 7865. Check for punctuation errors, duplicate fields, incorrect input format and incorrect input data.",
            "inputData": "+44 123 456 7865",
            "inputType": "PHONE_DATA",
            "message": "H112 : No pattern matched for this input - 44 744 618 4828. Check for punctuation errors, duplicate fields, incorrect input format and incorrect input data.",
            "localizedMessage": "H112 : No pattern matched for this input - 44 744 618 4828. Check for punctuation errors, duplicate fields, incorrect input format and incorrect input data."
        }
    ]
}

PreviousGuidesNextUnderstanding Email Data

Last updated 1 year ago

Phone numbers with the 'connected|Network confirmed connection' status are validated in the default countries 'AU' or 'NZ' but may be validated as another country (e.g., 'Validated as another country - IN'). For further insight into the importance of the default country, please refer the '' section.

Here is a sample input file that comprises of global numbers across different countries AU, IN, NZ and GB, this file has been processed with default locale as "AUSTRALIA". Please refer for locale setup.

Exception generated when Api credentials for phone are not set as detailed in

Exception generated when global phone validation is not enabled as detailed in

Default Country for Phone Validation
Phone and Email Access Configuration File.
Activating Global Phone Validation
Alignment of Default Locale and 'hosted.defaultCountry for Phone Validation Users