### Get Started with HERE Routing API v8

Source: https://docs.here.com/search_labelkey=v8&page=6

A guide to quickly get started with the HERE Routing API v8 on the HERE platform.

```APIDOC
## Get started

### Description
This section shows how to quickly get started with HERE Routing API v8 on the HERE platform, including basic setup and a sample request.

### Method
GET

### Endpoint
/routes

### Parameters
#### Query Parameters
- **apiKey** (string) - Required - Your HERE API key.
- **origin** (string) - Required - The starting point for the route (latitude,longitude).
- **destination** (string) - Required - The ending point for the route (latitude,longitude).

### Request Example
```json
{
  "example": "GET /routes?apiKey=YOUR_API_KEY&origin=52.5160,13.3779&destination=52.5160,13.3779"
}
```

### Response
#### Success Response (200)
- **routes** (array) - Contains the calculated route information.

#### Response Example
```json
{
  "example": "{\"routes\":[{\"sections\":[{\"duration\":30,\"length\":10000}]}]}"}
```
```

--------------------------------

### Get Started with HERE Geocoding & Search API v7

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics/quick-start

This section outlines how to get started quickly using HERE Geocoding and Search on the HERE platform. It covers obtaining a HERE account and the minimum setup required.

```APIDOC
## Get Started with HERE Geocoding & Search API v7

### Description
This section outlines how to get started quickly using HERE Geocoding and Search on the HERE platform. For more detailed information on HERE account setup, project creation, service linking, app registration, and authentication, see the Identity & Access Management Guide.

### Get a HERE account
Obtain access to the HERE platform through your organization administrator's invitation or get started for free.

*   If your company has already established a HERE platform organization, contact your organization admin who can invite you to join the organization.
*   If your company hasn’t established a HERE platform organization yet, you can get started for free. For more information, see the HERE platform pricing.
```

--------------------------------

### Tutorials

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics/response-items-enrichment-related

Guides and examples for implementing specific features, such as search along a route or sending user actions.

```APIDOC
## Tutorials

### Description
Step-by-step guides to help you implement advanced features and use cases with the API.

### Topics
- **How to implement search along the route**
- **Send user actions**
  - Action on Browse response
  - Action on Autosuggest response
  - Action on Lookup response
- **How to find geo-coordinates using Autosuggest**
```

--------------------------------

### Get Application API Request Example

Source: https://docs.here.com/bundle/identity-and-access-management-authentication-api-v1.1-api-reference/page/index

This example demonstrates how to retrieve an application's details using its HRN. The request involves a GET method to the '/apps/{app}' endpoint, where '{app}' is the URL-encoded HRN of the application. It requires appropriate authorization headers.

```http
GET /apps/{app} HTTP/1.1
Host: identity-and-access-management-authentication-api-v1.1-api-reference.docs-be.here.com
X-Correlation-ID: <your-correlation-id>
X-Request-ID: <your-request-id>
Authorization: Bearer <your-token>
```

--------------------------------

### Autocomplete API Example

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-autocomplete-language

This example demonstrates how to use the Autocomplete API to get suggestions for a given query. It shows the request URL with query parameters and the expected JSON response.

