Search results

Page title matches

• Global Phone:Request
  ...ry name will greatly increase the chances of recognizing and verifying the phone number in question. Global Phone supports REST and JSON protocols.
  7 KB (990 words) - 23:37, 26 February 2024
• Global Phone V3:Request
  ...ry name will greatly increase the chances of recognizing and verifying the phone number in question. Global Phone supports multiple protocols to access the service, including SOAP, JSON, RE
  5 KB (664 words) - 19:18, 7 December 2018
• Global Phone Web Service:Request
  #REDIRECT [[Global Phone:Request]]
  34 bytes (4 words) - 19:24, 10 March 2015
• Global Phone Web Service:Example Request
  #REDIRECT [[Global Phone:Example Request]]
  42 bytes (5 words) - 19:22, 10 March 2015
• Global Phone Web Service:Request Elements
  #REDIRECT [[Global Phone:Request Elements]]
  43 bytes (5 words) - 19:23, 10 March 2015
• Global Phone Web Service:Request Record Elements
  #REDIRECT [[Global Phone:Request Record Elements]]
  50 bytes (6 words) - 19:22, 10 March 2015

Page text matches

• Global Phone
  ...a you can perform premium real-time checks to distinguish live numbers and phone types. ...ree-demo.png|link=https://www.melissa.com/request-demo?product=wiki+global+phone+service]]
  3 KB (345 words) - 23:57, 4 May 2023
• Global Phone V3:Reference
  [[Global Phone V3|← Global Phone V3]] |Image=[[File:MediumTile_GlobalPhoneWS.png|link=Global Phone]]
  2 KB (265 words) - 20:35, 6 July 2016
• Global Phone:REST XML
  ==REST Request== ...no recordID element because a REST request can only submit one record per request:
  1 KB (118 words) - 18:02, 2 February 2016
• Global Phone V3:REST XML
  ==REST Request== ...no recordID element because a REST request can only submit one record per request:
  1 KB (120 words) - 22:43, 2 May 2016
• Global Phone Web Service:Request
  #REDIRECT [[Global Phone:Request]]
  34 bytes (4 words) - 19:24, 10 March 2015
• Global Phone Web Service:Example Request
  #REDIRECT [[Global Phone:Example Request]]
  42 bytes (5 words) - 19:22, 10 March 2015
• Global Phone Web Service:Request Elements
  #REDIRECT [[Global Phone:Request Elements]]
  43 bytes (5 words) - 19:23, 10 March 2015
• Global Phone Web Service:Request Record Elements
  #REDIRECT [[Global Phone:Request Record Elements]]
  50 bytes (6 words) - 19:22, 10 March 2015
