Reverse GeoCoder:Example Request: Difference between revisions
Jump to navigation
Jump to search
m Admin moved page Reverse GeoCoder Web Service:Example Request to Reverse GeoCoder:Example Request |
No edit summary |
||
| Line 34: | Line 34: | ||
&recs={MaxRecords} | &recs={MaxRecords} | ||
&t={TransmissionReference} | &t={TransmissionReference} | ||
</pre> | </pre> | ||
Revision as of 22:00, 7 March 2019
| Reverse GeoCoder Navigation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
| ||||||||||
| ||||||||||
| ||||||||||
| Sample Code |
The following requests detail the possible elements and general format of the four possible protocols.
JSON Request
{
"RequestArray": {
"CustomerId":"string",
"Latitude":"string",
"Longitude":"string",
"MaxDistance":"string",
"MaxRecords":"string",
"TransmissionReference":"string"
}
}
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}
XML Request
<RequestArray> <CustomerID>string</CustomerID> <Latitude>string</Latitude> <Longitude>string</Longitude> <MaxDistance>string</MaxDistance> <MaxRecords>string</MaxRecords> <TransmissionReference>string</TransmissionReference> </RequestArray>