```APIDOC
## GET /v1/autocomplete

### Description
Retrieves a list of suggested locations based on a partial query string. This is useful for implementing type-ahead search functionality.

### Method
GET

### Endpoint
https://autocomplete.search.hereapi.com/v1/autocomplete

### Parameters
#### Query Parameters
- **q** (string) - Required - The partial text string for which to search for suggestions.
- **lang** (string) - Optional - The language of the results to be returned, specified as a BCP 47 language tag (e.g., "en-US", "it-IT").
- **limit** (integer) - Optional - The maximum number of suggestions to return. Defaults to 5.
- **apiKey** (string) - Required - Your unique API key for authentication.

### Request Example
```
GET https://autocomplete.search.hereapi.com/v1/autocomplete?q=Berli&lang=it-IT&limit=1&apiKey={YOUR_API_KEY}
```

### Response
#### Success Response (200)
- **items** (array) - A list of suggested location objects.
  - **title** (string) - The display title of the suggested item.
  - **id** (string) - A unique identifier for the suggested item.
  - **language** (string) - The language of the item's title and address.
  - **resultType** (string) - The type of the result (e.g., "locality", "street").
  - **address** (object) - An object containing the structured address components.
    - **label** (string) - The full address label.
    - **countryCode** (string) - The ISO 3166-1 alpha-3 country code.
    - **countryName** (string) - The name of the country.
    - **state** (string) - The name of the state or province.
    - **city** (string) - The name of the city.
    - **postalCode** (string) - The postal code.
  - **localityType** (string) - The specific type of locality (e.g., "city").
  - **highlights** (object) - Information about where the query terms appear in the result fields.

#### Response Example
```json
{
  "items": [
    {
      "title": "Germania, 10117, Berlino",
      "id": "here:cm:namedplace:20187403",
      "language": "it",
      "resultType": "locality",
      "localityType": "city",
      "address": {
        "label": "Berlino, Germania",
        "countryCode": "DEU",
        "countryName": "Germania",
        "stateCode": "BE",
        "state": "Berlino",
        "countyCode": "B",
        "county": "Berlino",
        "city": "Berlino",
        "postalCode": "10117"
      },
      "highlights": {
        "title": [
          {
            "start": 17,
            "end": 22
          }
        ],
        "address": {
          "label": [
            {
              "start": 0,
              "end": 5
            }
          ],
          "city": [
            {
              "start": 0,
              "end": 5
            }
          ]
        }
      }
    }
  ]
}
```
```

--------------------------------

### Example GET Request for Autocomplete Endpoint

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics/endpoint-autocomplete-brief

This code snippet demonstrates a GET request to the HERE Autocomplete API. It includes the base URL, the 'autocomplete' endpoint, a query parameter 'q' for the search term, and an 'apiKey' placeholder for authentication. This request is used to find address completions.

```http
GET https://autocomplete.search.hereapi.com/v1/
    autocomplete
    ?q=Pariser+2+Frank
    &apiKey={YOUR_API_KEY}

```

--------------------------------

### Tutorials

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-geocode-hybrid

Guides and tutorials for using the API, including implementing search along a route, sending user actions, and finding geocoordinates using Autosuggest.

```APIDOC
## Tutorials

### Description
This section provides tutorials and guides for implementing various features using the API.

### Tutorials List
*   **How to implement search along the route**
*   **Send user actions**
    *   Action on Browse response
    *   Action on Autosuggest response
    *   Action on Lookup response
*   **How to find geo-coordinates using Autosuggest**
```

--------------------------------

### Get User Permissions API Request Example (Conceptual)

Source: https://docs.here.com/bundle/identity-and-access-management-account-v1-api-reference

This conceptual example illustrates how to make a GET request to retrieve user permissions. It includes query parameters for pagination and requires Bearer authorization.

```http
GET /permissions?count=100&pageToken=your_page_token
Authorization: Bearer YOUR_ACCESS_TOKEN
```

--------------------------------

### Query Parameter Examples

Source: https://docs.here.com/bundle/geocoding-and-search-api-v7-api-reference

Examples demonstrating how to construct query strings for various search scenarios, including free-text queries with wildcards and location-based searches.

```text
q=Eismieze Berlin
q=res*
q=berlin+bran*
q=New+Yok+Giants
```

```text
at=52.5308,13.3856
at=-13.163068,-72.545128
```

```text
in=countryCode:USA
in=countryCode:CAN,MEX,USA
in=circle:52.53,13.38;r=10000
in=bbox:13.08836,52.33812,13.761,52.6755
```

```text
fuelStation[fuelTypes]=biodiesel,ethanol,gasoline
```

```text
mobilityMode=car
mobilityMode=motorbike
mobilityMode=truck
```

```text
ranking=excursionDistance
```

