For your chosen Web API implement some code that uses it Dem

Solution

Use the API picker to find the right API for your project.

More about the web services

The remainder of this guide discusses techniques for setting up web service requests and parsing the responses. For particular documentation for each service, however, you must consult the appropriate documentation.

What is a web service?

The Google Maps API provides these web services as an interface for requesting Maps API data from external services and using them within your Maps applications. These services are designed to be used in conjunction with a map, as per the Maps API Terms of Service License Restrictions.

These web services use HTTP requests to specific URLs, passing URL parameters as arguments to the services. Generally, these services return data in the HTTP request as either JSON or XML for parsing and/or processing by your application.

A typical web service request is generally of the following form:

where service indicates the particular service requested and output indicates the response format (usually json or xml).

Full documentation of each service is contained within the particular developer guides for those services. However, this guide serves to hold some common practices useful for setting up your web service requests and processing your web service responses.

SSL Access

https://maps.googleapis.com/maps/api/service/output?parameters

HTTPS is required for all Maps API web service requests containing user data, or developer identifiers. Requests made over HTTP that include sensitive data may be rejected.

Building a Valid URL

You may think that a \"valid\" URL is self-evident, but that\'s not quite the case. A URL entered within an address bar in a browser, for example, may contain special characters (e.g. \"+\"); the browser needs to internally translate those characters into a different encoding before transmission. By the same token, any code that generates or accepts UTF-8 input might treat URLs with UTF-8 characters as \"valid\", but would also need to translate those characters before sending them out to a web server. This process is called URL-encoding.

We need to translate special characters because all URLs need to conform to the syntax specified by the W3 Uniform Resource Identifier specification. In effect, this means that URLs must contain only a special subset of ASCII characters: the familiar alphanumeric symbols, and some reserved characters for use as control characters within URLs. The table below summarizes these characters:

When building a valid URL, you must ensure that it contains only those characters shown above. Conforming a URL to use this set of characters generally leads to two issues, one of omission and one of substitution:

All characters to be URL-encoded are encoded using a \'%\' character and a two-character hex value corresponding to their UTF-8 character. For example, + in UTF-8 would be URL-encoded as%E4%B8%8A%E6%B5%B7%2B%E4%B8%AD%E5%9C%8B. The string ? and the Mysterians would be URL-encoded as%3F+and+the+Mysterians.

Some common characters that must be encoded are:

Converting a URL that you receive from user input is sometimes tricky. For example, a user may enter an address as \"5th&Main St.\" Generally, you should construct your URL from its parts, treating any user input as literal characters.

Additionally, URLs are limited to 8192 characters for all web services. For most services, this character limit will seldom be approached. However, note that certain services have several parameters that may result in long URLs.

Polite Use of Go