Difference between revisions of "Reverse GeoCoder:Request"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
{{ ReverseGeoCoderNav | |||
|RequestCollapse= | |||
{ | }} | ||
{ | |||
| | |||
Line 58: | Line 8: | ||
==Request== | ==Request== | ||
A request consists of a protocol to make a call to the | 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 set of geo-coordinates. | ||
Reverse GeoCoder supports multiple protocols to access the service, including SOAP, JSON, REST, and XML. | |||
[[Category:Reverse GeoCoder | [[Category:Reverse GeoCoder]] | ||
[[Category:Reference]] | [[Category:Reference]] |
Revision as of 22:55, 10 March 2015
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 Customer ID and at least one set of geo-coordinates.
Reverse GeoCoder supports multiple protocols to access the service, including SOAP, JSON, REST, and XML.