```text
route=BFoz5xJ67i1B1B7PzIhaxL7Y
route=BFoz5xJ67i1B1B7PzIhaxL7Y;w=5000
route=BlD05xgKuy2xCCx9B7vUCl0OhnRC54EqSCzpEl-HCxjD3pBCiGnyGCi2CvwFCsgD3nDC4vB6eC;w=2000
```

--------------------------------

### Autosuggest Query Example

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-signals-autosuggest

This example demonstrates how to use the Autosuggest API to get location suggestions based on a partial query and a specific geographic location.

```APIDOC
## GET /v1/autosuggest

### Description
Retrieves location suggestions based on a partial text query and a specified geographic point.

### Method
GET

### Endpoint
`https://autosuggest.search.hereapi.com/v1/autosuggest`

### Query Parameters
- **apiKey** (string) - Required - Your HERE API key.
- **at** (string) - Required - Latitude and longitude coordinates (e.g., "52.5044,13.33673").
- **limit** (integer) - Optional - The maximum number of suggestions to return.
- **q** (string) - Required - The partial text query entered by the user.

### Request Example
```bash
curl -sD /dev/stderr "https://autosuggest.search.hereapi.com/v1/autosuggest?apiKey=$API_KEY\&at=52.5044,13.33673\&limit=5\&q=rest" | jq .
```

### Response
#### Success Response (200)
- **items** (array) - A list of suggested items, which can be categories or places.
  - **title** (string) - The display title of the suggestion.
  - **id** (string) - A unique identifier for the suggestion.
  - **resultType** (string) - The type of the result (e.g., "categoryQuery", "place").
  - **href** (string) - A URL for a follow-up request related to the suggestion.
- **queryTerms** (array) - Terms related to the query (often empty).

#### Response Example
```json
{
  "items": [
    {
      "title": "Restaurant",
      "id": "here:cm:ontology:restaurant",
      "resultType": "categoryQuery",
      "href": "https://autosuggest.search.hereapi.com/v1/discover?at=52.5044%2C13.33673&limit=5&q=Restaurant&_ontology=restaurant"
    },
    {
      "title": "Marjellchen (Restaurant Marjellchen)",
      "id": "here:pds:place:276u336x-1e3dc04849204f10a3643af8f781e36e",
      "resultType": "place"
    }
  ],
  "queryTerms": []
}
```
```

--------------------------------

### Example GET Request for Reverse Geocoding with Navigation Attributes

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics/response-items-enrichment-nav

This is an example of a GET request to the HERE Geocoding and Search API's `/revgeocode` endpoint. It demonstrates how to include the `showNavAttributes` parameter with multiple values (functionalClass, access, physical, speedLimits) to retrieve detailed road navigation information for a given location.

```http
GET https://revgeocode.search.hereapi.com/v1/
    revgeocode
    ?at=37.7702656,-122.4213821
    &showNavAttributes=functionalClass,access,physical,speedLimits
    &apiKey={YOUR_API_KEY}

```

--------------------------------

### Tutorials

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics/response-items-enrichment

Guides and tutorials for implementing various features of the HERE Geocoding & Search API v7, including search along routes and handling user actions.

```APIDOC
## Tutorials

### Description
Learn how to implement advanced features and use cases with the HERE Geocoding & Search API v7.

### Topics
- **How to implement search along the route**
- **Send user actions**
  - **Action on Browse response**
  - **Action on Autosuggest response**
  - **Action on Lookup response**
- **How to find geo-coordinates using Autosuggest**
```

--------------------------------

### Example Request Payload for Creating an Application

Source: https://docs.here.com/bundle/identity-and-access-management-authentication-api-v1.1-api-reference/page/index

A sample JSON payload demonstrating how to create a new application with basic details like name and description.

```json
{
  "name": "My Application",
  "description": "This is a description of My Application"
}
```

--------------------------------

### Query Parameter Examples

Source: https://docs.here.com/bundle/geocoding-and-search-api-v7-api-reference/page/index

Illustrates how to construct query strings for the Search API, including free-text search with wildcard-like behavior and specifying search context.

```text
q=Eismieze Berlin
res
rest
resta
restau
berlin+bran
berlin+brand
berlin+branden
New+Yok+Giants
```

--------------------------------

### Get Map Attributes for a Tile

Source: https://docs.here.com/bundle/map-attributes-api-developer-guide/page/topics/quick-start

This endpoint allows you to retrieve map attributes for a specific tile. You need to provide the desired layers and the tile ID in your request.

```APIDOC
## GET /v8/maps/attributes

