ZeeMaps REST API v1

Create and manage maps and markers, run geographic searches, and render map images — programmatically. The API is built for enterprise and integration customers and is the foundation the ZeeMaps MCP server is built on.

Base URL: https://api.zeemaps.com/v1
Auth: Authorization: Bearer <api_key> on every request
Format: JSON request and response bodies; RFC 3339 timestamps
Plan: API access requires the enterprise plan

Source of truth. The reference and guides are kept in sync with zeemaps-api-spec.yaml, the machine-readable OpenAPI spec — the reference is rebuilt from it whenever it changes, so it never drifts from the contract.

Start here

Quickstart →
Key to first call to your first markers in minutes. Authentication →
Bearer keys, scopes, the enterprise gate, and bootstrapping. API Reference →
Every endpoint, request, and response.

Guides

Quickstart — key → GET /v1/me → create a map → add markers.
Authentication & API keys — Bearer auth, read_only/read_write scopes, the enterprise-plan requirement and 402 PLAN_REQUIRED, requesting a key, and the help_url deep-link flow.
Errors — the { error: { code, message, help_url? } } envelope and the full status-code table.
Rate limits — per-key limits, the X-RateLimit-* headers, 429, and backoff.
Pagination — keyset next_page_token, page_size, and best-effort total_count.
Conventions — the owned-only model, units, and naming.
Recipes & how-tos — pins by coordinates or address, region and circle markers, categories and colors, the three bulk-import shapes, search, sharing, and lifecycle.
Versioning & changelog — what v1 guarantees and what has shipped.

Reference

The full, per-endpoint API reference is rendered directly from zeemaps-api-spec.yaml. Guides link into specific operations there for request and response detail.