Global Address Verification:Request - Revision history

Admin at 00:34, 11 June 2022

2022-06-11T00:34:44Z

@@ Line 244: / Line 244: @@
 |-
 |<code>OFF</code>||'''''Default.''''' No extra result codes will be returned.
 |}

2020-09-18T15:52:26Z

@@ Line 29: / Line 29: @@
 |Format||format||Format
 |-
-|Record ID||rowspan="18" valign="center"|Record|| ||RecordID
+|Record ID||rowspan="19" valign="center"|Record|| ||RecordID
 |-
 |Organization||org||Organization
 |-
 |Address Line 1||a1||AddressLine1
@@ Line 204: / Line 206: @@
 :*US Territories will have "United States of America" appended if the CountryOfOrigin is not a US Territory, but the CountryName and ISO codes will be that of the territory.
 :*Canada is treated like any other non-US Territory.
 |}
@@ Line 265: / Line 305: @@
 |-
 |SOAP/XML||<code><Organization>'''''string'''''</Organization></code>
 |}

2019-01-09T21:39:31Z

← Older revision		Revision as of 21:39, 9 January 2019
Line 178:		Line 178:

	:<h4 style="border-bottom:1px solid black;">OutputGeo</h4>		:<h4 style="border-bottom:1px solid black;">OutputGeo</h4>
	::~~Allow~~ you to specify if you want geocoding output in the response		::Allows you to specify if you want geocoding output in the response.

	::{\| class="alternate01 sortable"		::{\| class="alternate01 sortable"

2018-12-07T17:59:45Z

← Older revision		Revision as of 17:59, 7 December 2018
Line 9:		Line 9:

	Global Address Verification supports JSON, JSONP, REST, SOAP, and XML protocols.		Global Address Verification supports JSON, JSONP, REST, SOAP, and XML protocols.


			==URL==
			{{URL-GlobalAddressVerification}}

2017-08-31T22:15:25Z

Request Elements

← Older revision		Revision as of 22:15, 31 August 2017
Line 170:		Line 170:
	\|-		\|-
	\|<code>NATIVE</code>\|\|Returns in the native script for the designated country.		\|<code>NATIVE</code>\|\|Returns in the native script for the designated country.
			\|}


			:<h4 style="border-bottom:1px solid black;">OutputGeo</h4>
			::Allow you to specify if you want geocoding output in the response

			::{\| class="alternate01 sortable"
			!Option Name !! Parameter !! Description
			\|-
			\|rowspan="3"\|'''OutputGeo'''\|\|<code>ON</code>\|\|'''''Default.''''' Latitude and longitude is returned in the output when available
			\|-
			\|<code>OFF</code>\|\|Do not return latitude and longitude for the record.
	\|}		\|}

Line 205:		Line 217:
	\|SOAP/XML (HTTP Header)\|\|<code>Accept: application/xml</code>		\|SOAP/XML (HTTP Header)\|\|<code>Accept: application/xml</code>
	\|}		\|}


	==Request Record Elements==		==Request Record Elements==

2016-12-23T17:46:37Z

← Older revision		Revision as of 17:46, 23 December 2016
Line 6:		Line 6:
	{{CustomTOC}}		{{CustomTOC}}

	A request consists of a protocol to make a call to the service, detailing desired elements. The minimum required elements in a request are your Customer ID and at least one address record.		A request consists of a protocol to make 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 record.

	Global Address Verification supports JSON, JSONP, REST, SOAP, and XML protocols.		Global Address Verification supports JSON, JSONP, REST, SOAP, and XML protocols.
Line 85:		Line 85:
	:''Required.''		:''Required.''

	:This is a string value containing the ~~identification number~~ issued to the customer by Melissa Data for Global Address Verification.		:This is a string value containing the License Key issued to the customer by Melissa Data for Global Address Verification.

	:If this element is absent, the Web Service will return an error. To receive a ~~customer ID~~, please contact your Melissa Data sales representative at 1-800-MELISSA.		:If this element is absent, the Web Service will return an error. To receive a License Key, please contact your Melissa Data sales representative at 1-800-MELISSA.

	:{\| class="alternate01"		:{\| class="alternate01"

2016-10-14T22:38:29Z

← Older revision		Revision as of 22:38, 14 October 2016
Line 203:		Line 203:
	\|JSON (HTTP Header)\|\|<code>Accept: application/json</code>		\|JSON (HTTP Header)\|\|<code>Accept: application/json</code>
	\|-		\|-
	\|XML (HTTP Header)\|\|<code>Accept: application/xml</code>		\|SOAP/XML (HTTP Header)\|\|<code>Accept: application/xml</code>
	\|}		\|}

2016-10-14T22:32:42Z

← Older revision		Revision as of 22:32, 14 October 2016
Line 23:		Line 23:
	\|Options\|\|opt\|\|Options		\|Options\|\|opt\|\|Options
	\|-		\|-
	\|Format~~\|\|Request~~\|\|format\|\|Format		\|Format\|\|format\|\|Format
	\|-		\|-
	\|Record ID\|\|rowspan="18" valign="center"\|Record\|\| \|\|RecordID		\|Record ID\|\|rowspan="18" valign="center"\|Record\|\| \|\|RecordID

2016-10-14T22:31:53Z

@@ Line 17: / Line 17: @@
 !Field Name !! Level !! REST !! JSON/XML
 |-
-|Transmission Reference||rowspan="3" valign="center"|Request||t||TransmissionReference
+|Transmission Reference||rowspan="4" valign="center"|Request||t||TransmissionReference
 |-
 |Customer ID||id||CustomerID
 |-
 |Options||opt||Options
 |-
 |Record ID||rowspan="18" valign="center"|Record|| ||RecordID
@@ Line 58: / Line 60: @@
 |-
 |Country||ctry||Country
 |}
@@ Line 188: / Line 188: @@
 :*US Territories will have "United States of America" appended if the CountryOfOrigin is not a US Territory, but the CountryName and ISO codes will be that of the territory.
 :*Canada is treated like any other non-US Territory.
 |}
@@ Line 507: / Line 523: @@
 |-
 |SOAP/XML||<code><Country>'''''string'''''</Country></code>
 |}

2016-10-07T21:35:16Z

← Older revision		Revision as of 21:35, 7 October 2016
Line 16:		Line 16:
	{\| class="alternate01 sortable"		{\| class="alternate01 sortable"
	!Field Name !! Level !! REST !! JSON/XML		!Field Name !! Level !! REST !! JSON/XML
	\|- ~~style="vertical-align:top;"~~		\|-
	\|Transmission Reference\|\|rowspan="3" valign="center"\|Request\|\|t\|\|TransmissionReference		\|Transmission Reference\|\|rowspan="3" valign="center"\|Request\|\|t\|\|TransmissionReference
	\|-		\|-