• Global Phone:Licensing
  ...Key from your Melissa Data representative. Without the License Key, Global Phone will not function. ...ense Key, use the CustomerID property in your requests. See [[Global Phone:Request#Customer ID|Customer ID]] for more information.
  464 bytes (64 words) - 22:18, 19 December 2016
• Global Phone V3:Licensing
  ...Key from your Melissa Data representative. Without the License Key, Global Phone V3 will not function. ...e Key, use the CustomerID property in your requests. See [[Global Phone V3:Request Elements#Customer ID|Customer ID]] for more information.
  484 bytes (69 words) - 19:58, 15 March 2017
• Global Phone V3:REST JSON
  ==REST Request== ...no recordID element because a REST request can only submit one record per request:
  1 KB (113 words) - 22:43, 2 May 2016
• Global Phone:REST JSON
  ==REST Request== ...no recordID element because a REST request can only submit one record per request:
  1 KB (108 words) - 21:45, 29 March 2018
• Phone Verifier
  |Product1=[[Global Phone]] ...bers down to 7 and 10 digits, update area codes, and append data about the phone number.
  2 KB (234 words) - 00:01, 21 April 2022
• Global Phone:SOAP
  ==SOAP Request== [[Category:Global Phone]]
  2 KB (161 words) - 18:25, 2 February 2016
• Global Phone V3:SOAP
  ==SOAP Request== [[Category:Global Phone V3]]
  2 KB (163 words) - 22:45, 2 May 2016
• Global Phone V3:Request
  ...ry name will greatly increase the chances of recognizing and verifying the phone number in question. Global Phone supports multiple protocols to access the service, including SOAP, JSON, RE
  5 KB (664 words) - 19:18, 7 December 2018
• Global Phone V3:Batch XML
  ==XML Batch Request== <Request>
  3 KB (240 words) - 22:44, 2 May 2016
• Global Phone:Batch XML
  ==XML Batch Request== <Request>
  3 KB (238 words) - 18:07, 2 February 2016
• Global Phone:Request
  ...ry name will greatly increase the chances of recognizing and verifying the phone number in question. Global Phone supports REST and JSON protocols.
  7 KB (990 words) - 23:37, 26 February 2024
• Global Phone:Transition
  [[Global Phone|&larr; Global Phone V4]] ...service. The new version has new features and improvements to help improve phone accuracy, along with constant updates every month.
  7 KB (1,040 words) - 22:28, 19 December 2016
• Global Phone:Batch JSON
  ==JSON Batch Request== [[Category:Global Phone]]
  2 KB (142 words) - 21:46, 29 March 2018
• Talend:Data Quality Components
  ...and standardize addresses, parse out names and detect vulgarities, verify phone numbers, verify email domains, correct email syntax errors, and append cens <br>[[File:Request-free-demo.png|link=https://www.melissa.com/request-demo?product=wiki+talend]]
  1,016 bytes (128 words) - 23:29, 10 June 2021
• Unison by Melissa
  <br>[[File:Request-free-demo.png|link=https://www.melissa.com/request-demo?product=wiki+unison]] *[https://vimeo.com/375022028 Phone Cleansing Tutorial Video]
  2 KB (277 words) - 21:28, 18 March 2024
• Global Phone V3:Response
  ...s the result of a request. This consists of returned results codes, parsed phone elements, and appended geographic information. ...ed to make the request, the response 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
• Global Phone V3:Batch JSON
  ==JSON Batch Request== [[Category:Global Phone V3]]
  3 KB (206 words) - 22:44, 2 May 2016
• Global Phone:Response
  ...s the result of a request. This consists of returned results codes, parsed phone elements, and appended geographic information. ...ed 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
• Data Quality Components for Pentaho
  ...and standardize addresses, parse out names and detect vulgarities, verify phone numbers, verify email domains, correct email syntax errors, and append cens <br>[[File:Request-free-demo.png|link=https://www.melissa.com/request-demo?product=wiki+pentaho]]
  2 KB (251 words) - 22:18, 10 June 2021
• Global Phone:FAQ
  [[Global Phone|&larr; Global Phone]] ==How accurate is Global Phone at identifying disconnected and invalid numbers?==
  6 KB (998 words) - 17:09, 10 November 2023
• MatchUp Web Service:Introduction
  ...a Data Web Services in that it is batch-oriented. This means that a single request record is not returned with response data about that record independent of The MatchUp Web Service does not currently have Global Matching capability. In other words, only domestic US/CAN matchcodes are av
  7 KB (1,148 words) - 15:53, 21 May 2021
• Personator Identity
  ...rifies your client/contact data globally. Verify a person’s name, address, phone, email, date of birth and their national ID against trusted reference data <br>[[File:Request-free-demo.png|link=https://www.melissa.com/request-demo?product=wiki+personator+dentity+verification]]
  3 KB (349 words) - 23:06, 19 October 2023
• Global Phone:Build History
  [[Global Phone|&larr; Global Phone]] *https://releasenotes.melissa.com/cloud-api/global-phone/
  7 KB (1,083 words) - 01:04, 7 March 2023
• FAQ:SSIS:Known Issues
  ==SSIS 8.1: Global Verify Pass-Through Column Records== ...r if the dataset is greater than the threads multiplied by the records per request. As a work around we suggest to set the records per transmission to 10 via
  13 KB (1,972 words) - 22:54, 7 June 2023
• Personator Identity:Response
  A response is the result of a request. This consists of returned result codes. |Results ||rowspan="21" valign="center"| Phone || Results
  46 KB (6,225 words) - 23:38, 26 February 2024
• Cloud Service:Best Practices
  ...time process like a web form entry or a call center application, send in a request with one record. For batch processing scenario like a database, send reques // Perform Phone Lookup and store results to the Response
  11 KB (1,819 words) - 18:19, 18 November 2019
• Listware for Excel:FAQ
  ...process' for a range of cells, blocks of 100 records are sent via SOAP web request to our servers, where the data is processed according to the options you ha ...will also verify Canadian addresses. For all other countries, use Listware Global Check & Verify.
  18 KB (3,036 words) - 00:32, 25 February 2023
• Result Code Details
  *For a list of example input that returns a specified Melissa Data Result code, see [[Result Code ...=[[Image:ICON_API_GlobalAddressObject.png|84px|Global Address Object|link=#Global Address Object]]
  128 KB (19,482 words) - 23:27, 19 February 2024
• Result Codes
  |US Only. A physical plot exists but is not a deliverable addresses. One example might be a railroad track or river running alongside this street, as they w ...for the address to be verified is not met. A country input is required for global products. For US/CA, a postal code or city/state are required. Requirements
  90 KB (14,655 words) - 23:27, 19 February 2024