### Description
Retrieves map attributes for a specified tile, including various details like link IDs, country codes, vehicle types, and more, depending on the requested layers.

### Method
GET

### Endpoint
`https://smap.hereapi.com/v8/maps/attributes`

### Parameters
#### Query Parameters
- **layers** (string) - Required - Specifies the map layers for which to retrieve attributes (e.g., `LINK_ATTRIBUTE_FC5`).
- **in** (string) - Required - Defines the input geometry, typically a tile ID (e.g., `tile:72503709`).
- **apiKey** (string) - Required - Your unique API key for authentication.

### Request Example
```json
{
  "code": "curl -gX GET 'https://smap.hereapi.com/v8/maps/attributes?\nlayers=LINK_ATTRIBUTE_FC5\n&in=tile:72503709&\n&apiKey=YOUR_API_KEY'"
}
```

### Response
#### Success Response (200)
- **Tiles** (array) - Contains information about the requested tiles.
  - **Meta** (object) - Metadata for the tile, including layer name, tile ID, level, map region, and map release.
  - **Rows** (array) - An array of attribute objects for the tile.
    - **LINK_ID** (string) - The unique identifier for the link.
    - **ISO_COUNTRY_CODE** (string) - The ISO country code.
    - **VEHICLE_TYPES** (string) - Information about allowed vehicle types.
    - **URBAN** (string) - Indicates if the road is in an urban area.
    - **TRANSPORT_VERIFIED** (string) - Indicates if transport has been verified.
    - **FUNCTIONAL_CLASS** (string) - The functional class of the road.
    - **CONTROLLED_ACCESS** (string) - Indicates if the road has controlled access.
    - **LIMITED_ACCESS_ROAD** (string) - Indicates if it is a limited access road.
    - **TRAVEL_DIRECTION** (string) - The direction of travel.
    - **BOAT_FERRY** (string) - Indicates if a boat ferry is present.
    - **RAIL_FERRY** (string) - Indicates if a rail ferry is present.
    - **MULTI_DIGITIZED** (string) - Indicates if the road is multi-digitized.
    - **DIVIDER** (string) - Indicates if a divider is present.
    - **DIVIDER_LEGAL** (string) - Indicates if the divider is legal.
    - **FRONTAGE** (string) - Indicates frontage information.
    - **PAVED** (string) - Indicates if the road is paved.
    - **RAMP** (string) - Indicates if it is a ramp.
    - **PRIVATE** (string) - Indicates if the road is private.
    - **POI_ACCESS** (string) - Indicates access for Points of Interest.
    - **INTERSECTION_CATEGORY** (string/null) - The category of the intersection.
    - **SPEED_CATEGORY** (string) - The speed category of the road.
    - **LANE_CATEGORY** (string) - The lane category.
    - **COVERAGE_INDICATOR** (string) - Coverage indicator.
    - **TO_REF_NUM_LANES** (string/null) - Number of lanes to the reference.
    - **FROM_REF_NUM_LANES** (string/null) - Number of lanes from the reference.
    - **PHYSICAL_NUM_LANES** (string/null) - Physical number of lanes.
    - **LOW_MOBILITY** (string) - Indicates low mobility restrictions.
    - **PUBLIC_ACCESS** (string) - Indicates public access.
    - **GRADE_CATEGORY** (string/null) - The grade category.
    - **ROUTE_TYPES** (string) - Information about route types.
    - **OVERPASS_UNDERPASS** (string/null) - Indicates overpass or underpass.
    - **TOPOLOGY_ID** (string) - The topology identifier.
    - **START_OFFSET** (string) - The start offset.
    - **END_OFFSET** (string) - The end offset.

