Reverse GeoCoder:Request: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
Reverse GeoCoder supports multiple protocols to access the service, including SOAP, JSON, REST, and XML. | Reverse GeoCoder supports multiple protocols to access the service, including SOAP, JSON, REST, and XML. | ||
==URL== | |||
{{URL-ReverseGeoCoder}} | |||
[[Category:Reverse GeoCoder]] | [[Category:Reverse GeoCoder]] | ||
[[Category:Reference]] | [[Category:Reference]] | ||
Revision as of 19:43, 7 December 2018
| Reverse GeoCoder Navigation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
| ||||||||||
| ||||||||||
| ||||||||||
| Sample Code |
Request
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 License Key and at least one set of geo-coordinates.
Reverse GeoCoder supports multiple protocols to access the service, including SOAP, JSON, REST, and XML.
URL
REST, XML, JSON, etc.
Use URL Standard http://reversegeo.melissadata.net/v3/WEB/ReverseGeoCode/DoLookup Secure https://reversegeo.melissadata.net/v3/WEB/ReverseGeoCode/DoLookup