Products
/
Spatial API
Proprietary Infrastructure

Location APIs
built and operated
by Placematic.

Geocoding, routing, spatial queries, and territory logic — delivered as REST APIs from Placematic's own infrastructure. Not a reseller. Not a wrapper. Built by us.

Book a demo
Start a Pilot
geocode.http
API · 38ms
GET /v1/geocode
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
// Request
GET /v1/geocode?q=1600+Golf+Rd,+Rolling+Meadows+IL
Authorization: "Bearer pm_live_••••"

// Response · 200 OK
{
  "query": "1600 Golf Rd, Rolling Meadows IL",
  "result": {
    "lat": 42.05863,
    "lng": -88.03112,
    "accuracy": "rooftop",
    "confidence": 0.98,
    "formatted_address": "1600 Golf Rd Ste 1200, Rolling Meadows, IL 60008"
  },
  "api_version": "2026-03-14",
  "response_time_ms": 38
}
Proprietary infrastructure — not a HERE reseller
REST API — JSON responses, full documentation
HERE Gold Partner since 2016
SLA-backed uptime
— / endpoints

What's in the Placematic Spatial API.

Six first-class endpoints covering geocoding, search, routing, and spatial logic. Every endpoint returns typed JSON and is versioned per calendar date.
GET
/v1/geocode

Geocoding

Convert addresses to coordinates with rooftop-level accuracy.
Supports batch geocoding up to 1,000 addresses per request
GET
/v1/reverse

Reverse Geocoding

Convert coordinates to structured address data.
Returns street, city, ZIP, county, and country components
GET
/v1/search

Address Search & Autocomplete

Real-time address suggestions as users type.
Optimized for US addresses with sub-100ms response times
POST
/v1/route

Routing

Single and multi-stop route optimization.
Supports time windows, vehicle profiles, and road restrictions
POST
/v1/pos-grids-for-geoposition

Territory Query

Point-in-polygon and zone assignment queries.
Assign any coordinate to a defined territory or service zone
POST
/v1/spatial/search

Spatial Search

Find locations within a radius or polygon boundary.
Returns ranked results with distance and bearing from origin
— / integration

Simple to integrate. Powerful in production.

A single POST to /v1/route returns an optimized multi-stop plan with per-waypoint ETAs. No SDK required.
POST/v1/route  ·  optimize: time · vehicle: van
200 OK · 84ms
Request application/json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
{
  "origin": {
    "lat": 41.5250,
    "lng": -88.0817
  },
  "destinations": [
    { "id": "stop_01", "lat": 41.8781, "lng": -87.6298 },
    { "id": "stop_02", "lat": 42.0451, "lng": -87.6877 },
    { "id": "stop_03", "lat": 42.0586, "lng": -88.0311 }
  ],
  "optimize": "time",
  "vehicle": "van",
  "time_window": "08:00-18:00",
  "restrictions": {
    "avoid_tolls": false,
    "max_weight_kg": 2400
  }
}
Response application/json · 200
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
{
  "status": "ok",
  "total_distance_km": 142.8,
  "total_duration_min": 186,
  "optimized_order": ["stop_01", "stop_02", "stop_03"],
  "waypoints": [
    { "sequence": 1, "id": "stop_01",
      "lat": 41.8781, "lng": -87.6298,
      "eta": "08:52" },
    { "sequence": 2, "id": "stop_02",
      "lat": 42.0451, "lng": -87.6877,
      "eta": "10:18" },
    { "sequence": 3, "id": "stop_03",
      "lat": 42.0586, "lng": -88.0311,
      "eta": "11:44" }
  ],
  "api_version": "2026-03-14",
  "response_time_ms": 84
}
● 200 OK  ·  region=us-east-1  ·  request_id=req_01HX8QZ4T2 api.placematic.com  ·  v2026-03-14
See full API Reference
— / performance

Built for production workloads.

P50 Latency

< 50ms

Median geocoding response time, US addresses.
Uptime SLA

99.9%

API uptime SLA for production accounts.
Batch Size

1,000

Max batch geocoding requests per call.
Integration

REST + JSON

No proprietary SDK required. Works with any HTTP client.
Six first-class endpoints covering geocoding, search, routing, and spatial logic. Every endpoint returns typed JSON and is versioned per calendar date.
— / who uses it

Who uses the Spatial API and how.

01 / Fleet & ELD

Fleet & ELD platforms

Embed geocoding and routing directly into your dispatch or tracking product.
CUSTOMER
GreenLight ELD · Joliet, IL — powering address resolution and route calculations across their fleet.
02 / Logistics

Logistics & delivery software

Validate delivery addresses at entry, calculate optimized routes for multi-stop drivers, and assign stops to service zones — all via a single API integration.
ENDPOINTS
/geocode · /route · /territory
03 / SaaS

SaaS products with location features

Add location search, address autocomplete, and territory logic to your product without building or maintaining location infrastructure.
ENDPOINTS
/search · /spatial/search · /territory
— / infrastructure

Our infrastructure.
Your reliability.

Placematic's Spatial API is built on our own spatial data infrastructure — not a pass-through to a third-party provider. We operate the API layer, manage data quality, handle versioning, and provide direct engineering support. When you integrate Placematic, you work with one team end-to-end.

Dedicated API infrastructure — not shared cloud commodity

HERE-powered data layers + Placematic proprietary data

Direct engineering support — no ticket queues

One contract, one SLA, one point of contact

— / related

Spatial API works best with:

UpGrid
Territory management

Use Spatial API territory queries to power zone assignment inside UpGrid's territory management interface.
Learn more

UpInsight
Geomarketing analytics

Feed geocoded location data and spatial search results into UpInsight's geomarketing analytics engine.
Learn more
HERE logo

HERE Platform
Partner data platform

Access HERE's routing, maps, and geocoding alongside Placematic's proprietary APIs — one contract, delivered together.
Learn more
— / questions

Frequently asked questions.

No. Placematic’s Spatial API is proprietary infrastructure built and operated by Placematic. Some endpoints use HERE as a data source alongside other providers, but the API itself — endpoints, response format, documentation, and SLA — is Placematic’s own product.

No. You integrate with Placematic directly. One contract, one set of credentials, one invoice. We handle all upstream data relationships.

Yes. We offer a structured pilot with API credentials scoped to your use case. Reach out and we’ll define the scope on the first call.

Spatial API is Placematic’s proprietary layer — geocoding, routing, territory queries, and spatial search built by us. HERE Platform via Placematic gives you access to HERE’s full suite of maps, routing, and data products under a single Placematic contract. Many clients use both.

Ready to integrate location intelligence into your product?

Talk to us about your use case. We'll scope API access together.

Book a Demo

API credentials available on first call. No commitment required.