#### Response Example
```json
{
  "Tiles": [
    {
      "Meta": {
        "layerName": "LINK_ATTRIBUTE_FC5",
        "tileId": 72503709,
        "level": 13,
        "mapRegion": "NA",
        "mapRelease": "25103"
      },
      "Rows": [
        {
          "LINK_ID": "866492995",
          "ISO_COUNTRY_CODE": "PAN",
          "VEHICLE_TYPES": "16",
          "URBAN": "N",
          "TRANSPORT_VERIFIED": "N",
          "FUNCTIONAL_CLASS": "5",
          "CONTROLLED_ACCESS": "N",
          "LIMITED_ACCESS_ROAD": "N",
          "TRAVEL_DIRECTION": "B",
          "BOAT_FERRY": "N",
          "RAIL_FERRY": "N",
          "MULTI_DIGITIZED": "N",
          "DIVIDER": "N",
          "DIVIDER_LEGAL": "N",
          "FRONTAGE": "N",
          "PAVED": "N",
          "RAMP": "N",
          "PRIVATE": "N",
          "POI_ACCESS": "N",
          "INTERSECTION_CATEGORY": null,
          "SPEED_CATEGORY": "8",
          "LANE_CATEGORY": "1",
          "COVERAGE_INDICATOR": "B8",
          "TO_REF_NUM_LANES": null,
          "FROM_REF_NUM_LANES": null,
          "PHYSICAL_NUM_LANES": null,
          "LOW_MOBILITY": "3",
          "PUBLIC_ACCESS": "Y",
          "GRADE_CATEGORY": null,
          "ROUTE_TYPES": "0",
          "OVERPASS_UNDERPASS": null,
          "TOPOLOGY_ID": "468857692",
          "START_OFFSET": "00",
          "END_OFFSET": "52176"
        }
      ]
    }
  ]
}
```
```

--------------------------------

### Modify Geometries via HTTP GET (WKT)

Source: https://docs.here.com/bundle/here-map-attributes-api-api-reference

This example demonstrates modifying geometries using an HTTP GET request with WKT content. It requires the layerId and action parameters. Note: This feature is deprecated.

```http
GET /v8/maps/modify?layerId={app_id}.{mapName}.{layerName}&action=delete&wktQuote=\"&ownerAppId=<owner_app_id>&file="<WKT content>" HTTP/1.1
Host: smap.hereapi.com
```

--------------------------------

### Discover API with Simplified Route Example

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics/implementing-route

Example usage of the HERE Discover API, including a simplified route parameter, demonstrating how a simplified polyline can be integrated.

```APIDOC
## Discover API with Simplified Route Example

### Description

This example shows a request to the HERE Discover API (`/v1/discover`) which includes a `route` parameter. This parameter likely expects a simplified flexible polyline, demonstrating the practical application of route simplification for services with URL length constraints.

### Method

`GET`

### Endpoint

`https://discover.search.hereapi.com/v1/discover`

### Parameters

#### Path Parameters

None

#### Query Parameters

- **apiKey** (string) - Required - Your HERE API key.
- **at** (string) - Required - Latitude and longitude coordinates (e.g., `52.5308,13.3847`).
- **limit** (integer) - Optional - The maximum number of items to return.
- **route** (string) - Required - A simplified flexible polyline string representing a route.
- **q** (string) - Required - The search query (e.g., `restaurant`).

### Request Example

