# LocationIQ Documentation Documentation

## Guides
- [Autocomplete API](https://docs.locationiq.com/docs/autocomplete.md): The Autocomplete API is designed to enhance search experiences in frontend applications, offering instant place suggestions in search bars and form fields as users type, recognizing both partial and full words for a streamlined and efficient user interaction.
- [Reverse Geocoding API](https://docs.locationiq.com/docs/reverse-geocoding.md): Reverse geocoding is the process of converting a coordinate or location (latitude, longitude) to a readable address or place name. This permits the identification of nearby street addresses, places, and/or area subdivisions such as a neighborhood, county, state, or country.
- [Interactive Playground](https://docs.locationiq.com/docs/reverse-geocoding-sandbox.md)
- [Search / Forward Geocoding](https://docs.locationiq.com/docs/search-forward-geocoding.md): **Forward Geocoding** is the process of converting addresses (like "_Statue of Liberty, New York_") into geographic coordinates (latitude and longitude), allowing you to place markers on a map, tidy mismatched or incomplete addresses, optimize delivery routes, enhance customer profiling, and offer location-specific promotions.
- [Timezone API](https://docs.locationiq.com/docs/timezone.md): The Timezone API provides time offset data for locations on the surface of the earth.
- [Convert Meeting Time Across TimeZones](https://docs.locationiq.com/docs/quickstart-convert-time-across-timezones.md)
- [Examples - Leaflet](https://docs.locationiq.com/docs/examples-leaflet.md)
- [Examples - Openlayer](https://docs.locationiq.com/docs/examples-openlayer.md)
- [Examples - Maplibre](https://docs.locationiq.com/docs/maps-samples.md)
- [Static Maps](https://docs.locationiq.com/docs/static-maps.md): Static maps are standalone images (in JPG or PNG format) that can be displayed on web and mobile devices
- [API Reference](https://docs.locationiq.com/docs/static-maps-api-reference.md): Static maps are standalone images (in JPG or PNG format) that can be displayed on web and mobile devices without the aid of a mapping library or API. Our Static Maps API returns an image in response to an HTTP request. For each request, you can specify the map's location, size of the image, zoom level, type of map. You can also place markers or draw a path at locations on the map.
- [Code Samples](https://docs.locationiq.com/docs/client-libraries.md)
- [Match Quality](https://docs.locationiq.com/docs/match-quality.md)
- [Map Matching API](https://docs.locationiq.com/docs/map-matching-api.md): Matching API matches or snaps given GPS points to the road network in the most plausible way.
- [Matrix API](https://docs.locationiq.com/docs/matrix-api.md): Computes duration of the fastest route between all pairs of supplied coordinates. Returns the durations or distances or both between the coordinate pairs.
- [Optimize API](https://docs.locationiq.com/docs/optimize-api.md): Optimize API solves the Traveling Salesman Problem(TSP) using a greedy heuristic (farthest-insertion algorithm) for 10 or more waypoints and uses brute force for less than 10 waypoints. The returned path does not have to be the fastest path. As TSP is NP-hard it only returns an approximation.
- [General Options](https://docs.locationiq.com/docs/routing-api.md)

## API Reference
- [Autocomplete](https://docs.locationiq.com/reference/autocomplete-2.md): The Autocomplete API is a variant of the Search API that returns place predictions in response to an HTTP request. The request specifies a textual search string and optional geographic bounds. The service can be used to provide autocomplete functionality for text-based geographic searches, by returning places such as businesses, addresses and points of interest as a user types.   The Autocomplete API can match on full words as well as substrings. Applications can therefore send queries as the user types, to provide on-the-fly place predictions.  <a href="https://locationiq.com/demo#autocomplete" target="_blank">Try this API in our Playground</a>  > If you use Leaflet for your maps, you add LocationIQ's Autocomplete as a plugin instantly! You can <a href="https://github.com/location-iq/leaflet-geocoder" target="_blank">view instructions here</a>. You can also view a <a href="https://maps.locationiq.com" target="_blank">live demo here</a>.  > The Autocomplete API endpoint (https://api.locationiq.com/v1) offers an Anycast IP address and route user requests to a datacenter closest to them. You can still manually specify a `region` similar to other LocationIQ endpoints, but in the interest of end-user experience, we don't recommended such a configuration.
- [Balance](https://docs.locationiq.com/reference/balance-api-ref.md): The Balance API provides a count of request credits left in the user's account for the day. Balance is reset at midnight UTC every day (00:00 UTC).
- [Lookup](https://docs.locationiq.com/reference/lookup-1.md): The lookup API allows querying the address and other details of one or multiple OSM objects, such as nodes, ways, or relations.
- [Nearby - Places (Public BETA)](https://docs.locationiq.com/reference/nearby-poi-api.md): The Nearby API returns nearby places around a specified location. Results can include points of interest such as cafes, hospitals, and airports, as well as place-level features such as cities, depending on the requested `tag`. Note: The Nearby API endpoint is presently in BETA. The request or response format may change without notice. While we don't expect to remove any elements, there will be additions.
- [Reverse Geocoding](https://docs.locationiq.com/reference/reverse-api.md): Reverse geocoding is the process of converting a coordinate or location (latitude, longitude) to a readable address or place name. This permits the identification of nearby street addresses, places, and/or area subdivisions such as a neighborhood, county, state, or country.
- [Directions Service](https://docs.locationiq.com/reference/directions.md): Finds the fastest route between coordinates in the supplied order.
- [Matching Service](https://docs.locationiq.com/reference/matching.md): Matching API matches or snaps given GPS points to the road network in the most plausible way. Please note the request might result multiple sub-traces. Large jumps in the timestamps (> 60s) or improbable transitions lead to trace splits if a complete matching could not be found. The algorithm might not be able to match all points. Outliers are removed if they can not be matched successfully.
- [Matrix Service](https://docs.locationiq.com/reference/matrix.md): Computes duration of the fastest route between all pairs of supplied coordinates. Returns the durations or distances or both between the coordinate pairs. Note that the distances are not the shortest distance between two coordinates, but rather the distances of the fastest routes.
- [Nearest Service](https://docs.locationiq.com/reference/nearest.md): Snaps a coordinate to the street network and returns the nearest n matches. Where coordinates only supports a single {longitude},{latitude} entry.
- [Optimize Service](https://docs.locationiq.com/reference/optimize.md): Optimize API solves the Traveling Salesman Problem(TSP) using a greedy heuristic (farthest-insertion algorithm) for 10 or more waypoints and uses brute force for less than 10 waypoints. The returned path does not have to be the fastest path. As TSP is NP-hard it only returns an approximation. Note that all input coordinates have to be connected for the optimize service to work.
- [Postal Code Search](https://docs.locationiq.com/reference/search-postalcode.md): Postal Address Lookup streamlines the task of locating details when only a postal code match is necessary. It’s particularly useful when you want to fetch location information without handling complete addresses.
- [Structured Geocoding](https://docs.locationiq.com/reference/search-structured.md): Structured Query offers a more specific way to search for locations. Instead of using a single text string, you can provide distinct address components in a structured format. This includes specifying elements like street, neighborhood, city, state, country, and postal code, each sent as separate API parameters.
- [Free Form Query](https://docs.locationiq.com/reference/search.md): The Search API allows converting addresses, such as a street address, into geographic coordinates (latitude and longitude). These coordinates can serve various use-cases, from placing markers on a map to helping algorithms determine nearby bus stops. This process is also known as Forward Geocoding.
- [Timezone](https://docs.locationiq.com/reference/timezone-api.md): The Timezone API provides time offset data for locations on the surface of the earth.