> ## Documentation Index
> Fetch the complete documentation index at: https://docs.placematic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Placematic Developer Hub

> Implementation guidance for HERE Location Services — choosing APIs, forecasting costs, migrating from Google Maps, and shipping routing systems that survive production.

# HERE Location Services, implemented

Placematic is an official HERE reseller and Gold Partner. We issue production API keys, hold the contract, and write the guidance below from systems we have shipped since 2016.

Start with a request that returns `200`.

<CodeGroup>
  ```bash cURL theme={null}
  curl "https://router.hereapi.com/v8/routes" \
    -H "apiKey: $PLACEMATIC_KEY" \
    -G \
    --data-urlencode "transportMode=truck" \
    --data-urlencode "origin=42.0641,-88.0509" \
    --data-urlencode "destination=41.5250,-88.0817" \
    --data-urlencode "truck[height]=410" \
    --data-urlencode "truck[grossWeight]=35000" \
    --data-urlencode "return=summary"
  ```

  ```python Python theme={null}
  import os, requests

  resp = requests.get(
      "https://router.hereapi.com/v8/routes",
      headers={"apiKey": os.environ["PLACEMATIC_KEY"]},
      params={
          "transportMode": "truck",
          "origin": "42.0641,-88.0509",
          "destination": "41.5250,-88.0817",
          "truck[height]": 410,
          "truck[grossWeight]": 35000,
          "return": "summary",
      },
      timeout=10,
  )
  resp.raise_for_status()
  print(resp.json()["routes"][0]["sections"][0]["summary"])
  ```

  ```javascript Node.js theme={null}
  const params = new URLSearchParams({
    transportMode: "truck",
    origin: "42.0641,-88.0509",
    destination: "41.5250,-88.0817",
    "truck[height]": "410",
    "truck[grossWeight]": "35000",
    return: "summary",
  });

  const resp = await fetch(
    `https://router.hereapi.com/v8/routes?${params}`,
    { headers: { "apiKey": process.env.PLACEMATIC_KEY } }
  );
  if (!resp.ok) throw new Error(`HERE returned ${resp.status}`);
  console.log(await resp.json());
  ```
</CodeGroup>

<Info>
  No key yet? [Request one](https://placematic.com/start-trial/) — issued within one business day, no credit card, no demo call. Placematic USA LLC is the contracting party. You never open a HERE account.
</Info>

## Start here

<CardGroup cols={2}>
  <Card title="Getting Started" icon="play" href="/start-here/what-is-here-location-services">
    Platform overview, API keys, authentication, and how HERE pricing actually works.
  </Card>

  <Card title="Guides" icon="book-open" href="/guides">
    Truck routing, distance matrices, batch geocoding, and migrating off Google Maps.
  </Card>

  <Card title="Use Cases" icon="truck" href="/use-cases">
    Reference architectures for fleet and ELD platforms, delivery zones, and retail networks.
  </Card>

  <Card title="Comparisons" icon="scale-balanced" href="/comparisons">
    HERE against Google, TomTom, and Mapbox — including where they beat HERE.
  </Card>
</CardGroup>

## What this documentation covers

HERE maintains the parameter tables and response schemas. We link to them. What we write is the layer around the reference:

**Which API answers your question.** Routing, Distance Matrix, and Tour Planning look interchangeable and are not. Building a matrix from a loop of routing calls is the most expensive architectural mistake in this domain.

**What it will cost.** Per-1,000 rates are close across vendors. Your bill is set by call mix, volume tier, and whether you batched. We show you how to forecast it before you sign anything.

**How teams get it wrong.** `transportMode=truck` selects a routing engine. It does not supply your vehicle's dimensions. Omit them and HERE returns a route, without warning, that a 4.1m trailer cannot physically drive.

**When to use something else.** For consumer place discovery, business hours, and reviews, Google's data is better and you should keep it. Under roughly 10k calls a month, migration is a rounding error you will spend a quarter chasing.

## Featured guides

<CardGroup cols={2}>
  <Card title="Truck Routing" icon="truck" href="/guides/truck-routing">
    Physical constraints as first-class inputs — and the trap geometry that proves your integration applies them.
  </Card>

  <Card title="HERE Pricing Explained" icon="chart-line" href="/start-here/here-pricing-explained">
    Call volume versus asset-based pricing, and how to model a bill you can defend to finance.
  </Card>

  <Card title="Choosing the Right HERE APIs" icon="sitemap" href="/start-here/choosing-the-right-here-apis">
    A decision path by the question your system asks, not by product name.
  </Card>

  <Card title="Migrating from Google Maps" icon="arrow-right-arrow-left" href="/guides/google-migration">
    Endpoint mapping, sequencing, and validating route quality during cutover.
  </Card>
</CardGroup>

## Who builds on this

Placematic has been a HERE Gold Partner since 2016, deploying HERE into production routing engines, ELD platforms, and field operations tools.

Every page here comes from an integration we shipped, including the ones that went badly the first time.

## Need production keys?

Placematic helps engineering teams select the right HERE APIs, forecast usage, migrate from Google Maps, and reach production. One contract, one invoice, no direct HERE account.

<Card title="Request API keys" icon="key" href="https://placematic.com/start-trial/">
  One business day. No credit card. No demo call required.
</Card>