```
https://discover.search.hereapi.com/v1/discover?apiKey={YOUR_API_KEY}&at=52.5308,13.3847&limit=10&route=BF0-zgKyl2xCvCrJ2mBtwBwY9kB2xEthIyYrjDuBjlBoOpEoLNoJzE0I9KkPjeiI5JwrDzoCqdtc8H1NgKtjBsM1WuQ_yB2alkCuGlK8EpDuFUiPgV-HT0LpOkJDmD5B2dnnBmI_G8J_D0zEmW4RbiSzD6N3EuUtKqS9MsOjNsZneiyC1oE8RxY8hB1iB8tBjesJzJ8HhOuErPmC1W1FxjBzB7YD3kGiK5iFatyBvEzlC7Nj_D1B7lBgB3rBiGj5Bq8B7tL-YhjHsM_6BiSt2Bi8Cv7F0SrrBwO_nBoMtnBiN7zBggBzuFqRrqC-LvmB8QzsB4hBrkCohB_xBkiBxnBqhBvd4hBrW2lBpRsnB_JysB1DizDhBkYlE6a3JqW3M6ZvU2pC5tC6oBziB8uB3c2kF51C4XvPyT_QmhBpnB45Bt7CmnC31CuW5f0NjYwOtfiqBn2DiVhtBoWxjB09BjwC-zBx5C-brmBmczcg1BruB0apbklEtiFkjB1nBwiBlhB4_BtzB8X3XyZ9hBm4Bn6CwiB7oBoWxTkZzQszCzlBuWzMge1WoclckZpgBgcxuBu1Bl3DgTnmBwaloB8V9YkbjXgb9PsKZuGwCmRgRsI4DqL1B-J3I8F_K0D5NsFtvCkJ77B2K5uB4PtyBsO7jBgVnqBqTtf6gBrtBkYtpB2Y12BqS92BuKnpBqJ5yByPt9E6JxhCwQ9jCmSj1ByWryBmattBqRxY4xBh9BojB33BqwElzIqV_wBwbhtCkXnzByZzrBg4BnxCymB5oCsbhiCsY3rCmNj0B2mBpwF4NhxBqXn9BkkBhrCiZ1lCqNr0B-Jz0BgMnzC4Gt-BsGrxDkC1yIqF7jCsLpnCgJlnB-NhvBkP3oBmQrkBge71B23BhuC0Std-SljBgU3tBkW_jC2gBzwEglB94D4MzhC0L9vDoNtnCyU_kCufpqCwQhuB0MjvBkKj1BqFhrBmDpyBqCzjIoChlC4HhpC4NnkCmRn5BgU5xBoVzpBigBzyB2QlewQ7lB0cpxCiO9gBqS_hBgkB72BiSxf0Q_kB8M9kB-dp5D-e33C0OnyByLzyByJ17BiGnjCqBrhC7BxvB3K1_DFxqC-Hp9C0I1zB-JjsB4WtqC0drlCmWzoB03CrrEqR9gB8P5kBqVxhCwShyCkN3tB6O_nBqdpjC6QtxBiOx5B6Ir2BoF99BM3zBxCzwBtMl0DlBzyBuCn6B-zB1nM4T_6G0FtuE8EzlCmjC7hS2GzsCqI3yF_G7-F0D54J0FzwC2O35Cw2Cv-K8xB9xHmUhpC6pBlgE6QtrC2JlqCwF9wCS1lCvCj9DwC52BuV54DsK_1D2WrjDuO7hEmenwEqIzkCmB32BjD_yBtzB_pL1EjvB_BhtB-B3iCkR3pGvBpkBnM1oDL5wB-Gv2B4iB_zEqFjsBsC9vBnCtlCvNrxErtBrlJ1HnsDb3oB2CppBkZnkEgB_V1B_kB1DjRpH3R1JtP_M9NvWzO55B7XxYnPnchXlpBjoBnhBnrBriB97BpbjhClOtrBzOt3BjH1xBoB5hBgLzpC2DtvFqD5N6G_I85B51BwUvRoLtE2KiD4MwHqnBgkB8UqQ0EuCiChBkL_ZmIpjBuNtlBuN9R6CrMWjkB2MyB6RvH6TjiB2GnY0B9R7I5E9I9H3CNhDyF;w=1000&q=restaurant
```

### Response

#### Success Response (200)

Returns a JSON object containing discover results based on the query and location, potentially influenced by the provided route.

