Search & Places

Autosuggest, geocoding, nearby discovery, place details, and Mappls Pin addressing.

Resolve messy human intent into precise places. Search as a user types, convert addresses to coordinates, reverse coordinates into addresses, discover relevant POIs, inspect place details, search along a route, and use compact Mappls Pins instead of error-prone latitude and longitude pairs.

What you can build

Capabilities

Autosuggest and text searchProduction guidance, platform support, examples, and operational considerations included.01

Forward and reverse geocodingProduction guidance, platform support, examples, and operational considerations included.02

Nearby and route-corridor searchProduction guidance, platform support, examples, and operational considerations included.03

Place details and categoriesProduction guidance, platform support, examples, and operational considerations included.04

Address validation and standardizationProduction guidance, platform support, examples, and operational considerations included.05

Mappls Pin and DIGIPIN workflowsProduction guidance, platform support, examples, and operational considerations included.06

Choose your surface

Available platforms

Keep business identifiers and server-side policy portable; use the native surface where device integration or long-lived state matters.

REST Web Android iOS React Native Flutter Widgets

Authentication

Restricted static key (current) or OAuth bearer (legacy)

Current core REST uses a restricted static key in the documented access_token query contract. The pre-August-2025 line uses OAuth bearer with legacy hosts and paths. Never mix generations; keep server-use keys off untrusted clients and request logs.

Use separate projects for development, staging, and production.
Apply the narrowest domain, IP, platform, product, and resource scopes available.
Never ship a server secret in a browser bundle, mobile binary, prompt, or public repository.

Copy, run, understand

Quickstart

Replace placeholders with credentials from the developer console. Examples include the lifecycle and failure-handling context that short snippets usually omit.

Search & Places quickstart

import { createMapplsClientFromEnvironment } from "@mappls/server-sdk";

// MAPPLS_STATIC_KEY is applied using the current documented query contract.
// Keep the restricted key inside this trusted server process.
const mappls = createMapplsClientFromEnvironment();
const suggestions = await mappls.autosuggest({
  query: "coffee",
  region: "IND"
});

Before productionRestrict and rotate credentialsHandle timeouts and typed errorsAdd tracing without logging secretsTest quota and degraded-mode behavior

Production state machines

Operate the complete lifecycle

These blueprints name every state, actor, command, event, invariant, durable record, retry boundary, failure recovery, source contract, and operational signal.

stateful

Consented address verification

Normalize a declared service address, capture purpose-bound device evidence, apply an explainable versioned policy, require human review where evidence is weak, and retire precise data without erasing accountability.

Browse all stateful journey blueprints

Traceable documentation

Source repositories

Reference content is reconciled against these public and private source families. Version, authentication generation, and maturity are recorded before content is promoted.

mappls-rest-apisREST API · current →mappls-android-sdkSDK · current →mappls-ios-sdkSDK · current →mappls-web-pluginsWidget · current →

Browse all 49 related integration guides