Search results

Page title matches

• Global Name Web Service:Response Elements
  #REDIRECT [[Global Name:Response Elements]]
  43 bytes (5 words) - 00:31, 10 March 2015
• Global Name Web Service:Response Record Elements
  #REDIRECT [[Global Name:Response Record Elements]]
  50 bytes (6 words) - 00:32, 10 March 2015
• Global Phone Web Service:Response Elements
  #REDIRECT [[Global Phone:Response Elements]]
  44 bytes (5 words) - 19:30, 10 March 2015
• Global Phone Web Service:Response Record Elements
  #REDIRECT [[Global Phone:Response Record Elements]]
  51 bytes (6 words) - 19:32, 10 March 2015

Page text matches

• Global Name Web Service:Response Elements
  #REDIRECT [[Global Name:Response Elements]]
  43 bytes (5 words) - 00:31, 10 March 2015
• Global Name Web Service:Response Record Elements
  #REDIRECT [[Global Name:Response Record Elements]]
  50 bytes (6 words) - 00:32, 10 March 2015
• Global Phone Web Service:Response Elements
  #REDIRECT [[Global Phone:Response Elements]]
  44 bytes (5 words) - 19:30, 10 March 2015
• Global Phone Web Service:Response Record Elements
  #REDIRECT [[Global Phone:Response Record Elements]]
  51 bytes (6 words) - 19:32, 10 March 2015
• Global Email V3:Response
  ...ult of a request. This consists of returned results codes and parsed email elements. ...ocol used to make the request, the response will be in a certain protocol. Global Email supports the JSON, JSONP, SOAP, and XML protocols.
  6 KB (833 words) - 17:13, 23 May 2019
• Global Name:Response
  ==Response== ...sult of a request. This consists of returned results codes and parsed name elements.
  13 KB (1,836 words) - 18:21, 29 February 2024
• Global Email:Response
  ...ult of a request. This consists of returned results codes and parsed email elements. ...ocol used to make the request, the response will be in a certain protocol. Global Email supports the JSON, JSONP, and XML protocols.
  13 KB (1,650 words) - 00:08, 9 September 2022
• Global Email V3:Request
  ...ke a call to the service, detailing desired elements. The minimum required elements in a request are your Customer ID (License Key) and at least one input emai Global Email supports JSON, JSONP, REST, SOAP, and XML protocols.
  5 KB (725 words) - 21:36, 18 March 2020
• Global Phone V3:Response
  ...result of a request. This consists of returned results codes, parsed phone elements, and appended geographic information. ...esponse will be in a certain protocol. Global Phone supports four possible response protocols: SOAP, JSON, XML, and REST.
  14 KB (1,865 words) - 22:47, 2 May 2016
• Personator Identity:FAQ
  Throughput and response times for Personator Identity can vary due to many factors. Each action tha ...on relies on Melissa’s Global services to validate individual contact data elements.
  2 KB (232 words) - 00:35, 22 April 2022
• Global Phone:Response
  ...result of a request. This consists of returned results codes, parsed phone elements, and appended geographic information. ...ocol used to make the request, the response will be in a certain protocol. Global Phone supports JSON and REST protocols.
  15 KB (2,011 words) - 00:43, 6 March 2018
• Global Email:Request
  ...ke a call to the service, detailing desired elements. The minimum required elements in a request are your Customer ID (License Key) and at least one input emai Global Email supports JSON, JSONP, REST, and XML protocols.
  6 KB (828 words) - 19:44, 28 April 2023
• Global Phone:Transition
  [[Global Phone|← Global Phone V4]] Melissa data has recently announced the depreciation of Global Phone V3 service with the transition to our V4 service. The new version has
  7 KB (1,040 words) - 22:28, 19 December 2016
• Global Phone:FAQ
  [[Global Phone|← Global Phone]] ==How accurate is Global Phone at identifying disconnected and invalid numbers?==
  6 KB (998 words) - 17:09, 10 November 2023
• Express Entry:Global Getting Started
  ==Using Express Entry Global== ...er, these form the REST request sent to the server, which then returns the response in your choice of XML or JSON.
  5 KB (693 words) - 20:26, 29 July 2019
• Global Email:V3 Deprecation
  [[Global Email|← Global Email]] Melissa Data has recently announced the deprecation of Global Email V3 service with the transition to our V4 service. The new version has
  9 KB (1,240 words) - 20:20, 16 September 2022
• IP Locator:Transition
  *More comprehensive set of global IP4 Addresses (covers 99.999 % of the internet) *ISP Name
  8 KB (1,111 words) - 19:25, 16 December 2016
• Global Email V3:Notice
  [[Global Email V3|← Global Email V3]] The new system of Global Email (Version 3.0.0.50) can now be consumed using the following endpoint:
  10 KB (1,398 words) - 17:22, 23 May 2019
• Global Name:Request
  ...est are your Customer ID (License Key) and at least a full name or company name. Global Name supports JSON, JSONP, REST, SOAP, and XML protocols.
  18 KB (2,534 words) - 01:16, 21 January 2023
• Global Address Verification:Request
  ...ke a call to the service, detailing desired elements. The minimum required elements in a request are your Customer ID (License Key) and at least one address re Global Address Verification supports JSON, JSONP, REST, SOAP, and XML protocols.
  21 KB (2,768 words) - 00:34, 11 June 2022

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)