Here Browse

Technical Preview

Overview

Client-mode REST API connectors for HERE Platform: geocoding and reverse geocoding, place search, truck routing with tolls, isolines, routing matrix, real-time traffic, waypoint sequencing, GPS trace route matching and Tour Planning. This is one of the templates in the HERE Platform REST API app (here-platform). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).

Not yet verified against the live vendor API: No HERE API key: every event except the public /version ones needs apiKey. Every HERE host was probed and answers 401 ‘apiKey invalid’ for a dummy key; Routing, Isoline and Matrix /version answered 200 live, but no keyed call could run.

Auth

schemes: [“API key query parameter (apiKey=, apikey= on Route Matching and Tour Planning)”]
secrets: [“HERE_API_KEY”]
note: OAuth 2.0 bearer (OAuth 1.0a signed token request to account.api.here.com) not packaged. *Version events are public.

Template parameters

Placeholder	Type	Description	Required
`RouteName`	string	Name of the Here Browse connector	no
`BaseUrl`	string	Here Browse base URL without trailing slash (e.g. https://browse.search.hereapi.com)	yes

BASE_ADDRESS default: https://browse.search.hereapi.com.

Events

Event	Method	Endpoint	Request topic	Response topic	Payload fields
`Browse`	GET	`/v1/browse?apiKey={value.json.apikey}&at={value.json.at}{value.json.params}`	`fleet/here/places/browse`	`fleet/here/places/browse/response`	`apikey`, `at`, `params`

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:

mosquitto_pub -t '$SYS/Coreflux/Command' -m "-routeCode HERE_BROWSE"

The deployable connector from the REST API app, with BASE_ADDRESS already filled in:

DEFINE ROUTE HereBrowse WITH TYPE REST_API
    ADD REST_API_CONFIG
        WITH BASE_ADDRESS "https://browse.search.hereapi.com"
        WITH ENABLE_CLIENT "true"
        WITH USE_SSL "true"
        WITH REQUEST_TIMEOUT '30'
        WITH DEFAULT_CONTENT_TYPE "application/json"
    ADD EVENT Browse
        WITH SOURCE_TOPIC "fleet/here/places/browse"
        WITH DESTINATION_TOPIC "fleet/here/places/browse/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/v1/browse?apiKey={value.json.apikey}&at={value.json.at}{value.json.params}"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "User-Agent" "Coreflux-Broker REST_API route (https://www.coreflux.org)"

Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call Browse by publishing a JSON payload to its request topic, and read the reply on the response topic:

mosquitto_sub -t 'fleet/here/places/browse/response' &
mosquitto_pub -t 'fleet/here/places/browse' -m '{"apikey": "<apikey>", "at": "<at>", "params": "<params>"}'

Quick Start

Coreflux MQTT Broker

LoT Language

Coreflux HUB

VS Code - LoT Notebooks

Coreflux Portal

Using AI with Coreflux

Product Updates

Overview

Auth

Template parameters

Events

Deploy

Usage example

​Overview

​Auth

​Template parameters

​Events

​Deploy

​Usage example

​Related

Overview

Auth

Template parameters

Events

Deploy

Usage example

Related