Difference between revisions of "Reverse GeoCoder:REST JSON"
Jump to navigation
Jump to search
Line 6: | Line 6: | ||
{{CustomTOC}} | {{CustomTOC}} | ||
==REST Request== | ==doLookup== | ||
===REST Request=== | |||
There is no recordID element because a REST request can only submit one record per request: | There is no recordID element because a REST request can only submit one record per request: | ||
Line 21: | Line 22: | ||
</pre> | </pre> | ||
===JSON Response=== | |||
==JSON Response== | |||
<pre> | <pre> | ||
{ | { | ||
Line 43: | Line 43: | ||
"MelissaAddressKey":"string", | "MelissaAddressKey":"string", | ||
"MelissaAddressKeyBase":"string" | "MelissaAddressKeyBase":"string" | ||
}] | |||
} | |||
</pre> | |||
==doLookupPostalCodes== | |||
===REST Request=== | |||
There is no recordID element because a REST request can only submit one record per request: | |||
<pre> | |||
http://ReverseGeo.melissadata.net/V3/WEB/ReverseGeoCode/doLookupPostalCodes | |||
?id={CustomerId} | |||
&lat={Latitude} | |||
&long={Longitude} | |||
&dist={MaxDistance} | |||
&recs={MaxRecords} | |||
&t={TransmissionReference} | |||
&opt={Options} | |||
&format=json | |||
</pre> | |||
===JSON Response=== | |||
<pre> | |||
{ | |||
"Version":"string", | |||
"TransmissionReference":"string", | |||
"TransmissionResults":"string", | |||
"Results":"string", | |||
"TotalRecords":"string", | |||
"Records":[{ | |||
"City":"string", | |||
"State":"string", | |||
"PostalCode":"string", | |||
"Latitude":"string", | |||
"Longitude":"string", | |||
"Distance":"string" | |||
}], | |||
"Records":[{ | |||
"City":"string", | |||
"State":"string", | |||
"PostalCode":"string", | |||
"Latitude":"string", | |||
"Longitude":"string", | |||
"Distance":"string" | |||
}] | }] | ||
} | } |
Latest revision as of 22:08, 6 December 2021
Reverse GeoCoder Navigation | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
| ||||||||||
| ||||||||||
| ||||||||||
Sample Code |
doLookup
REST Request
There is no recordID element because a REST request can only submit one record per request:
http://ReverseGeo.melissadata.net/V3/WEB/ReverseGeoCode/doLookup ?id={CustomerId} &lat={Latitude} &long={Longitude} &dist={MaxDistance} &recs={MaxRecords} &t={TransmissionReference} &opt={Options} &format=json
JSON Response
{ "Version":"string", "TransmissionReference":"string", "TransmissionResults":"string", "Results":"string", "TotalRecords":"string", "Records":[{ "AddressLine1":"string", "SuiteName":"string", "SuiteCount":"string", "City":"string", "State":"string", "PostalCode":"string", "AddressKey":"string", "Latitude":"string", "Longitude":"string", "Distance":"string", "MelissaAddressKey":"string", "MelissaAddressKeyBase":"string" }] }
doLookupPostalCodes
REST Request
There is no recordID element because a REST request can only submit one record per request:
http://ReverseGeo.melissadata.net/V3/WEB/ReverseGeoCode/doLookupPostalCodes ?id={CustomerId} &lat={Latitude} &long={Longitude} &dist={MaxDistance} &recs={MaxRecords} &t={TransmissionReference} &opt={Options} &format=json
JSON Response
{ "Version":"string", "TransmissionReference":"string", "TransmissionResults":"string", "Results":"string", "TotalRecords":"string", "Records":[{ "City":"string", "State":"string", "PostalCode":"string", "Latitude":"string", "Longitude":"string", "Distance":"string" }], "Records":[{ "City":"string", "State":"string", "PostalCode":"string", "Latitude":"string", "Longitude":"string", "Distance":"string" }] }