#### Response Example

```json
{
  "results": [
    {
      "title": "Example Restaurant",
      "vicinity": "123 Main St, City",
      "position": {
        "lat": 52.5308,
        "lng": 13.3847
      }
    }
    // ... more results
  ]
}
```
```

--------------------------------

### HERE Search API - Browse Endpoint Request Example

Source: https://docs.here.com/bundle/geocoding-and-search-api-v7-api-reference

Example of a POST request to the HERE Search API's browse endpoint. This demonstrates how to specify query parameters like 'apiKey' and 'at' along with additional fields to enrich the search results.

```bash
curl -X POST "https://browse.search.hereapi.com/v1/browse?apiKey=YOUR_API_KEY&at=52.5160,13.3779&show=ev,fuel,truck"
```

--------------------------------

### Tutorial: Send User Actions

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics/request-constructing

Instructions on how to send user interaction data back to the HERE API, potentially for improving services or personalization.

```APIDOC
## Tutorial: Send user actions

### Description
Learn how to send user interaction events to the HERE API to provide feedback or enable specific features.

### Actions
- **Action on Browse response**
- **Action on Autosuggest response**
- **Action on Lookup response**

### Parameters
(Details on the parameters required for sending user actions.)

### Request Example
(Example request body for sending a user action.)
```

--------------------------------

### Autocomplete API Request Example (English Query)

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-autocomplete-language

This example demonstrates a GET request to the HERE Autocomplete API to find 'Athens'. It specifies a limit of 1 result and requires an API key for authentication. The query is in English.

```http
GET https://autocomplete.search.hereapi.com/v1/autocomplete
    ?q=Athens
    &limit=1
    &apiKey={YOUR_API_KEY}

```

--------------------------------

### Import Geometries via HTTP GET (WKT)

Source: https://docs.here.com/bundle/here-map-attributes-api-api-reference

This example demonstrates importing WKT geometries using an HTTP GET request. It requires the layerId and the WKT content as a query parameter. Note: This feature is deprecated.

```http
GET /v8/maps/upload?layerId={app_id}.{mapName}.{layerName}&wkt="<WKT content>" HTTP/1.1
Host: smap.hereapi.com
```

--------------------------------

### Tutorials

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-geocode-scoring

Guides and tutorials for implementing specific features of the HERE Geocoding & Search API v7.

```APIDOC
## Tutorials

### Description
Step-by-step guides to help developers implement various functionalities using the HERE Geocoding & Search API v7.

### Tutorials List

*   **How to implement search along the route**
    *   Description: Guide on performing searches for points of interest along a specified route.

*   **Send user actions**
    *   Description: Instructions on how to track user interactions with API responses for analytics or personalization.
    *   Sub-sections:
        *   Action on Browse response
        *   Action on Autosuggest response
        *   Action on Lookup response

*   **How to find geo-coordinates using Autosuggest**
    *   Description: Tutorial demonstrating how to obtain geographic coordinates by leveraging the Autosuggest feature.
```

--------------------------------

### GET /lookup

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-signals-lookup

Retrieves detailed information about a specific place using its unique resource ID. This is useful for getting details after a search or signal action.

```APIDOC
## GET /lookup

### Description
This endpoint retrieves detailed information about a specific place using its unique ID. It's often used to get more context about a resource identified in a previous search or signal.

### Method
GET

### Endpoint
https://lookup.search.hereapi.com/v1/lookup

### Parameters
#### Query Parameters
- **apiKey** (string) - Required - Your API key for authentication.
- **id** (string) - Required - The unique identifier of the place (e.g., `here:pds:place:276u339g-0dd32a93728c47c3b35985e550f30a70`).

### Request Example
```curl
curl -sD /dev/stderr "https://lookup.search.hereapi.com/v1/lookup?apiKey=$API_KEY\n&id=here:pds:place:276u339g-0dd32a93728c47c3b35985e550f30a70" \
| jq .
```

