Reverse GeoCoder:Request: Difference between revisions
Jump to navigation
Jump to search
Created page with "← Reverse GeoCoder Web Service Reference {| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px..." |
No edit summary |
||
| Line 20: | Line 20: | ||
|- | |- | ||
|[[Reverse GeoCoder Web Service:Request Elements|Request Elements]] | |[[Reverse GeoCoder Web Service:Request Elements|Request Elements]] | ||
|- | |- | ||
|[[Reverse GeoCoder Web Service:Example Request|Example Request]] | |[[Reverse GeoCoder Web Service:Example Request|Example Request]] | ||
Revision as of 23:27, 2 October 2014
← Reverse GeoCoder Web Service Reference
| Reverse GeoCoder Web Service Navigation | ||||
|---|---|---|---|---|
| ||||
| ||||
| ||||
| ||||
|
Request
A request consists of a protocol to make a call to the Web Service, detailing desired elements. The minimum required elements in a request are your Customer ID and at least one set of geo-coordinates.
The Reverse GeoCoder Web Service supports multiple protocols to access the Web Service, including SOAP, JSON, REST, and XML.