### Response
#### Success Response (200)
- **title** (string) - The name of the place.
- **id** (string) - The unique identifier of the place.
- **access** (array) - An array of access points, each with `lat` and `lng` coordinates.

#### Response Example
```json
{
  "title": "Flughafen Berlin Brandenburg Willy Brandt",
  "id": "here:pds:place:276u339g-0dd32a93728c47c3b35985e550f30a70",
  "access": [{ "lat": 52.36447, "lng": 13.51003 }],
  ...
}
```
```

--------------------------------

### Autocomplete API Request Example (Transliterated Query, English Preferred)

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-autocomplete-language

This example shows a GET request to the HERE Autocomplete API for 'Athina Stad' (transliterated Greek) with a preferred response language of 'en-US'. The API key is required.

```http
GET https://autocomplete.search.hereapi.com/v1/autocomplete
    ?q=Athina+Stad
    &lang=en-US
    &apiKey={YOUR_API_KEY}

```

--------------------------------

### Tutorials

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-geocode-spatial-reference

A collection of tutorials demonstrating various use cases and implementation tips for the HERE Geocoding & Search API v7.

```APIDOC
## Tutorials

### Description
Guides and examples to help developers implement specific features and use cases with the API.

### Tutorials List
- **How to implement search along the route**
- **Send user actions**
  - Action on Browse response
  - Action on Autosuggest response
  - Action on Lookup response
- **How to find geo-coordinates using Autosuggest**
```

--------------------------------

### Reverse Geocoding Request Example

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-revgeocode-result-type-filter

This example demonstrates a basic GET request to the `/revgeocode` endpoint. It specifies the coordinates (`at`), a limit for the number of results, the desired language, and requires an API key for authentication. The response will contain location details.

```HTTP
GET https://revgeocode.search.hereapi.com/v1/revgeocode
    ?at=50.1158056,8.6786751
    &limit=3
    &lang=en-US
    &apiKey={YOUR_API_KEY}
```

--------------------------------

### Via Waypoint Examples

Source: https://docs.here.com/bundle/routing-api-v8-api-reference/page/index

Provides examples of specifying via waypoints, including coordinates, side of street hints, course, radius, name hints, stop durations, pass-through settings, display locations, weight changes, and charging station details.

```plaintext
via=51.611571,11.351608
via=52.531052,13.384872;sideOfStreetHint=52.530941,13.384939;matchSideOfStreet=always
via=51.611571,11.351608;course=170;radius=20;minCourseDistance=500
via=52.510319,13.285616;nameHint=Kaiserdamm
via=51.611571,11.351608!stopDuration=600
via=51.611571,11.351608!passThrough=true
via=52.52697,13.42500;displayLocation=52.51885,13.46237
via=52.531052,13.384872!currentWeightChange=+500
via=51.611571,11.351608!charging=(power=100;current=250;voltage=400;supplyType=dc;minDuration=1200)
```

--------------------------------

### HERE API Geocoding Request Example

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics-api/code-geocode-result-types-filter

This is an example of a GET request to the HERE API for geocoding. It specifies the base URL, the geocode endpoint, query parameters for the search term ('q') and result types ('types'), and requires an API key for authentication.

```http
GET https://geocode.search.hereapi.com/v1/
    geocode
    ?q=Harfowa%2C+Warszawa
    &types=address%2Carea
    &apiKey={YOUR_API_KEY}


```

--------------------------------

### Nearby Address Request Example (HTTP)

Source: https://docs.here.com/bundle/geocoding-and-search-api-developer-guide/page/topics/response-items-enrichment-related

This example demonstrates an HTTP GET request to the HERE API Revgeocode endpoint to retrieve nearby address information. It specifies the latitude and longitude, bearing, language, and requests related nearby address data.

```HTTP
GET https://revgeocode.search.hereapi.com/v1/
    revgeocode
    ?at=2.5186672,13.4079117
    &bearing=60
    &lang=en-US
    &showRelated=nearbyAddress
    &apiKey={YOUR_API_KEY}

```