{"count":714,"boundary":{"indexedFields":["title","description","eyebrow","keywords","canonical path"],"queryProcessing":"browser-local","queryLogging":false,"queryAnalytics":false,"providerCalls":0,"maximumQueryCharacters":160,"maximumRenderedResults":12},"entries":[{"id":"sdk-guide:api-client-studio","kind":"SDK & guide","title":"Mappls API Client Studio","description":"Download eight source-grounded contract-client packages with exact operation identities, generation metadata, fixture-first tests, checksums, and explicit live-transport qualification boundaries.","href":"/client-libraries","eyebrow":"8 languages · 1,296 exact bindings","keywords":"API client generated library TypeScript Python Java Kotlin C# Go PHP Ruby fixture checksum source fingerprint"},{"id":"solution:developer-experience-benchmark","kind":"Solution","title":"Mappls developer-experience benchmark","description":"Inspect the twenty repository-backed developer-experience criteria, current official Stripe, Google Maps, and Apple comparison patterns, exact proof metrics, and one explicit external sandbox gate.","href":"/benchmark","eyebrow":"20 evidenced criteria · official-source comparison","keywords":"developer experience benchmark scorecard Stripe Google Maps Apple Developer onboarding documentation sample code AI native sandbox trust evidence"},{"id":"solution:solution-architect","kind":"Solution","title":"Mappls solution architect","description":"Compose an evidence-bounded product, platform, contract, journey, tutorial, and runnable-app plan from a real industry scenario.","href":"/architect","eyebrow":"Interactive architecture planner","keywords":"capability explorer API picker industry platform stateless stateful build plan architecture"},{"id":"platform:product-platform-capability-matrix","kind":"Platform","title":"Mappls product × platform capability matrix","description":"Compare every Mappls product across every REST, web, native, hybrid, embedded, widget, deep-link, and MCP platform without inferring availability from adjacent evidence.","href":"/platforms/matrix","eyebrow":"130 exact decision records · honest not-listed cells","keywords":"product platform matrix compatibility availability support SDK API runtime REST Web Android iOS Flutter React Native Cordova Xamarin Linux Automotive Widgets Deep links MCP selection required"},{"id":"platform:capability-qualification-center","kind":"Platform","title":"Mappls Capability Qualification Center","description":"Turn any product-platform decision into a source lock, runtime and authentication choice, offline proof, non-production conformance plan, hostile-path suite, and independent release handoff.","href":"/platforms/qualify","eyebrow":"130 portable qualification journeys · 43 evidence-ready","keywords":"capability qualification conformance compatibility test entitlement source lock credential class fixture non-production hostile path stateful replay unknown outcome release evidence download JSON"},{"id":"platform:live-conformance-center","kind":"Platform","title":"Mappls Live Conformance Center","description":"Plan eight bounded non-production reads, keep credentials and provider bodies inside a trusted runner, inspect canonical reports locally, and prepare digest-bound release evidence.","href":"/conformance","eyebrow":"8 allowlisted reads · 10 product-family boundaries","keywords":"live conformance entitlement proof non-production read only report inspector SHA-256 release evidence search route matrix InTouch credential safe"},{"id":"solution:integration-manifests","kind":"Solution","title":"Mappls integration manifests","description":"Generate a portable, deterministic integration decision binding platform, products, authentication generations, exact source-fingerprinted operations, journeys, runnable proof, and release gates.","href":"/integration-manifests","eyebrow":"624 reviewable integration contracts · zero provider calls","keywords":"integration manifest lock file CI source fingerprint contract authentication generation platform journey reproducible download JSON"},{"id":"tutorial:developer-academy","kind":"Tutorial","title":"Mappls Developer Academy","description":"Build one progressive curriculum from industry outcome, exact platform, and entry experience through source evidence, code labs, hostile journeys, a tested capstone, and production acceptance.","href":"/academy","eyebrow":"624 personalized curricula · 21 capstones","keywords":"academy learning path curriculum beginner intermediate advanced training capstone tutorial industry platform production readiness no credential"},{"id":"platform:api-sandbox","kind":"Platform","title":"Mappls credential-free API sandbox","description":"Execute every normalized contract against deterministic success, empty, validation, authentication, rate-limit, and unavailable fixtures before connecting a live account.","href":"/sandbox","eyebrow":"162 contracts · 6 fixture scenarios","keywords":"sandbox mock fixture try it API success empty 401 429 503 no credential source example"},{"id":"api-generation:contract-generation-ledger","kind":"API generation","title":"Mappls API generation comparisons","description":"Compare exact retained InTouch and mGIS source generations, structural changes, compatibility signals, fingerprints, and application-owned migration checklists.","href":"/api-generations","eyebrow":"17 version transitions · no support inference","keywords":"API version contract generation migration compatibility breaking change OpenAPI source fingerprint InTouch mGIS"},{"id":"sdk-guide:sdk-directory","kind":"SDK & guide","title":"Mappls SDK and distribution center","description":"Compare every public SDK and binary distribution by platform, lifecycle, install evidence, source activity, migration risk, and local correspondence before selecting a package.","href":"/sdks","eyebrow":"58 source-backed records · 7 platforms","keywords":"SDK library package binary distribution compatibility install Android iOS Flutter React Native Web Cordova"},{"id":"platform:authentication-center","kind":"Platform","title":"Mappls authentication and credential center","description":"Choose, place, restrict, rotate, revoke, and troubleshoot the correct credential generation across trusted servers, browser, mobile, widgets, devices, enterprise surfaces, and MCP.","href":"/authentication","eyebrow":"14 paths · fail-closed placement advisor","keywords":"authentication credentials static key OAuth bearer public key origin package signing bundle rotation revocation MCP InTouch"},{"id":"platform:error-diagnostics-center","kind":"Platform","title":"Mappls errors and diagnostics center","description":"Classify failures by safe status, code, runtime, and operation safety; choose fix, retry, or reconciliation; and build a credential-safe support packet.","href":"/errors","eyebrow":"11 recovery classes · retry-safe classifier","keywords":"error diagnostics status request ID 401 403 409 429 500 503 504 retry timeout unknown outcome reconcile support"},{"id":"platform:webhook-receiver-guide","kind":"Platform","title":"Mappls Developer Console webhook receiver guide","description":"Verify signed raw bodies, prove destination ownership, deduplicate durable effects, preserve ordering, survive bounded retries, and operate independently approved replay.","href":"/webhooks","eyebrow":"4 signed topics · 4 receiver languages","keywords":"webhook HMAC SHA256 signature raw body challenge retry ordering deduplication idempotency replay TypeScript Python Java Go"},{"id":"platform:environment-readiness-center","kind":"Platform","title":"Mappls environments and deployment readiness","description":"Separate fixture, development, staging, and production identities; assess conditional release controls; and promote builds without copying credentials or state.","href":"/environments","eyebrow":"4 boundaries · 11 evidence controls","keywords":"environment fixture development staging production deployment promotion release rollback credential isolation stateful reconciliation"},{"id":"platform:agent-integration-center","kind":"Platform","title":"Mappls Agent Integration Center","description":"Design a purpose-bound Mappls AI application with an exact MCP allowlist, data and durable-state boundaries, human approval, hostile-path evaluations, operational controls, and release evidence.","href":"/ai/agents","eyebrow":"6 patterns · 12 controls · 8 evaluation dimensions","keywords":"AI agent MCP copilot tool allowlist human in the loop precise location operational state evaluation evals prompt injection data minimization kill switch release"},{"id":"platform:a2a-agent-server","kind":"Platform","title":"Mappls A2A agent server","description":"Discover and delegate three source-grounded offline skills or ten opt-in purpose-bound Mappls provider reads over Agent2Agent Protocol v1.0, with server-held credentials and zero writes.","href":"/ai/a2a","eyebrow":"A2A v1.0 · JSON-RPC + HTTP+JSON · 3 offline + 10 live reads","keywords":"A2A Agent2Agent agent card multi agent JSON-RPC HTTP JSON task lifecycle offline live read purpose solution plan capability journey simulation Search Routes InTouch"},{"id":"platform:build-with-mappls-agent-skill","kind":"Platform","title":"Build with Mappls Agent Skill","description":"Install a standards-compatible, offline-first skill that teaches AI coding agents to select exact Mappls capabilities, freeze a canonical manifest, implement stateless and stateful paths, and preserve entitlement and release authority.","href":"/ai/skills","eyebrow":"Agent Skills format · checksummed offline package","keywords":"Agent Skills SKILL.md Codex Claude AI coding agent offline integration manifest source grounded stateful MCP A2A download"},{"id":"platform:ai-integration-evaluation-lab","kind":"Platform","title":"Mappls AI Integration Evaluation Lab","description":"Run deterministic MCP, A2A, Agent Skill, stateful-journey, and hostile-boundary cases with path-level diagnostics and no provider call.","href":"/ai/evals","eyebrow":"90 cases · 918 assertions · offline runner","keywords":"AI evals evaluation benchmark MCP A2A Agent Skill stateful journey hostile prompt injection authority JSONL CI offline"},{"id":"platform:developer-cli","kind":"Platform","title":"Mappls Developer CLI","description":"Search the canonical catalog, create any of 13 source-bounded platform projects, and inspect credential and evidence gates without making a provider call.","href":"/cli","eyebrow":"Offline developer tool · 13 platform starters","keywords":"command line terminal CLI scaffold starter create doctor project audit JSON offline credential safe"},{"id":"platform:deep-link-handoff-lab","kind":"Platform","title":"Mappls deep-link handoff lab","description":"Build and validate source-documented place, navigation, point-on-map, and Pin links with native and browser fallback evidence.","href":"/tools/deep-links","eyebrow":"Zero-SDK integration tool","keywords":"deep link universal link app URI Mappls Pin navigation Kotlin Swift fallback"},{"id":"platform:widget-integration-lab","kind":"Platform","title":"Mappls widget integration lab","description":"Configure source-documented iframe widgets without accepting secrets, and select guarded enterprise or native integration tracks.","href":"/tools/widgets","eyebrow":"Credential-safe integration tool","keywords":"widget iframe Places Nearby EarthView RealView Metaverse mGIS native entitlement CSP"},{"id":"platform:add-a-place-contribution-guide","kind":"Platform","title":"Mappls Add a Place contribution guide","description":"Generate the corrected public iframe and operate reported submission, independent reconciliation, publication evidence, rejection, retry, and application-side withdrawal.","href":"/tools/widgets/add-a-place","eyebrow":"Credential-free embed · stateful host journey","keywords":"Add a Place contribution iframe publication moderation reconciliation Mappls Pin evidence withdrawal"},{"id":"platform:realview-inspection-guide","kind":"Platform","title":"Mappls RealView inspection guide","description":"Configure the paid Auth2 iframe boundary, exact-origin no-imagery adapter, ephemeral browser-token ownership, human observation, review, rework, and accessible fallback.","href":"/tools/widgets/realview","eyebrow":"Paid entitlement · governed visual inspection","keywords":"RealView panorama 360 Auth2 iframe status 204 inspection entitlement token coverage review"},{"id":"platform:offline-automotive-release-guide","kind":"Platform","title":"Mappls offline and automotive release control","description":"Operate runtime, map data, configuration, voice, target compatibility, activation, dual-slot update, qualification, interruption, rollback, and retirement as one governed release.","href":"/tools/automotive","eyebrow":"Entitled runtime · A/B release control","keywords":"offline automotive NaviMaps NCASE Telecons embedded A/B slots map package power loss rollback activation qualification"},{"id":"platform:skydnn-vision-evidence-guide","kind":"Platform","title":"Mappls SkyDNN vision evidence workflow","description":"Lock a discovered model to an immutable asset hash, validate synchronous inference geometry and confidence, review independently, and redact derived detections without persisting media or credentials.","href":"/tools/vision","eyebrow":"SkyDNN AI · governed inference evidence","keywords":"SkyDNN computer vision predict modelhub bounding box polygon polyline confidence image satellite review redaction human in the loop"},{"id":"platform:native-widget-matrix","kind":"Platform","title":"Mappls native widget implementation matrix","description":"Select a versioned Android, iOS, Flutter, or React Native widget path with explicit lifecycle, state ownership, release tests, and capability gaps.","href":"/tools/widgets/native","eyebrow":"20-path mobile implementation selector","keywords":"native widget Android iOS Flutter React Native place search nearby directions geofence feedback lifecycle state"},{"id":"platform:mgis-integration-planner","kind":"Platform","title":"Mappls mGIS integration planner","description":"Choose the entitled widget wrapper, twelve Web JS methods, durable dataset workspace, or separate sovereign MIGIST deployment with explicit state and evidence boundaries.","href":"/tools/mgis","eyebrow":"Enterprise geospatial contract selector","keywords":"mGIS MGIS.Widget dataset WMS style raster analysis workspace MIGIST sovereign air gap"},{"id":"source:repository-reconciliation","kind":"Source","title":"Mappls public and local repository reconciliation","description":"Inspect every public mappls-api repository against deterministic exact or normalized local candidates, including unmatched public and local-only evidence.","href":"/sources/reconciliation","eyebrow":"82 public repositories · identity-safe correspondence","keywords":"GitHub public repository local repository MMI Mappls MapmyIndia exact match normalized match unmatched local-only source evidence"},{"id":"source:documentation-coverage","kind":"Source","title":"Mappls documentation coverage","description":"Inspect required source-exact documentation, code, API/SDK selection, quickstart, tutorial, stateful journey, runnable app, and migration evidence across every source, product, and platform.","href":"/coverage","eyebrow":"105 coverage records · explicit required gaps","keywords":"documentation coverage completeness quality gap source exact adjacent evidence stateful journey quickstart tutorial sample app migration"},{"id":"platform:stateful-operations-planner","kind":"Platform","title":"Mappls stateful operations planner","description":"Select any journey-bearing product and generate its state-ownership boundary, aggregates, lifecycle evidence, eight implementation controls, runnable apps, and release gates.","href":"/tools/stateful","eyebrow":"9 product tracks · 17 complete state machines","keywords":"stateful hybrid application state provider state aggregate idempotency optimistic concurrency audit outbox reconciliation privacy recovery"},{"id":"platform:stateful-journey-lab","kind":"Platform","title":"Mappls Stateful Journey Lab","description":"Execute all eighteen application journeys through complete, idempotent replay, stale-version, invalid-transition, and unknown-outcome fixtures with immutable event and recovery evidence.","href":"/tools/journey-lab","eyebrow":"18 journeys · 90 deterministic fixture paths","keywords":"journey simulator state machine idempotency optimistic concurrency version conflict invalid transition unknown outcome reconciliation event outbox fixture no credential"},{"id":"product:maps","kind":"Product","title":"Maps","description":"Fast, expressive vector and raster maps across web, mobile, hybrid, and embedded apps.","href":"/docs/maps","eyebrow":"stateless · Core location","keywords":"maps Vector and raster basemaps Markers, shapes, layers, and overlays Traffic and thematic visualization Custom styles and camera controls Static and travelled-route images Offline and embedded map packages Web Android iOS React Native Flutter Cordova Xamarin REST mappls-web-maps-js mappls-android-sdk mappls-ios-sdk mappls-flutter-sdk mappls-react-native-sdk mappls-map-ios-distribution"},{"id":"product:search-places","kind":"Product","title":"Search & Places","description":"Autosuggest, geocoding, nearby discovery, place details, and Mappls Pin addressing.","href":"/docs/search-places","eyebrow":"stateless · Core location","keywords":"search-places Autosuggest and text search Forward and reverse geocoding Nearby and route-corridor search Place details and categories Address validation and standardization Mappls Pin and DIGIPIN workflows REST Web Android iOS React Native Flutter Widgets mappls-rest-apis mappls-android-sdk mappls-ios-sdk mappls-web-plugins"},{"id":"product:routes-navigation","kind":"Product","title":"Routes & Navigation","description":"Routes, matrices, optimization, map matching, predictive ETAs, and turn-by-turn navigation.","href":"/docs/routes-navigation","eyebrow":"hybrid · Mobility","keywords":"routes-navigation Multi-profile routing and alternatives Distance and time matrices Trip and vehicle-route optimization Map matching and snap-to-road Predictive routes and refreshed ETAs Online and offline turn-by-turn navigation REST Android iOS Automotive Linux React Native mappls-rest-apis mappls-android-sdk mappls-ios-sdk mapmyindia-navigation-sdk mappls-routenet mappls-telecons-offline-sdk"},{"id":"product:intouch-telematics","kind":"Product","title":"InTouch Telematics","description":"Live tracking, trips, devices, vehicles, events, geofences, and fleet intelligence.","href":"/docs/intouch-telematics","eyebrow":"stateful · Operations","keywords":"intouch-telematics Device and vehicle provisioning Live location and historical trails Trips, stoppages, and events Geofences, alerts, and notifications Driver behavior and fleet reports Mobile sensor-based tracking SDKs REST Android iOS React Native Web Widgets mappls-intouch-rest-apis mappls-intouch-android-sdk mappls-intouch-ios-sdk mappls-react-native-intouch-sdk"},{"id":"product:workmate","kind":"Product","title":"Workmate","description":"Workforce automation for people, clients, tasks, attendance, proof, and live operations.","href":"/docs/workmate","eyebrow":"stateful · Operations","keywords":"workmate Worker and team management Task assignment and dispatch Attendance and shift workflows Client visits and proof of service Live operations and exceptions Forms, evidence, and completion reports REST Android Web mapmyindia-workmate-apis mappls-workmate-android-sdk"},{"id":"product:gis-analytics","kind":"Product","title":"GIS & Analytics","description":"Spatial data, analysis, maps, dashboards, and embeddable location intelligence.","href":"/docs/gis-analytics","eyebrow":"hybrid · Intelligence","keywords":"gis-analytics Dataset upload and cataloguing Layer styling and thematic maps Spatial queries and analysis Dashboards and embedded insights Workspace roles and governed sharing Import, export, and lineage REST Web Widgets MCP mapmyindia-mgis-apis mapmyindia-mgis-libraries mappls-insight-sdk migist-complete"},{"id":"product:app-widgets-deep-links","kind":"Product","title":"App Widgets & Deep Links","description":"Embeddable Mappls experiences for places, directions, 3D views, RealView, and app hand-off.","href":"/docs/app-widgets-deep-links","eyebrow":"stateless · Experience","keywords":"app-widgets-deep-links Place and map visualization Directions and navigation hand-off Immersive 3D and RealView experiences Cross-platform universal links Low-code embeds Credential-free entry points Widgets Deep links Web Android iOS mappls-app-widgets mappls-web-plugins"},{"id":"product:offline-automotive","kind":"Product","title":"Offline & Automotive","description":"Offline maps, search, routing, guidance, compilers, and embedded navigation runtimes.","href":"/docs/offline-automotive","eyebrow":"stateful · Embedded","keywords":"offline-automotive Offline maps, search, and routing Turn-by-turn guidance runtime Regional data compilation Voice and traffic customization GPS health and dead reckoning hooks Signed data and software updates Automotive Linux Android mappls-telecons-offline-sdk mappls-telecons-compiler mappls-telecons-search-compiler mappls-telecons-background-compiler mappls-routenet linuxsdk-dev1 linuxsdk-dev2 yahaan"},{"id":"product:ai-location","kind":"Product","title":"AI & Location","description":"AI/ML APIs, vision, location-aware agents, ranking, and natural-language spatial workflows.","href":"/docs/ai-location","eyebrow":"hybrid · Intelligence","keywords":"ai-location Vision and imagery analysis Location-aware retrieval and ranking Natural-language map operations Typed tools for AI agents Spatial workflow orchestration Evaluation and grounding patterns REST Web MCP mappls-ai-apis skydnn-aiapi-docs genesis-toolkit mapplsaiwebtesting"},{"id":"product:capture-feedback","kind":"Product","title":"Capture & Feedback","description":"On-demand location capture, camera evidence, map feedback, and update workflows.","href":"/docs/capture-feedback","eyebrow":"hybrid · Data operations","keywords":"capture-feedback Single-shot and subscribed location Accuracy and timeout policies Camera and field evidence Map issue reporting Reviewable update workflows Battery-aware capture Android iOS mappls-camera-sdk-android mappls-camera-sdk-ios mappls-location-capture-android-sdk mappls-location-capture-ios-sdk mappls-feedback-kit-ios-distribution mappls-feedback-uikit-ios-distribution"},{"id":"platform:rest","kind":"Platform","title":"REST implementation","description":"Put Mappls behind a stable service boundary in any stack.","href":"/platforms/rest","eyebrow":"Platform playbook","keywords":"REST REST Credentials never reach a browser or mobile bundle Timeout, retry, and idempotency policies are explicit Coordinates, addresses, and identifiers have data-retention rules Every operation is attributable in logs and usage reporting"},{"id":"platform:web","kind":"Platform","title":"Web implementation","description":"Build expressive browser maps without surrendering performance or control.","href":"/platforms/web","eyebrow":"Platform playbook","keywords":"Web Web Origin restrictions include every deployed hostname Map lifecycle follows the framework lifecycle Large datasets are tiled, clustered, or progressively loaded Keyboard, touch, reduced-motion, and failure states are tested"},{"id":"platform:android","kind":"Platform","title":"Android implementation","description":"Compose native maps, places, tracking, and navigation with Android lifecycle discipline.","href":"/platforms/android","eyebrow":"Platform playbook","keywords":"Android Android Dependency versions are pinned and reproducible Location permission is contextual and revocable Background work complies with current Android policy SDK resources and observers are released deterministically"},{"id":"platform:ios","kind":"Platform","title":"iOS implementation","description":"Deliver Mappls-native Apple experiences through modular, lifecycle-safe frameworks.","href":"/platforms/ios","eyebrow":"Platform playbook","keywords":"iOS iOS Package and binary versions belong to the same release line Secrets are not recoverable from the app bundle Info.plist purpose strings match actual collection Delegates, observers, and background sessions terminate cleanly"},{"id":"platform:react-native","kind":"Platform","title":"React Native implementation","description":"Share product logic while keeping native Mappls capabilities honest on both platforms.","href":"/platforms/react-native","eyebrow":"Platform playbook","keywords":"React Native React Native Native and wrapper releases are compatible High-frequency events are throttled before crossing the bridge Unmount releases native views and listeners Platform-specific behavior is documented, not hidden"},{"id":"platform:flutter","kind":"Platform","title":"Flutter implementation","description":"Use one Dart experience with deliberate native Mappls configuration underneath.","href":"/platforms/flutter","eyebrow":"Platform playbook","keywords":"Flutter Flutter Android and iOS configuration is version-controlled Controllers are used only after readiness Streams and platform views are disposed Release builds are tested on physical devices"},{"id":"platform:cordova","kind":"Platform","title":"Cordova implementation","description":"Maintain hybrid location experiences with explicit native ownership and a migration path.","href":"/platforms/cordova","eyebrow":"Platform playbook","keywords":"Cordova Cordova/Ionic Supported status is verified before new development Toolchain and plugin versions are frozen Bridge inputs are validated and bounded A tested migration and rollback path exists"},{"id":"platform:xamarin","kind":"Platform","title":"Xamarin implementation","description":"Stabilize existing .NET mobile integrations and move forward without losing behavior.","href":"/platforms/xamarin","eyebrow":"Platform playbook","keywords":"Xamarin Xamarin/.NET The support and security posture is documented Build inputs can be reproduced Native resources have deterministic ownership Migration parity is measured with journey-level tests"},{"id":"platform:linux","kind":"Platform","title":"Linux implementation","description":"Run location and navigation reliably on controlled, embedded Linux systems.","href":"/platforms/linux","eyebrow":"Platform playbook","keywords":"Linux Linux/Embedded Runtime and data compatibility is enforced Device identity and activation can be rotated Updates are signed, resumable, and reversible Health and resource telemetry survive application restarts"},{"id":"platform:automotive","kind":"Platform","title":"Automotive implementation","description":"Treat in-vehicle navigation as a safety-aware, upgradeable system—not a screen.","href":"/platforms/automotive","eyebrow":"Platform playbook","keywords":"Automotive Automotive Linux/Embedded Driver-distraction and safety requirements are testable Navigation recovers after power and connectivity loss Runtime and map data roll out as a compatible unit Simulation and road-test evidence cover full journeys"},{"id":"platform:widgets","kind":"Platform","title":"Widgets implementation","description":"Embed complete Mappls experiences while keeping hand-off, privacy, and fallback deliberate.","href":"/platforms/widgets","eyebrow":"Platform playbook","keywords":"Widgets Widgets/Deep links Web Embedding and content-security policies permit only required origins No sensitive business state lives only inside the widget Loading, failure, and unsupported-browser fallbacks exist Analytics distinguish view, engagement, completion, and hand-off"},{"id":"platform:deep-links","kind":"Platform","title":"Deep links implementation","description":"Open useful Mappls place and journey experiences from any channel—with no SDK requirement.","href":"/platforms/deep-links","eyebrow":"Platform playbook","keywords":"Deep links Widgets/Deep links User or confidential data never appears in query parameters All variable values are encoded and length-bounded App and browser fallbacks reach the same intent Redirect and campaign domains are allow-listed and monitored"},{"id":"platform:mcp","kind":"Platform","title":"MCP implementation","description":"Give AI systems typed Mappls capabilities with policy, evidence, and human control.","href":"/platforms/mcp","eyebrow":"Platform playbook","keywords":"MCP AI/MCP Tools expose the least authority needed State-changing calls require explicit policy and approval Responses identify source, freshness, and uncertainty Every tool call is tenant-scoped, metered, redacted, and traceable"},{"id":"quickstart:rest-api","kind":"Quickstart","title":"Your first trusted Mappls request","description":"a validated autosuggest result from a credential-safe server boundary","href":"/quickstart/rest-api","eyebrow":"REST · 15 minutes · public-source","keywords":"Load the current restricted static key only inside the trusted process. Legacy OAuth and InTouch bearer credentials are separate generations and must never be mixed by inference. The public REST repository and normalized operation are repository evidence; the issued account remains authoritative for host, auth generation, quota, and region. Node.js 20 or newer A Mappls project and restricted non-production server key An approved region and one autosuggest test query Request logging configured to omit URLs containing key query parameters mappls-rest-apis The successful response retains a Mappls place identity and the failure response is typed and redacted. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. A request succeeds locally but its key appears in proxy traces The current key uses a query transport and an intermediary records full URLs. Disable query-string logging, restrict the key to server egress, redact telemetry, and rotate any exposed credential before continuing. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:web-map","kind":"Quickstart","title":"Render one accessible web map","description":"a responsive map and text-synchronized selected place","href":"/quickstart/web-map","eyebrow":"Web · 15 minutes · public-source","keywords":"Use only the browser-supported public key restricted to exact origins. Privileged REST credentials stay on a backend-for-frontend. The selected Web Maps source contains current and sample evidence; confirm the script/package line and allowed origin against the target project. A static HTML or framework application An exact localhost origin A domain-restricted browser key A visible fallback container and selected-place text region mappls-web-maps mappls-web-maps-js Map, text fallback, and selected identity stay synchronized at mobile and desktop widths. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. The map is blank while no provider error is visible The host has zero height, the script was blocked, the origin is not allowed, or initialization ran before the DOM existed. Inspect host dimensions and script/network status, surface the load error beside the text fallback, and initialize exactly once after mount. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:android-native","kind":"Quickstart","title":"Create a lifecycle-safe Android map","description":"a native map screen that survives recreation and permission denial","href":"/quickstart/android-native","eyebrow":"Android · 25 minutes · public-source","keywords":"Use only the documented Android credential configuration restricted to the package and signing identity. Server credentials never belong in the APK. The public repositories are sample-classified evidence; confirm Maven coordinates, BoM, AGP/Kotlin, min/target SDK, and supported release with Mappls. Android Studio and a clean Kotlin app Confirmed AGP, Kotlin, minSdk, and targetSdk matrix A package/signature-restricted non-production key At least one physical device for release validation mappls-android-sdk mappls-android-compose-demo Camera/selection state restores intentionally and no map listener or location request survives the owning lifecycle. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. Debug works but release crashes or renders nothing Repository, dependency, shrinker, manifest, signing restriction, architecture, or resource configuration differs in release. Resolve the release dependency graph, inspect merged manifest/resources, verify signing identity and restrictions, and test the smallest release screen on hardware. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:ios-native","kind":"Quickstart","title":"Create a lifecycle-safe iOS map","description":"a native Swift map feature with explicit package and view ownership","href":"/quickstart/ios-native","eyebrow":"iOS · 25 minutes · public-source","keywords":"Use only the documented app credential restricted to the bundle/team context. Keep server secrets and privileged exchanges outside the application bundle. Public distribution repositories identify candidate package lines, not a universal version matrix. Confirm SwiftPM products, binary checksums, Xcode/Swift, deployment target, and extension compatibility together. A clean Swift application Confirmed Xcode, Swift, deployment target, and package line A bundle-restricted non-production app credential An iPhone or iPad for release and lifecycle tests mappls-map-ios-distribution mappls-api-kit-ios-distribution The selected place survives intended scene restoration and released views retain no delegates, observers, tasks, or background sessions. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. SwiftPM resolves but archive or launch fails Package/binary release lines, deployment target, architecture, privacy manifest, or dependent extensions are incompatible. Inspect Package.resolved and archive linkage, verify checksums and platform slices, then confirm the complete package matrix with the owning product guide. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:react-native-map","kind":"Quickstart","title":"Bridge one map feature across Android and iOS","description":"a typed shared map feature with separately verified native halves","href":"/quickstart/react-native-map","eyebrow":"React Native · 30 minutes · public-source","keywords":"Configure Android and iOS app credentials independently and keep privileged calls on a backend. JavaScript configuration is not a secret store. The public wrapper is sample-classified. Confirm React Native, wrapper, New Architecture status, Gradle/Kotlin, Xcode/Swift, and underlying native Mappls versions as one release unit. A clean React Native TypeScript app Approved wrapper/native version matrix Separate restricted Android and iOS app credentials Physical Android and iOS devices mappls-react-native-sdk Android and iOS return the same application-level selected ID while platform-specific failures remain visible and attributable. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. One platform works while the other reports missing native view/module Only one native project, dependency graph, architecture mode, autolinking step, credential restriction, or build cache is correct. Treat each platform as its own build: inspect resolved native dependencies and registration, clean only scoped build output, and prove the native example before the shared wrapper. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:flutter-map","kind":"Quickstart","title":"Build a native-backed Flutter place picker","description":"a Dart form that commits one accepted Mappls place identity","href":"/quickstart/flutter-map","eyebrow":"Flutter · 30 minutes · public-source","keywords":"Configure separately restricted Android and iOS app credentials in their native projects. Do not put server secrets in Dart assets or compile-time constants. The corpus contains Mappls sample evidence and an older current-classified MapmyIndia wrapper. Confirm the supported Flutter/Dart plugin and both native SDK lines before choosing one. A clean Flutter application Confirmed Flutter, Dart, plugin, Android, and iOS matrix Restricted credentials for both native runners Physical devices and release signing mappls-flutter-sdk flutter-mapmyindia-gl The form cannot submit stale text as a selected place and platform views/controllers are disposed after navigation. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. The Dart API resolves but the platform view fails at runtime Android/iOS native configuration, plugin/native version, renderer, architecture, permission, or credential setup is incomplete. Run the plugin's minimal native-backed screen on each platform, inspect native logs and dependency graphs, and wait for controller readiness before commands. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:cordova-maintenance","kind":"Quickstart","title":"Stabilize a Cordova map before migration","description":"a reproducible legacy screen behind a replaceable capability facade","href":"/quickstart/cordova-maintenance","eyebrow":"Cordova · 35 minutes · legacy-maintenance","keywords":"Treat all client credentials as platform-restricted public credentials and keep privileged REST work on a backend. Never reuse legacy auth with a current host by resemblance. Only legacy/beta Cordova sources exist in the public corpus. This quickstart is for stabilizing an existing estate—not recommending Cordova for new development. Use the migration track to select a supported target. An existing Cordova/Ionic repository A reproducible lockfile and build-host image Inventory of plugins, native SDKs, credentials, signing, and store constraints A chosen migration owner and target decision date mapmyindia-map-cordova-ionic-beta mapmyindia-restapi-cordova-ionic-beta One legacy journey is reproducible, has a fallback, and can switch to a replacement adapter without changing domain state. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. A fresh machine cannot reproduce the signed build Unpinned Node/Cordova/plugin/native build inputs, removed repositories, certificates, or generated native edits are part of the hidden build. Capture the entire toolchain manifest and generated-project changes before feature work; if dependencies are unavailable, prioritize the migration seam and replacement cohort. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:xamarin-maintenance","kind":"Quickstart","title":"Extract a Xamarin map integration for replacement","description":"a shared .NET contract with independently owned Android and iOS adapters","href":"/quickstart/xamarin-maintenance","eyebrow":"Xamarin · 40 minutes · entitlement-required","keywords":"Use separately restricted native app credentials and keep privileged service credentials on a backend. Do not move secrets into shared assemblies during extraction. No public repository in the snapshot provides a current Xamarin successor. Obtain the existing binding/source and target-platform contract from Mappls and use the migration principles before implementation. An existing Xamarin solution and reproducible build host Inventory of NuGet packages, native bindings, binaries, and licenses Android and iOS journey fixtures A confirmed supported migration target Shared tests prove equivalent place identity and errors while no shared state retains a native view, context, delegate, or credential. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. Shared tests pass but a platform leaks or crashes after navigation Renderer/delegate/event ownership remains implicit or native callbacks target a disposed shared object. Trace creation, subscription, disappearance, disposal, and late callbacks per platform; introduce cancellation/version fencing at the adapter boundary. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:linux-embedded","kind":"Quickstart","title":"Boot a supervised embedded map client","description":"a health-checked native process with an atomic data/runtime boundary","href":"/quickstart/linux-embedded","eyebrow":"Linux · 45 minutes · entitlement-required","keywords":"Use device/workload identity and entitlement delivered through the approved provisioning channel; never bake fleet-wide secrets into an image or package. The public snapshot has no platform-specific Linux distribution guide. The runtime, ABI, compiler, graphics, activation, and data contract must come from the entitled private distribution. Target CPU, ABI, libc, GPU/graphics, OS image, storage, and sensor manifest Entitled runtime, data, license, and activation contract A supervised service environment Dual-slot storage or another atomic rollback mechanism Every test leaves exactly one bootable active runtime/data set and health reports the selected versions without leaking device credentials. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. The process starts but rendering or routing fails on target hardware ABI/libc/compiler/GPU/runtime/data epoch or activation is incompatible despite a successful file copy. Compare the signed release manifest to device facts, fail readiness, retain the previous slot, and obtain the exact compatibility decision from the runtime owner. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:automotive-navigation","kind":"Quickstart","title":"Simulate one recoverable navigation session","description":"a safety-aware route-to-arrival state machine over an entitled runtime","href":"/quickstart/automotive-navigation","eyebrow":"Automotive · 60 minutes · entitlement-required","keywords":"Provision per-device identity, activation, regions, runtime, and map data through the approved vehicle/fleet control plane. Avoid shared embedded credentials. The public snapshot does not establish an automotive SDK or safety contract. Obtain the entitled runtime, data, activation, vehicle-interface, HMI, and regulatory requirements before binding an adapter. Vehicle hardware/OS/display/control/sensor operating envelope Entitled runtime, map data, activation, and update contract Deterministic GNSS and vehicle-signal simulator Safety, distraction, privacy, and release owners The session recovers to a safe explainable state with compatible runtime/data and never presents stale guidance as current after a reset. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. Guidance resumes with an old route or unsafe prompt after restart Route/session version, position freshness, vehicle state, HMI policy, or runtime/data identity was not persisted and reconciled atomically. Fail guidance to a safe state, reconcile session and release manifest, replay the deterministic trace, and require simulation evidence before road testing. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:widgets-place","kind":"Quickstart","title":"Embed a place journey with an owned fallback","description":"an accessible host that validates one widget result and survives widget failure","href":"/quickstart/widgets-place","eyebrow":"Widgets · 20 minutes · public-source","keywords":"Use only the widget/browser credential class restricted to exact origins. Validate every postMessage/callback payload and keep privileged operations on the server. The current public Web Plugins guide spans current vector and legacy raster integration branches; source activity is not a support promise. Confirm the exact widget, script, origin, event schema, release, entitlement, and authentication line before implementation. A confirmed Mappls widget and auth generation Exact host and allowed widget origins An accessible host form and manual fallback A versioned callback/message schema mappls-web-plugins The host submits only a validated selected identity and remains usable when the widget is slow, blocked, denied, or unavailable. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. The widget displays but selection never reaches the form Origin, callback name, event schema/version, load timing, or host state invalidation differs from the confirmed integration line. Log only safe message metadata, verify exact origin/schema from the guide, reject unknown shapes, and keep the visible fallback active. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:deep-links","kind":"Quickstart","title":"Ship one zero-SDK Mappls hand-off","description":"a place link that reaches the same intent across app and browser fallbacks","href":"/quickstart/deep-links","eyebrow":"Deep links · 10 minutes · public-source","keywords":"Deep links contain no credential. Put only bounded non-sensitive intent in the URL; precise private/user data and server secrets must never become query parameters. Use the exact link shape documented by the current App Widgets source. The scaffold below deliberately receives that approved base rather than inventing an undocumented path. A stable Mappls place identity or validated destination The exact documented link template Installed/uninstalled Android and iOS test devices Browser, messaging, email, and QR test channels mappls-app-widgets Every supported channel reaches the same destination intent or a useful visible fallback without sensitive query data. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. A channel opens a generic page or different destination The association, link shape, encoding, redirector, app installation state, or channel rewriting altered the documented intent. Compare the final URL components without private data, bypass unapproved redirectors, and retest installed/uninstalled fallback against the exact guide. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"quickstart:mcp-agent","kind":"Quickstart","title":"Connect a read-only Mappls agent","description":"a grounded documentation query through local stdio or authenticated stateless HTTP","href":"/quickstart/mcp-agent","eyebrow":"MCP · 15 minutes · local-reference","keywords":"Keep provider credentials in the MCP server process or approved secret provider, never model context or client configuration committed to source. A remote internal gateway bearer or issuer-bound OAuth access token is independent from every Mappls provider credential. Documentation and migration tools require no live credential. The MCP implementation is maintained in this repository and protocol-tested over stdio and Streamable HTTP. Live tool success still depends on the issued account, operation, region, and credential scope; production OAuth authorization-server registration, consent, lifecycle, and revocation remain company integrations. Node.js 22 or newer An MCP-capable client or the downloadable Spatial Operations Agent A built `@mappls/mcp-server` package No credential for offline discovery; separately scoped non-production credentials only for approved live reads Fixture, real stdio, and remote HTTP share one governed application client contract. Local stdio and an explicit live-read deployment advertise 42 typed tools; default remote HTTP advertises only the 32 credential-free tools. Both profiles retain 38 resources and two prompts, OAuth mode binds an attributable principal/client/scope to the exact resource, remote HTTP retains no session registry, and no profile exposes writes. A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result. No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts. Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends. The client starts but lists no tools/resources, or a planned tool is unavailable The package was not built, the stdio path/runtime or remote URL/auth is wrong, the configured profile is offline while the plan needs live-read, JWT issuer/audience/scope is mismatched, stdout contains non-protocol output, or a host/origin allowlist rejected the client. Run the package build and protocol test directly, use solution_research and mappls_get_authentication_path to prove offline negotiation and credential placement, check credential-free health and protected-resource metadata, inspect only safe token classification, verify the absolute local entrypoint or exact HTTPS resource identity, then reconnect with the smallest profile. Authentication or entitlement is rejected The credential class, restriction, account region, host/path generation, package application, or subscribed capability does not match. Do not try another credential shape blindly. Capture the safe status/request identity and reconcile the exact contract in the developer console or support packet. The sample works once but not after reload, backgrounding, or a second run Lifecycle ownership, listener disposal, token/session refresh, saved state, or a singleton initialization boundary is incomplete. Instrument create/ready/cancel/destroy transitions and prove one owner before adding product behavior."},{"id":"source-launchpad:github","kind":"Source launchpad","title":"Mappls API Organization Guide: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/github","eyebrow":".github · stateless · source-ready","keywords":"Guide Unspecified maps The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 862c91224d2b3e3fd8d3bed8. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. This source does not establish a complete credential contract. Keep the adapter credential-free until the developer application, runtime, restriction, entitlement, and current authentication generation are approved. The exact source guide `github` and fingerprint `862c91224d2b3e3fd8d3bed8` recorded in the project A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mapmyindia-angular-sample-websdk-rest","kind":"Source launchpad","title":"Angular Sample for MapmyIndia Interactive Maps JS SDK & MapmyIndia RESTful APIs for Web: source launchpad","description":"Run one reviewed sample seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mapmyindia-angular-sample-websdk-rest","eyebrow":"mapmyindia-angular-sample-webSDK-REST · stateless · sample-learning","keywords":"Sample Web REST maps search-places identity-platform This is sample-classified evidence and proves a learning path, not a universally supported production release. The immutable evidence key is 4280593e3c2f3278656e1952. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mapmyindia-angular-sample-websdk-rest` and fingerprint `4280593e3c2f3278656e1952` recorded in the project A browser application and an allowed development origin A trusted backend or API client capable of HTTPS requests OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A reviewed, credential-free source example starting with “2. Create file name of proxy.conf.json in your project and put given c” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mapmyindia-purejs-sample-websdk-rest","kind":"Source launchpad","title":"MapmyIndia Interactive Maps JS SDK & MapmyIndia RESTful APIs for Web in Pure JS: source launchpad","description":"Run one reviewed sample seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mapmyindia-purejs-sample-websdk-rest","eyebrow":"mapmyindia-pureJS-sample-webSDK-REST · stateless · sample-learning","keywords":"Sample Web REST maps search-places routes-navigation tracking-telematics identity-platform This is sample-classified evidence and proves a learning path, not a universally supported production release. The immutable evidence key is 7648d47274423632e0d612ff. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mapmyindia-purejs-sample-websdk-rest` and fingerprint `7648d47274423632e0d612ff` recorded in the project A browser application and an allowed development origin A trusted backend or API client capable of HTTPS requests OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A reviewed, credential-free source example starting with “Creating project in Pure Javascript for MapmyIndia REST APIs & Interac” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-ai-apis","kind":"Source launchpad","title":"MAPPLS AI / ML APIs: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-ai-apis","eyebrow":"mappls-ai-apis · stateless · source-ready","keywords":"REST API REST AI/MCP maps search-places workforce gis-analytics ai-vision capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 80cfbc9b9c7ce4b4590d05e1. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-ai-apis` and fingerprint `80cfbc9b9c7ce4b4590d05e1` recorded in the project A trusted backend or API client capable of HTTPS requests The corresponding product entitlement enabled for the developer application A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-android-compose-demo","kind":"Source launchpad","title":"Mappls Vector Map Android SDK JetPack Compose: source launchpad","description":"Run one reviewed sample seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-android-compose-demo","eyebrow":"mappls-android-compose-demo · stateless · sample-learning","keywords":"Sample Android maps search-places routes-navigation gis-analytics widgets-deep-links capture-feedback This is sample-classified evidence and proves a learning path, not a universally supported production release. The immutable evidence key is 37562302b0fcd2d2115c705f. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-android-compose-demo` and fingerprint `37562302b0fcd2d2115c705f` recorded in the project An Android project with a supported Gradle and Kotlin or Java toolchain OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A reviewed, credential-free source example starting with “Setup your project” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-android-sdk","kind":"Source launchpad","title":"Mappls Android SDK: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-android-sdk","eyebrow":"mappls-android-sdk · stateless · source-ready","keywords":"SDK Android maps search-places routes-navigation tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 2ccc51932d1b333b3561336c. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-android-sdk` and fingerprint `2ccc51932d1b333b3561336c` recorded in the project An Android project with a supported Gradle and Kotlin or Java toolchain OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-annotation-extension-ios-distribution","kind":"Source launchpad","title":"Mappls Annotation Extension for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-annotation-extension-ios-distribution","eyebrow":"mappls-annotation-extension-ios-distribution · stateless · binary-review","keywords":"Distribution iOS maps search-places tracking-telematics capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is dcb2a91e8716dd659728ce45. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-annotation-extension-ios-distribution` and fingerprint `dcb2a91e8716dd659728ce45` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Circles (MGLCircleStyleAnnotation)” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-annotation-extension-ios-distribution-base","kind":"Source launchpad","title":"Mappls Annotation Extension for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-annotation-extension-ios-distribution-base","eyebrow":"mappls-annotation-extension-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS maps search-places tracking-telematics capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is dcb2a91e8716dd659728ce45. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-annotation-extension-ios-distribution-base` and fingerprint `dcb2a91e8716dd659728ce45` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Circles (MGLCircleStyleAnnotation)” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-api-core-ios-distribution","kind":"Source launchpad","title":"[MapplsAPICore](): source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-api-core-ios-distribution","eyebrow":"mappls-api-core-ios-distribution · stateless · binary-review","keywords":"Distribution iOS routes-navigation tracking-telematics capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is 32bdcb00147ba07812b6903e. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-api-core-ios-distribution` and fingerprint `32bdcb00147ba07812b6903e` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-api-kit-ios-distribution","kind":"Source launchpad","title":"[MapplsAPIKit (REST API Kit for iOS)](): source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-api-kit-ios-distribution","eyebrow":"mappls-api-kit-ios-distribution · stateless · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics workforce gis-analytics capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is 8067ef763bd59da11448365f. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-api-kit-ios-distribution` and fingerprint `8067ef763bd59da11448365f` recorded in the project An iOS project with Xcode and the package manager required by the source release OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Objective C” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-api-kit-ios-distribution-base","kind":"Source launchpad","title":"[MapplsAPIKit (REST API Kit for iOS)](): source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-api-kit-ios-distribution-base","eyebrow":"mappls-api-kit-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics workforce capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is fef99dda42ad1a82220474a2. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-api-kit-ios-distribution-base` and fingerprint `fef99dda42ad1a82220474a2` recorded in the project An iOS project with Xcode and the package manager required by the source release OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Objective C” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-app-widgets","kind":"Source launchpad","title":"Mappls App Widgets: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-app-widgets","eyebrow":"mappls-app-widgets · stateless · source-ready","keywords":"Deep link Widgets/Deep links search-places widgets-deep-links The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 1cb282714a115237fb8e116d. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. This source does not establish a complete credential contract. Keep the adapter credential-free until the developer application, runtime, restriction, entitlement, and current authentication generation are approved. The exact source guide `mappls-app-widgets` and fingerprint `1cb282714a115237fb8e116d` recorded in the project A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-camera-ios-distribution","kind":"Source launchpad","title":"MapplsCamera SDK for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-camera-ios-distribution","eyebrow":"mappls-camera-ios-distribution · stateless · binary-review","keywords":"Distribution iOS maps search-places tracking-telematics offline-automotive capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is 5188dcc0949df5e35f014373. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Use only the public application credential class documented for the exact package, origin, bundle, or signing identity. Privileged server credentials remain outside the client. The exact source guide `mappls-camera-ios-distribution` and fingerprint `5188dcc0949df5e35f014373` recorded in the project An iOS project with Xcode and the package manager required by the source release A Mappls project key restricted to the intended app, domain, or backend The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Swift Package Manager” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-camera-sdk-android","kind":"Source launchpad","title":"Mappls Camera SDK: source launchpad","description":"Run one reviewed sdk seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-camera-sdk-android","eyebrow":"mappls-camera-sdk-android · stateless · source-ready","keywords":"SDK Android maps search-places tracking-telematics workforce widgets-deep-links offline-automotive capture-feedback The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 7840f9c22c6b19e5eafd7e97. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Use only the public application credential class documented for the exact package, origin, bundle, or signing identity. Privileged server credentials remain outside the client. The exact source guide `mappls-camera-sdk-android` and fingerprint `7840f9c22c6b19e5eafd7e97` recorded in the project An Android project with a supported Gradle and Kotlin or Java toolchain A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A reviewed, credential-free source example starting with “Kotlin (build.gradle.kts)” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-camera-sdk-ios","kind":"Source launchpad","title":"MapplsCamera SDK for iOS: source launchpad","description":"Run one reviewed sdk seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-camera-sdk-ios","eyebrow":"mappls-camera-sdk-ios · stateless · source-ready","keywords":"SDK iOS maps search-places tracking-telematics offline-automotive capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is be2f3bb17147aef1890e71e5. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Use only the public application credential class documented for the exact package, origin, bundle, or signing identity. Privileged server credentials remain outside the client. The exact source guide `mappls-camera-sdk-ios` and fingerprint `be2f3bb17147aef1890e71e5` recorded in the project An iOS project with Xcode and the package manager required by the source release A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A reviewed, credential-free source example starting with “Swift Package Manager” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-direction-ui-ios-distribution","kind":"Source launchpad","title":"MapplsDirectionUI for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-direction-ui-ios-distribution","eyebrow":"mappls-direction-ui-ios-distribution · hybrid · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is c8594d45a1d168c0c9d4df60. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-direction-ui-ios-distribution` and fingerprint `c8594d45a1d168c0c9d4df60` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “MapplsDirectionsViewController” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-direction-ui-ios-distribution-base","kind":"Source launchpad","title":"MapplsDirectionUI for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-direction-ui-ios-distribution-base","eyebrow":"mappls-direction-ui-ios-distribution-base · hybrid · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is c8594d45a1d168c0c9d4df60. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-direction-ui-ios-distribution-base` and fingerprint `c8594d45a1d168c0c9d4df60` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “MapplsDirectionsViewController” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-drivingrange-plugin-ios-distribution","kind":"Source launchpad","title":"MapplsDrivingRangePlugin for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-drivingrange-plugin-ios-distribution","eyebrow":"mappls-drivingrange-plugin-ios-distribution · stateless · binary-review","keywords":"Distribution iOS maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is ab30151929b38a436eb0bfee. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-drivingrange-plugin-ios-distribution` and fingerprint `ab30151929b38a436eb0bfee` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “MapplsDrivingRangePlugin” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-drivingrange-plugin-ios-distribution-base","kind":"Source launchpad","title":"MapplsDrivingRangePlugin for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-drivingrange-plugin-ios-distribution-base","eyebrow":"mappls-drivingrange-plugin-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is d45431cb565d97f838db4aef. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-drivingrange-plugin-ios-distribution-base` and fingerprint `d45431cb565d97f838db4aef` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “MapplsDrivingRangePlugin” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-feedback-kit-ios-distribution","kind":"Source launchpad","title":"MapplsFeedbackKit for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-feedback-kit-ios-distribution","eyebrow":"mappls-feedback-kit-ios-distribution · hybrid · binary-review","keywords":"Distribution iOS search-places tracking-telematics widgets-deep-links offline-automotive capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is 505b2357a59292ab056a8375. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-feedback-kit-ios-distribution` and fingerprint `505b2357a59292ab056a8375` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Get Report Categories” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-feedback-kit-ios-distribution-base","kind":"Source launchpad","title":"MapplsFeedbackKit for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-feedback-kit-ios-distribution-base","eyebrow":"mappls-feedback-kit-ios-distribution-base · hybrid · binary-review","keywords":"Distribution iOS search-places tracking-telematics widgets-deep-links offline-automotive capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is 505b2357a59292ab056a8375. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-feedback-kit-ios-distribution-base` and fingerprint `505b2357a59292ab056a8375` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Get Report Categories” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-feedback-uikit-ios-distribution","kind":"Source launchpad","title":"MapplsFeedbackUIKit for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-feedback-uikit-ios-distribution","eyebrow":"mappls-feedback-uikit-ios-distribution · hybrid · binary-review","keywords":"Distribution iOS maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is ce9bd0f45c46db6da97d67b3. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-feedback-uikit-ios-distribution` and fingerprint `ce9bd0f45c46db6da97d67b3` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Present Navigation Controller” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-feedback-uikit-ios-distribution-base","kind":"Source launchpad","title":"MapplsFeedbackUIKit for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-feedback-uikit-ios-distribution-base","eyebrow":"mappls-feedback-uikit-ios-distribution-base · hybrid · binary-review","keywords":"Distribution iOS maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is ce9bd0f45c46db6da97d67b3. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-feedback-uikit-ios-distribution-base` and fingerprint `ce9bd0f45c46db6da97d67b3` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Present Navigation Controller” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-flutter-sdk","kind":"Source launchpad","title":"Mappls Flutter SDK: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-flutter-sdk","eyebrow":"mappls-flutter-sdk · stateless · source-ready","keywords":"SDK Flutter maps search-places routes-navigation tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 512ead785542761a9bff4f58. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-flutter-sdk` and fingerprint `512ead785542761a9bff4f58` recorded in the project A Flutter project with Android and iOS platform configuration OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-geoanalytics-ios-distribution","kind":"Source launchpad","title":"MapplsGeoanalytics Plugin for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-geoanalytics-ios-distribution","eyebrow":"mappls-geoanalytics-ios-distribution · stateless · binary-review","keywords":"Distribution iOS maps search-places tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is b68a2b4329dc3c4db762969b. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-geoanalytics-ios-distribution` and fingerprint `b68a2b4329dc3c4db762969b` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Initialization MapplsGeoanalyticsPlugin” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-geoanalytics-ios-distribution-base","kind":"Source launchpad","title":"MapplsGeoanalytics Plugin for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-geoanalytics-ios-distribution-base","eyebrow":"mappls-geoanalytics-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS maps search-places tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is b68a2b4329dc3c4db762969b. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-geoanalytics-ios-distribution-base` and fingerprint `b68a2b4329dc3c4db762969b` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Initialization MapplsGeoanalyticsPlugin” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-geofence-ui-ios-distribution","kind":"Source launchpad","title":"MapplsGeofenceUI Plugin for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-geofence-ui-ios-distribution","eyebrow":"mappls-geofence-ui-ios-distribution · hybrid · binary-review","keywords":"Distribution iOS maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is dc9ee3cb13b907b481c65810. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-geofence-ui-ios-distribution` and fingerprint `dc9ee3cb13b907b481c65810` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Step 3 :- Initialization of GeofenceViewUI” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-geofence-ui-ios-distribution-base","kind":"Source launchpad","title":"MapplsGeofenceUI Plugin for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-geofence-ui-ios-distribution-base","eyebrow":"mappls-geofence-ui-ios-distribution-base · hybrid · binary-review","keywords":"Distribution iOS maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is dc9ee3cb13b907b481c65810. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-geofence-ui-ios-distribution-base` and fingerprint `dc9ee3cb13b907b481c65810` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Step 3 :- Initialization of GeofenceViewUI” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-insight-sdk","kind":"Source launchpad","title":"Mappls Insight Embeddable Visualizations: source launchpad","description":"Run one reviewed sdk seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-insight-sdk","eyebrow":"mappls-insight-sdk · stateless · source-ready","keywords":"SDK Web gis-analytics offline-automotive capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 0ae2cda7c0a988f9a2be664e. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-insight-sdk` and fingerprint `0ae2cda7c0a988f9a2be664e` recorded in the project A browser application and an allowed development origin OAuth client credentials issued for the intended Mappls project A clean project or adapter module with no inherited Mappls credential or opaque provider state A reviewed, credential-free source example starting with “Sample code for Insight Dashboard” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-intouch-android-sdk","kind":"Source launchpad","title":"Mappls Intouch Android SDK: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-intouch-android-sdk","eyebrow":"mappls-intouch-android-sdk · stateful · source-ready","keywords":"SDK Android tracking-telematics workforce gis-analytics widgets-deep-links capture-feedback The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 47e2aea8b4e7549e12b44dfe. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-intouch-android-sdk` and fingerprint `47e2aea8b4e7549e12b44dfe` recorded in the project An Android project with a supported Gradle and Kotlin or Java toolchain OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A durable aggregate identity, idempotency key, optimistic version, audit, outbox, reconciliation, privacy, and retirement design The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content. A state-changing response is lost The provider may have committed while the application lacks acknowledgement. Reconcile by stable provider/business identity and original idempotency key; never send a new command identity until authoritative state is known."},{"id":"source-launchpad:mappls-intouch-ios-distribution","kind":"Source launchpad","title":"Mappls Intouch IOS Distribution: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-intouch-ios-distribution","eyebrow":"mappls-intouch-ios-distribution · stateful · selection-required","keywords":"Distribution iOS tracking-telematics No readable public README was retrieved, so provider-specific binding stops at source and entitlement selection. The immutable evidence key is 9b4522931dc0fa13f91cd719. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-intouch-ios-distribution` and fingerprint `9b4522931dc0fa13f91cd719` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A durable aggregate identity, idempotency key, optimistic version, audit, outbox, reconciliation, privacy, and retirement design The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content. A state-changing response is lost The provider may have committed while the application lacks acknowledgement. Reconcile by stable provider/business identity and original idempotency key; never send a new command identity until authoritative state is known."},{"id":"source-launchpad:mappls-intouch-ios-distribution-base","kind":"Source launchpad","title":"Mappls Intouch IOS Distribution Base: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-intouch-ios-distribution-base","eyebrow":"mappls-intouch-ios-distribution-base · stateful · selection-required","keywords":"Distribution iOS tracking-telematics No readable public README was retrieved, so provider-specific binding stops at source and entitlement selection. The immutable evidence key is 01ba4719c80b6fe911b091a7. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-intouch-ios-distribution-base` and fingerprint `01ba4719c80b6fe911b091a7` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A durable aggregate identity, idempotency key, optimistic version, audit, outbox, reconciliation, privacy, and retirement design The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content. A state-changing response is lost The provider may have committed while the application lacks acknowledgement. Reconcile by stable provider/business identity and original idempotency key; never send a new command identity until authoritative state is known."},{"id":"source-launchpad:mappls-intouch-ios-sdk","kind":"Source launchpad","title":"[Mappls Intouch SDK](): source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-intouch-ios-sdk","eyebrow":"mappls-intouch-ios-sdk · stateful · source-ready","keywords":"SDK iOS tracking-telematics workforce gis-analytics capture-feedback The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is d11c093839d4dfcabfdba4e9. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-intouch-ios-sdk` and fingerprint `d11c093839d4dfcabfdba4e9` recorded in the project An iOS project with Xcode and the package manager required by the source release OAuth client credentials issued for the intended Mappls project A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A durable aggregate identity, idempotency key, optimistic version, audit, outbox, reconciliation, privacy, and retirement design The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content. A state-changing response is lost The provider may have committed while the application lacks acknowledgement. Reconcile by stable provider/business identity and original idempotency key; never send a new command identity until authoritative state is known."},{"id":"source-launchpad:mappls-intouch-rest-apis","kind":"Source launchpad","title":"Mappls Intouch REST Apis: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-intouch-rest-apis","eyebrow":"mappls-intouch-rest-apis · stateful · source-ready","keywords":"REST API REST routes-navigation tracking-telematics capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 06df37d758e9eed1e65f69df. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-intouch-rest-apis` and fingerprint `06df37d758e9eed1e65f69df` recorded in the project A trusted backend or API client capable of HTTPS requests OAuth client credentials issued for the intended Mappls project A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A durable aggregate identity, idempotency key, optimistic version, audit, outbox, reconciliation, privacy, and retirement design The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content. A state-changing response is lost The provider may have committed while the application lacks acknowledgement. Reconcile by stable provider/business identity and original idempotency key; never send a new command identity until authoritative state is known."},{"id":"source-launchpad:mappls-ios-sdk","kind":"Source launchpad","title":"Mappls iOS SDK: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-ios-sdk","eyebrow":"mappls-ios-sdk · stateless · source-ready","keywords":"SDK iOS maps search-places routes-navigation tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 3e3adfeaccf78bbea89a8cbb. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-ios-sdk` and fingerprint `3e3adfeaccf78bbea89a8cbb` recorded in the project An iOS project with Xcode and the package manager required by the source release OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-lms-ios-distribution","kind":"Source launchpad","title":"Mappls LMS IOS Distribution: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-lms-ios-distribution","eyebrow":"mappls-lms-ios-distribution · stateless · binary-review","keywords":"Distribution iOS other This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is a9995a27ea65a15fcd371bcb. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-lms-ios-distribution` and fingerprint `a9995a27ea65a15fcd371bcb` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-lms-ios-distribution-base","kind":"Source launchpad","title":"Mappls LMS IOS Distribution Base: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-lms-ios-distribution-base","eyebrow":"mappls-lms-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS other This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is c5f9894dd4d6f5a5c44eba24. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-lms-ios-distribution-base` and fingerprint `c5f9894dd4d6f5a5c44eba24` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-location-capture-android-sdk","kind":"Source launchpad","title":"Mappls Location Capture SDK: source launchpad","description":"Run one reviewed sdk seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-location-capture-android-sdk","eyebrow":"mappls-location-capture-android-sdk · hybrid · source-ready","keywords":"SDK Android search-places tracking-telematics workforce widgets-deep-links capture-feedback The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is b698bbb4e4a361b24ec4a5d2. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. This source does not establish a complete credential contract. Keep the adapter credential-free until the developer application, runtime, restriction, entitlement, and current authentication generation are approved. The exact source guide `mappls-location-capture-android-sdk` and fingerprint `b698bbb4e4a361b24ec4a5d2` recorded in the project An Android project with a supported Gradle and Kotlin or Java toolchain A clean project or adapter module with no inherited Mappls credential or opaque provider state A reviewed, credential-free source example starting with “Kotlin (settings.gradle.kts)” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-location-capture-ios-sdk","kind":"Source launchpad","title":"Mappls Location Capture IOS SDK: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-location-capture-ios-sdk","eyebrow":"mappls-location-capture-ios-sdk · hybrid · selection-required","keywords":"SDK iOS capture-feedback No readable public README was retrieved, so provider-specific binding stops at source and entitlement selection. The immutable evidence key is 01ba4719c80b6fe911b091a7. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. This source does not establish a complete credential contract. Keep the adapter credential-free until the developer application, runtime, restriction, entitlement, and current authentication generation are approved. The exact source guide `mappls-location-capture-ios-sdk` and fingerprint `01ba4719c80b6fe911b091a7` recorded in the project An iOS project with Xcode and the package manager required by the source release A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-location-capture-sdk-ios-distribution","kind":"Source launchpad","title":"Mappls Location Capture SDK (iOS): source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-location-capture-sdk-ios-distribution","eyebrow":"mappls-location-capture-sdk-ios-distribution · hybrid · binary-review","keywords":"Distribution iOS tracking-telematics workforce capture-feedback This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is aa62d5d6bb832bc41af55ce8. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-location-capture-sdk-ios-distribution` and fingerprint `aa62d5d6bb832bc41af55ce8` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Using Swift Package Manager (SPM)” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-map-ios-distribution","kind":"Source launchpad","title":"[Mappls Map SDK](): source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-map-ios-distribution","eyebrow":"mappls-map-ios-distribution · stateless · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is fd3d74d52bd9f7cd6db39df1. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-map-ios-distribution` and fingerprint `fd3d74d52bd9f7cd6db39df1` recorded in the project An iOS project with Xcode and the package manager required by the source release OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Dependencies” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-map-ios-distribution-base","kind":"Source launchpad","title":"[Mappls Map SDK](): source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-map-ios-distribution-base","eyebrow":"mappls-map-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is c44a5c147bbf3ed89e854974. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-map-ios-distribution-base` and fingerprint `c44a5c147bbf3ed89e854974` recorded in the project An iOS project with Xcode and the package manager required by the source release OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Dependencies” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-map-move-ios-distribution-base","kind":"Source launchpad","title":"[Mappls Map SDK](): source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-map-move-ios-distribution-base","eyebrow":"mappls-map-move-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is df6752e592f6282a73260c2e. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-map-move-ios-distribution-base` and fingerprint `df6752e592f6282a73260c2e` recorded in the project An iOS project with Xcode and the package manager required by the source release OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Dependencies” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-nearby-finder-ios-distribution","kind":"Source launchpad","title":"[Custom Search Nearby Records](Custom-Search-Nearby-Records): source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-nearby-finder-ios-distribution","eyebrow":"mappls-nearby-finder-ios-distribution · stateless · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is c98e46c291897e99300024c3. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Use only the public application credential class documented for the exact package, origin, bundle, or signing identity. Privileged server credentials remain outside the client. The exact source guide `mappls-nearby-finder-ios-distribution` and fingerprint `c98e46c291897e99300024c3` recorded in the project An iOS project with Xcode and the package manager required by the source release A Mappls project key restricted to the intended app, domain, or backend The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Installation” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-nearby-finder-ios-distribution-base","kind":"Source launchpad","title":"[Custom Search Nearby Records](Custom-Search-Nearby-Records): source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-nearby-finder-ios-distribution-base","eyebrow":"mappls-nearby-finder-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is c98e46c291897e99300024c3. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Use only the public application credential class documented for the exact package, origin, bundle, or signing identity. Privileged server credentials remain outside the client. The exact source guide `mappls-nearby-finder-ios-distribution-base` and fingerprint `c98e46c291897e99300024c3` recorded in the project An iOS project with Xcode and the package manager required by the source release A Mappls project key restricted to the intended app, domain, or backend The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Installation” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-nearby-ui-ios-distribution","kind":"Source launchpad","title":"Mappls Nearby Search Widget for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-nearby-ui-ios-distribution","eyebrow":"mappls-nearby-ui-ios-distribution · stateless · binary-review","keywords":"Distribution iOS maps search-places tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is 139be695050e0183761cf105. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-nearby-ui-ios-distribution` and fingerprint `139be695050e0183761cf105` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “MapplsNearbyCategoriesViewController” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-nearby-ui-ios-distribution-base","kind":"Source launchpad","title":"Mappls Nearby Search Widget for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-nearby-ui-ios-distribution-base","eyebrow":"mappls-nearby-ui-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS maps search-places tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is 97c2b14769200eece962afc2. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-nearby-ui-ios-distribution-base` and fingerprint `97c2b14769200eece962afc2` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “MapplsNearbyCategoriesViewController” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-raster-catalogue-ios-distribution","kind":"Source launchpad","title":"MapplsRasterCatalogue Plugin for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-raster-catalogue-ios-distribution","eyebrow":"mappls-raster-catalogue-ios-distribution · stateless · binary-review","keywords":"Distribution iOS maps tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is 4bc01e5166d2793f3a0ca310. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-raster-catalogue-ios-distribution` and fingerprint `4bc01e5166d2793f3a0ca310` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Initialization MapplsRasterCatalogue Plugin” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-raster-catalogue-ios-distribution-base","kind":"Source launchpad","title":"MapplsRasterCatalogue Plugin for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-raster-catalogue-ios-distribution-base","eyebrow":"mappls-raster-catalogue-ios-distribution-base · stateless · binary-review","keywords":"Distribution iOS maps tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is 4bc01e5166d2793f3a0ca310. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-raster-catalogue-ios-distribution-base` and fingerprint `4bc01e5166d2793f3a0ca310` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Initialization MapplsRasterCatalogue Plugin” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-react-native-intouch-sdk","kind":"Source launchpad","title":"Mappls Intouch React Native SDK: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-react-native-intouch-sdk","eyebrow":"mappls-react-native-intouch-sdk · stateful · source-ready","keywords":"SDK React Native tracking-telematics workforce capture-feedback The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is cb0703543c8025cdd17cc535. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. This source does not establish a complete credential contract. Keep the adapter credential-free until the developer application, runtime, restriction, entitlement, and current authentication generation are approved. The exact source guide `mappls-react-native-intouch-sdk` and fingerprint `cb0703543c8025cdd17cc535` recorded in the project A React Native project with both native build environments A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A durable aggregate identity, idempotency key, optimistic version, audit, outbox, reconciliation, privacy, and retirement design The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content. A state-changing response is lost The provider may have committed while the application lacks acknowledgement. Reconcile by stable provider/business identity and original idempotency key; never send a new command identity until authoritative state is known."},{"id":"source-launchpad:mappls-react-native-sdk","kind":"Source launchpad","title":"Mappls React Native SDK: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-react-native-sdk","eyebrow":"mappls-react-native-sdk · stateless · source-ready","keywords":"SDK React Native maps search-places routes-navigation tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 2bf827b9457541a5e1624942. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-react-native-sdk` and fingerprint `2bf827b9457541a5e1624942` recorded in the project A React Native project with both native build environments OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-rest-apis","kind":"Source launchpad","title":"Mappls Map APIs (REST) !: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-rest-apis","eyebrow":"mappls-rest-apis · stateless · source-ready","keywords":"REST API REST maps search-places routes-navigation gis-analytics capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is a27fe1435b9cd778f7d5352d. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-rest-apis` and fingerprint `a27fe1435b9cd778f7d5352d` recorded in the project A trusted backend or API client capable of HTTPS requests OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-ui-widget-ios-distribution","kind":"Source launchpad","title":"MapplsUIWidgets - UI Components SDK for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-ui-widget-ios-distribution","eyebrow":"mappls-ui-widget-ios-distribution · hybrid · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is fa23204b72658dbd8f725bcd. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-ui-widget-ios-distribution` and fingerprint `fa23204b72658dbd8f725bcd` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Add a full-screen control” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-ui-widget-ios-distribution-base","kind":"Source launchpad","title":"MapplsUIWidgets - UI Components SDK for iOS: source launchpad","description":"Run one reviewed distribution seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-ui-widget-ios-distribution-base","eyebrow":"mappls-ui-widget-ios-distribution-base · hybrid · binary-review","keywords":"Distribution iOS maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform This repository is distribution evidence; package presence does not prove the owning product contract or compatibility matrix. The immutable evidence key is e117a13d81e7182e759a4d72. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-ui-widget-ios-distribution-base` and fingerprint `e117a13d81e7182e759a4d72` recorded in the project An iOS project with Xcode and the package manager required by the source release The corresponding product entitlement enabled for the developer application An approved package version, checksum, dependency matrix, entitlement, and owning product guide A reviewed, credential-free source example starting with “Add a full-screen control” An application-owned intent, generation, candidate, commit/review, cancellation, and cleanup model The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-web-maps","kind":"Source launchpad","title":"Sign up for Mappls: source launchpad","description":"Run one reviewed guide seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-web-maps","eyebrow":"mappls-web-maps · stateless · source-ready","keywords":"Guide Web maps search-places routes-navigation gis-analytics widgets-deep-links capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 6d102a2fe3c3301e12220a39. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Record a non-secret entitlement reference and the approved package identity. License material, activation payloads, private package URLs, and provider credentials never enter this starter archive. The exact source guide `mappls-web-maps` and fingerprint `6d102a2fe3c3301e12220a39` recorded in the project A browser application and an allowed development origin The corresponding product entitlement enabled for the developer application A clean project or adapter module with no inherited Mappls credential or opaque provider state A reviewed, credential-free source example starting with “Installation” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-web-maps-js","kind":"Source launchpad","title":"Mappls Web Maps JS: source launchpad","description":"Run one reviewed guide seam from the exact repository evidence, then prove its failure and lifecycle boundary.","href":"/launchpads/mappls-web-maps-js","eyebrow":"mappls-web-maps-js · stateless · source-ready","keywords":"Guide Web maps search-places routes-navigation gis-analytics widgets-deep-links capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 5b7bd5c66a780e8315d64bec. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-web-maps-js` and fingerprint `5b7bd5c66a780e8315d64bec` recorded in the project A browser application and an allowed development origin OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A reviewed, credential-free source example starting with “Adding the Map Script to your web page” A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-web-plugins","kind":"Source launchpad","title":"Mappls Web Plugins: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-web-plugins","eyebrow":"mappls-web-plugins · stateless · source-ready","keywords":"Widget Web Widgets/Deep links maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 0500ead3cc1dcb4e9f2fcd08. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. Keep OAuth client credentials and token exchange in an approved trusted runtime. Client UI receives only bounded application results, never the client secret or refresh material. The exact source guide `mappls-web-plugins` and fingerprint `0500ead3cc1dcb4e9f2fcd08` recorded in the project A browser application and an allowed development origin OAuth client credentials issued for the intended Mappls project A Mappls project key restricted to the intended app, domain, or backend A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:mappls-workmate-android-sdk","kind":"Source launchpad","title":"Workmate SDK - Android: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/mappls-workmate-android-sdk","eyebrow":"mappls-workmate-android-sdk · stateful · source-ready","keywords":"SDK Android tracking-telematics workforce identity-platform The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is e04a9f1e646d0348e9df1cdb. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. This source does not establish a complete credential contract. Keep the adapter credential-free until the developer application, runtime, restriction, entitlement, and current authentication generation are approved. The exact source guide `mappls-workmate-android-sdk` and fingerprint `e04a9f1e646d0348e9df1cdb` recorded in the project An Android project with a supported Gradle and Kotlin or Java toolchain A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A durable aggregate identity, idempotency key, optimistic version, audit, outbox, reconciliation, privacy, and retirement design The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content. A state-changing response is lost The provider may have committed while the application lacks acknowledgement. Reconcile by stable provider/business identity and original idempotency key; never send a new command identity until authoritative state is known."},{"id":"source-launchpad:skydnn-aiapi-docs","kind":"Source launchpad","title":"Skydnn AI APIs: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/skydnn-aiapi-docs","eyebrow":"skydnn-aiapi-docs · stateless · source-ready","keywords":"REST API REST AI/MCP maps gis-analytics ai-vision capture-feedback The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is f407d95bd8b3db716f04033d. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. This source does not establish a complete credential contract. Keep the adapter credential-free until the developer application, runtime, restriction, entitlement, and current authentication generation are approved. The exact source guide `skydnn-aiapi-docs` and fingerprint `f407d95bd8b3db716f04033d` recorded in the project A trusted backend or API client capable of HTTPS requests A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"source-launchpad:v1-2-0-logs","kind":"Source launchpad","title":"V1.2.0 Logs: source launchpad","description":"Complete source, release, entitlement, and adapter selection without inventing provider syntax.","href":"/launchpads/v1-2-0-logs","eyebrow":"v1.2.0-logs · stateless · source-ready","keywords":"Sample Unspecified other The current repository snapshot provides a readable source guide for this first-success path. The immutable evidence key is 29445321439b02ac0adff1a2. Confirm the released version, account region, entitlement, authentication, and supported product contract before live traffic. This source does not establish a complete credential contract. Keep the adapter credential-free until the developer application, runtime, restriction, entitlement, and current authentication generation are approved. The exact source guide `v1-2-0-logs` and fingerprint `29445321439b02ac0adff1a2` recorded in the project A clean project or adapter module with no inherited Mappls credential or opaque provider state A product-owner decision for the first supported operation because this source provides no credential-free copyable fenced example A bounded request or screen lifecycle with explicit timeout, error, and teardown behavior The repository exists but the selected package, endpoint, or product cannot be confirmed A distribution, sample, legacy name, public README, local candidate, and account entitlement are being treated as interchangeable authority. Keep binding selection-required; capture the exact source and account evidence, then obtain an owning product decision instead of borrowing adjacent syntax. Authentication or entitlement is rejected The application identity, credential generation, restriction, host, region, package, product, or entitlement does not match the selected source line. Retain only safe request/configuration identity, reconcile the developer application and source manifest, rotate anything exposed, and retry only after the mismatch is explicit. The first interaction times out, returns empty, or becomes unavailable Network, provider, region, quota, lifecycle readiness, or input constraints are unresolved. Return a typed unavailable/empty result, preserve the same request identity for a safe read retry, and never manufacture a fixture success as provider evidence. A callback, result, or event arrives after cancellation or replacement Screen, request, controller, subscription, or aggregate generation ownership is missing. Reject the stale generation, dispose it once, retain current application state, and count the late result without persisting opaque content."},{"id":"starter-kit:rest-api-starter","kind":"Starter kit","title":"Trusted REST service starter","description":"A dependency-free autosuggest service with bounded input, fixture-first behavior, abortable live calls, normalized output, and credential-safe errors.","href":"/starter-kits/rest-api-starter","eyebrow":"REST · JavaScript · public-source","keywords":"Node.js service rest-api mappls-rest-apis Load the current restricted static key only inside the trusted process. Legacy OAuth and InTouch bearer credentials are separate generations and must never be mixed by inference. The public REST repository and normalized operation are repository evidence; the issued account remains authoritative for host, auth generation, quota, and region. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof package.json json Run and test commands src/service.mjs javascript Fixture/live provider seam src/server.mjs javascript Bounded application endpoint test/service.test.mjs javascript Credential-free contract tests"},{"id":"starter-kit:web-map-starter","kind":"Starter kit","title":"Accessible web map host starter","description":"A responsive keyboard-accessible map host with explicit loading, ready, unavailable, selection, and teardown states around a replaceable SDK adapter.","href":"/starter-kits/web-map-starter","eyebrow":"Web · HTML + JavaScript · public-source","keywords":"Static web application web-map mappls-web-maps mappls-web-maps-js Use only the browser-supported public key restricted to exact origins. Privileged REST credentials stay on a backend-for-frontend. The selected Web Maps source contains current and sample evidence; confirm the script/package line and allowed origin against the target project. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof index.html html Accessible visual and text shell src/app.js javascript SDK-owned lifecycle seam styles.css css Responsive visible states"},{"id":"starter-kit:android-native-starter","kind":"Starter kit","title":"Android lifecycle adapter starter","description":"A Kotlin contract that keeps camera, selection, permission, recreation, and teardown state outside unconfirmed SDK types.","href":"/starter-kits/android-native-starter","eyebrow":"Android · Kotlin · public-source","keywords":"Android adapter module android-native mappls-android-sdk mappls-android-compose-demo Use only the documented Android credential configuration restricted to the package and signing identity. Server credentials never belong in the APK. The public repositories are sample-classified evidence; confirm Maven coordinates, BoM, AGP/Kotlin, min/target SDK, and supported release with Mappls. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof src/main/kotlin/MapFeature.kt kotlin SDK-independent feature contract src/main/kotlin/FixtureMapAdapter.kt kotlin Deterministic native lifecycle fixture BUILD_SELECTION.md markdown AGP, Kotlin, repository, and SDK gate"},{"id":"starter-kit:ios-native-starter","kind":"Starter kit","title":"iOS view-ownership starter","description":"A dependency-free Swift feature contract that isolates selected package types behind main-actor lifecycle and restoration.","href":"/starter-kits/ios-native-starter","eyebrow":"iOS · Swift · public-source","keywords":"Swift package ios-native mappls-map-ios-distribution mappls-api-kit-ios-distribution Use only the documented app credential restricted to the bundle/team context. Keep server secrets and privileged exchanges outside the application bundle. Public distribution repositories identify candidate package lines, not a universal version matrix. Confirm SwiftPM products, binary checksums, Xcode/Swift, deployment target, and extension compatibility together. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof Package.swift swift Dependency-free contract package Sources/MapplsStarter/MapFeature.swift swift Main-actor SDK seam Sources/MapplsStarter/FixtureMapAdapter.swift swift Deterministic view lifecycle fixture"},{"id":"starter-kit:react-native-map-starter","kind":"Starter kit","title":"React Native bridge-contract starter","description":"A typed shared state contract with independent Android and iOS adapter qualification instead of assumed wrapper parity.","href":"/starter-kits/react-native-map-starter","eyebrow":"React Native · TypeScript · public-source","keywords":"Cross-platform feature module react-native-map mappls-react-native-sdk Configure Android and iOS app credentials independently and keep privileged calls on a backend. JavaScript configuration is not a secret store. The public wrapper is sample-classified. Confirm React Native, wrapper, New Architecture status, Gradle/Kotlin, Xcode/Swift, and underlying native Mappls versions as one release unit. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof src/mappls-feature.ts typescript Shared bridge contract src/fixture-adapter.ts typescript Deterministic bridge fixture NATIVE_MATRIX.md markdown Independent native release checklist"},{"id":"starter-kit:flutter-map-starter","kind":"Starter kit","title":"Flutter place-selection starter","description":"A Dart selection aggregate and adapter seam preserving Mappls Pin identity while Android and iOS distributions are verified independently.","href":"/starter-kits/flutter-map-starter","eyebrow":"Flutter · Dart · public-source","keywords":"Flutter feature package flutter-map mappls-flutter-sdk flutter-mapmyindia-gl Configure separately restricted Android and iOS app credentials in their native projects. Do not put server secrets in Dart assets or compile-time constants. The corpus contains Mappls sample evidence and an older current-classified MapmyIndia wrapper. Confirm the supported Flutter/Dart plugin and both native SDK lines before choosing one. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof pubspec.yaml yaml Dependency-neutral package lib/mappls_feature.dart dart Stable selection and adapter contract lib/fixture_adapter.dart dart Credential-free fixture"},{"id":"starter-kit:cordova-maintenance-starter","kind":"Starter kit","title":"Cordova stabilization starter","description":"A legacy-safe WebView facade that waits for device readiness, owns teardown, and keeps a web/deep-link fallback available for migration.","href":"/starter-kits/cordova-maintenance-starter","eyebrow":"Cordova · JavaScript · legacy-maintenance","keywords":"Legacy capability facade cordova-maintenance mapmyindia-map-cordova-ionic-beta mapmyindia-restapi-cordova-ionic-beta Treat all client credentials as platform-restricted public credentials and keep privileged REST work on a backend. Never reuse legacy auth with a current host by resemblance. Only legacy/beta Cordova sources exist in the public corpus. This quickstart is for stabilizing an existing estate—not recommending Cordova for new development. Use the migration track to select a supported target. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof config.xml xml Minimal legacy host identity www/index.html html WebView host with deep-link fallback www/js/index.js javascript Device-ready lifecycle facade"},{"id":"starter-kit:xamarin-maintenance-starter","kind":"Starter kit","title":"Xamarin extraction starter","description":"A shared .NET contract extracting business identity and commands from legacy bindings before independent Android and iOS successor selection.","href":"/starter-kits/xamarin-maintenance-starter","eyebrow":"Xamarin · C# · entitlement-required","keywords":"Migration contract library xamarin-maintenance Use separately restricted native app credentials and keep privileged service credentials on a backend. Do not move secrets into shared assemblies during extraction. No public repository in the snapshot provides a current Xamarin successor. Obtain the existing binding/source and target-platform contract from Mappls and use the migration principles before implementation. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof MapplsMigration.csproj xml Portable contract build MapplsFeature.cs csharp Binding-independent contract MIGRATION.md markdown Characterization and replacement sequence"},{"id":"starter-kit:linux-embedded-starter","kind":"Starter kit","title":"Embedded Linux supervisor starter","description":"A proprietary-runtime-neutral C++ seam with boot, health, degraded, stopped, and teardown states for entitled Linux distributions.","href":"/starter-kits/linux-embedded-starter","eyebrow":"Linux · C++ · entitlement-required","keywords":"Supervised native process linux-embedded Use device/workload identity and entitlement delivered through the approved provisioning channel; never bake fleet-wide secrets into an image or package. The public snapshot has no platform-specific Linux distribution guide. The runtime, ABI, compiler, graphics, activation, and data contract must come from the entitled private distribution. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof CMakeLists.txt cmake Dependency-neutral native build src/runtime_adapter.hpp cpp Entitled runtime boundary src/main.cpp cpp Bounded fixture entrypoint"},{"id":"starter-kit:automotive-navigation-starter","kind":"Starter kit","title":"Automotive release-manifest starter","description":"A protected-artifact-neutral release skeleton for runtime/data/configuration/voice compatibility, qualification, atomic switch, and rollback.","href":"/starter-kits/automotive-navigation-starter","eyebrow":"Automotive · C++ + JSON · entitlement-required","keywords":"Dual-slot release controller automotive-navigation Provision per-device identity, activation, regions, runtime, and map data through the approved vehicle/fleet control plane. Avoid shared embedded credentials. The public snapshot does not establish an automotive SDK or safety contract. Obtain the entitled runtime, data, activation, vehicle-interface, HMI, and regulatory requirements before binding an adapter. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof release-manifest.example.json json Compatible release unit src/release_controller.hpp cpp Atomic update contract QUALIFICATION.md markdown Vehicle and interruption matrix"},{"id":"starter-kit:widgets-place-starter","kind":"Starter kit","title":"Widget journey host starter","description":"A credential-free nearby iframe host with loading, ready, fallback, candidate, committed, and destroyed application states.","href":"/starter-kits/widgets-place-starter","eyebrow":"Widgets · HTML + JavaScript · public-source","keywords":"Accessible iframe host widgets-place mappls-web-plugins Use only the widget/browser credential class restricted to exact origins. Validate every postMessage/callback payload and keep privileged operations on the server. The current public Web Plugins guide spans current vector and legacy raster integration branches; source activity is not a support promise. Confirm the exact widget, script, origin, event schema, release, entitlement, and authentication line before implementation. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof index.html html Accessible widget host host.js javascript Explicit iframe lifecycle HOST_STATES.md markdown Application-owned state"},{"id":"starter-kit:deep-links-starter","kind":"Starter kit","title":"Deep-link handoff starter","description":"A dependency-free navigation-link builder with validation and separate click, app-attempt, fallback, and arrival evidence.","href":"/starter-kits/deep-links-starter","eyebrow":"Deep links · HTML + JavaScript · public-source","keywords":"Zero-SDK web handoff deep-links mappls-app-widgets Deep links contain no credential. Put only bounded non-sensitive intent in the URL; precise private/user data and server secrets must never become query parameters. Use the exact link shape documented by the current App Widgets source. The scaffold below deliberately receives that approved base rather than inventing an undocumented path. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof index.html html Validated destination form app.js javascript Exact documented navigation shape HANDOFF.md markdown Evidence and privacy rules"},{"id":"starter-kit:mcp-agent-starter","kind":"Starter kit","title":"MCP client policy starter","description":"A dependency-free policy starter separating offline and live-read MCP resources before adding an SDK transport.","href":"/starter-kits/mcp-agent-starter","eyebrow":"MCP · JavaScript + JSON · local-reference","keywords":"AI tool-governance module mcp-agent Keep provider credentials in the MCP server process or approved secret provider, never model context or client configuration committed to source. A remote internal gateway bearer or issuer-bound OAuth access token is independent from every Mappls provider credential. Documentation and migration tools require no live credential. The MCP implementation is maintained in this repository and protocol-tested over stdio and Streamable HTTP. Live tool success still depends on the issued account, operation, region, and credential scope; production OAuth authorization-server registration, consent, lifecycle, and revocation remain company integrations. README.md markdown Setup and first-success boundary STARTER_MANIFEST.json json Machine-readable project scope .env.example dotenv Blank non-secret configuration EVIDENCE.md markdown Source and selection boundary ACCEPTANCE.md markdown Success and hostile-path proof mcp.config.example.json json Credential-empty transports src/policy.mjs javascript Least-authority tool policy test/policy.test.mjs javascript Executable policy tests"},{"id":"api:core-location-get-api-places-woodpecker-address-standardization-api","kind":"API","title":"Address Standardization API","description":"Address Standardization API is a process to convert the non formatted address into the user readable format by omitting unnecessary information in the address. MapmyIndia address standardization API provides real addresses along with admin and other information. This APIs follow OAuth2 based security. To know more on how to create your authorization tokens, please use our authorization token URL. More details available here. Live Demo","href":"/api-reference/core-location-get-api-places-woodpecker-address-standardization-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/api/places/woodpecker GET Core Location Address Standardization API WoodpeckerAPI stateless request-response"},{"id":"api:core-location-get-api-places-search-json-autosuggest-api","kind":"API","title":"AutoSuggest API","description":"The Autosuggest API helps users to complete queries faster by adding intelligent search capabilities to your web or mobile app. This API returns a list of results as well as suggested queries as the user types in the search field. This API also supports Hindi language. If a user enters query in hindi language he will get results in Hindi. This APIs follow OAuth2 based security. To know more on how to create your authorization tokens, please use our authorization token URL. More details available here. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-api-places-search-json-autosuggest-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/api/places/search/json GET Core Location Autosuggest API AutoSuggestAPI stateless request-response"},{"id":"api:core-location-get-rest-key-resources-profile-geopositions-distance-matrix-api","kind":"API","title":"Distance Matrix API","description":"This REST API computes the distance and durations in a matrix of routes between a set of source/primary positions (geographical coordinates) and a set of all supplied secondary positions. Please note that maximum number of points are limited to 100 only including source and secondary positions. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-rest-key-resources-profile-geopositions-distance-matrix-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{rest-key}/{resources}/{profile}/{geopositions} GET Core Location Distance Matrix APIs dmAPI stateless request-response"},{"id":"api:core-location-get-rest-key-distance-matrix-predictive-driving-coordinates-distance-matrix-predictive-eta-api","kind":"API","title":"Distance Matrix Predictive ETA API","description":"This API computes the distance and duration of a route between a source/primary position (geographical coordinates) and a list of all supplied secondary positions. Optionally one can input the deptime parameter and get the distance and duration optimized for that part of the day of a week. Time based functionality is available for selected cities only. Please note that maximum number of points are limited to 100 only including source and secondary positions. PREMIUM API","href":"/api-reference/core-location-get-rest-key-distance-matrix-predictive-driving-coordinates-distance-matrix-predictive-eta-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/distance_matrix_predictive/driving/{coordinates} GET Core Location Distance Matrix Predictive API dmPAPI stateless request-response"},{"id":"api:core-location-get-rest-key-elevation-elevation-api","kind":"API","title":"Elevation API","description":"The Elevation API provides elevation data above the sea level for location on Earth’s surface. The Elevation API allows you to retrieve sampled elevation data along a path. This API can be useful for biking, trucking & in other routing applications.","href":"/api-reference/core-location-get-rest-key-elevation-elevation-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/elevation GET Core Location Elevation API ElevationAPI stateless request-response"},{"id":"api:core-location-get-api-places-geocode-geocode-api","kind":"API","title":"Geocode API","description":"All mapping APIs that are used in mobile or web apps need some geo-position coordinates to refer to any given point on the map. Our Geocoding API converts real addresses into these geographic reference positions to be placed on a map, be it for any street, area, postal code, POI or a house number etc. This APIs follow OAuth2 based security. To know more on how to create your authorization tokens, please use our authorization token URL. More details available here. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-api-places-geocode-geocode-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/api/places/geocode GET Core Location Geocode API AtlasGeocodeAPI stateless request-response"},{"id":"api:core-location-get-api-places-nearby-json-nearby-api","kind":"API","title":"Nearby API","description":"Nearby Places API, enables you to add discovery and search of nearby POIs by searching for a generic keyword used to describe a category of places or via the unique code assigned to that category. This APIs follow OAuth2 based security. To know more on how to create your authorization tokens, please use our authorization token URL. More details available here. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-api-places-nearby-json-nearby-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/api/places/nearby/json GET Core Location Nearby API AtlasNearbyAPI stateless request-response"},{"id":"api:core-location-post-api-places-along-route-poi-along-the-route-api","kind":"API","title":"POI Along the Route API","description":"With POI Along the Route API user will be able to get the details of POIs of a particular category along his set route. The main focus of this API is to provide convenience to the user and help him in locating the place of his interest on his set route. This APIs follow OAuth2 based security. To know more on how to create your authorization tokens, please use our authorization token URL. More details available here","href":"/api-reference/core-location-post-api-places-along-route-poi-along-the-route-api","eyebrow":"POST · Core Maps, Search & Routing · legacy-source","keywords":"/api/places/along_route POST Core Location POI Along the Route API AtlasPOIAlongtheRouteAPI stateless request-response"},{"id":"api:core-location-get-apis-o2o-entity-eloc-place-detail-api","kind":"API","title":"Place Detail API","description":"MapmyIndia eloc is a simple, standardized and precise pan-India digital address system. Every location has been assigned a unique digital address or an eLoc. Place Detail API can be used to extract the details of a place with the help of its eLoc i.e. a 6 digit code or a placeid. This APIs follow OAuth2 based security. To know more on how to create your authorization tokens, please use our authorization token URL. More details available here. The API leverages OAuth 2.0 based security. Hence, the developer would need to send a request for access token using their clientid and clientsecret to the OAuth API. Once validated from the OAuth API, the accesstoken and the tokentype need to be sent as Authorization header with the value: \"{tokentype} {accesstoken}”. Authorization : tokentype accesstoken.","href":"/api-reference/core-location-get-apis-o2o-entity-eloc-place-detail-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/apis/O2O/entity/{eLoc} GET Core Location Place Detail API placeDetail stateless request-response"},{"id":"api:core-location-get-rest-key-rev-geocode-reverse-geocode-api","kind":"API","title":"Reverse Geocode API","description":"Reverse Geocoding is a process to give the closest matching address to a provided geographical coordinates (latitude/longitude). MapmyIndia reverse geocoding API provides real addresses along with nearest popular landmark for any such geo-positions on the map. This API also works in Hindi language response. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-rest-key-rev-geocode-reverse-geocode-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/rev_geocode GET Core Location Reverse Geocode API ReverseGeocodeAPI stateless request-response"},{"id":"api:core-location-get-rest-key-resources-profile-geopositions-route-optimization-api","kind":"API","title":"Route Optimization API","description":"Route Optimization is the process of determining the most cost-efficient route. It needs to include all relevant factors such as the number and location of all the required stops on the route. In other words, this API will solve the Traveling Salesman Problem of routing and the returned path does not have to be the fastest path. As TSP is NP-hard it only returns an approximation. Currently, not all combinations of roundtrip, source and destination are supported. Right now, the following combinations are possible: | roundtrip | source | destination | supported | | --- | --- | --- | --- | | true | first | last | yes | | true | first | any | yes | | true | any | last | yes | | true | any | any | yes | | false | first | last | yes | Live Demo | PREMIUM API","href":"/api-reference/core-location-get-rest-key-resources-profile-geopositions-route-optimization-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{rest_key}/{resources}/{profile}/{geopositions} GET Core Location Route Optimization API routeOptAPI stateless request-response"},{"id":"api:core-location-get-rest-key-resources-profile-geopositions-routing-api","kind":"API","title":"Routing API","description":"Routing and displaying driving directions on map, including instructions for navigation, distance to destination, traffic etc. are few of the most important parts of developing a map based application. This REST API calculates driving routes between specified locations including via points based on route calculation type(optimal or shortest). Please note that maximum number of points are limited to 100 only including source and secondary positions. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-rest-key-resources-profile-geopositions-routing-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/{resources}/{profile}/{geopositions} GET Core Location Routing API routingAPI stateless request-response"},{"id":"api:core-location-get-rest-key-resources-biking-geopositions-routing-api-with-biking-profile","kind":"API","title":"Routing API with biking profile","description":"Routing and displaying driving directions on map, including instructions for navigation, distance to destination, traffic etc. are few of the most important parts of developing a map based application. This REST API calculates driving routes between specified locations including via points based on route calculation type(optimal or shortest). Please note that maximum number of points are limited to 100 only including source and secondary positions. The MapmyIndia Bike Routing API takes into consideration routes where bikes are allowed to travel as well as those roads which might be non-navigable to larger vehicles. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-rest-key-resources-biking-geopositions-routing-api-with-biking-profile","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/{resources}/biking/{geopositions} GET Core Location Routing API with Biking Profile routingAPI stateless request-response"},{"id":"api:core-location-get-rest-key-resources-driving-geopositions-routing-api-with-driving-profile","kind":"API","title":"Routing API with driving profile","description":"Routing and displaying driving directions on map, including instructions for navigation, distance to destination, traffic etc. are few of the most important parts of developing a map based application. This REST API calculates driving routes between specified locations including via points based on route calculation type(optimal or shortest). Please note that maximum number of points are limited to 100 only including source and secondary positions. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-rest-key-resources-driving-geopositions-routing-api-with-driving-profile","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/{resources}/driving/{geopositions} GET Core Location Routing API with Driving Profile routingAPI stateless request-response"},{"id":"api:core-location-get-rest-key-resources-trucking-geopositions-routing-api-with-trucking-profile","kind":"API","title":"Routing API with trucking profile","description":"Routing and displaying driving directions on map, including instructions for navigation, distance to destination, traffic etc. are few of the most important parts of developing a map based application. This REST API calculates driving routes between specified locations including via points based on route calculation type(optimal or shortest). Please note that maximum number of points are limited to 100 only including source and secondary positions. MapmyIndia Truck Routing API calculates routes optimized for trucks and other commercial vehicles. Designed for professional transportation routing logistics, the API calculates safe and efficient routes that consider a vehicle’s attributes in relation to any route limitations. It also uses live traffic to determine precise ETAs, especially for areas that tend to be more congested. The routes include information such as route instructions, travel duration, and travel distance. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-rest-key-resources-trucking-geopositions-routing-api-with-trucking-profile","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/{resources}/trucking/{geopositions} GET Core Location Routing API with Trucking Profile routingAPI stateless request-response"},{"id":"api:core-location-get-rest-key-resources-walking-geopositions-routing-api-with-walking-profile","kind":"API","title":"Routing API with walking profile","description":"Routing and displaying driving directions on map, including instructions for navigation, distance to destination, traffic etc. are few of the most important parts of developing a map based application. This REST API calculates driving routes between specified locations including via points based on route calculation type(optimal or shortest). Please note that maximum number of points are limited to 100 only including source and secondary positions. MapmyIndia Pedestrian Routing API calculates the best route for pedestrians. It takes into account how easy it is for pedestrians to maneuver between links in the route while disregarding traffic conditions. The API recommends actions that are relevant for pedestrians and the maneuver instructions contain texts that are suitable for someone who is walking. Live Demo | Download Sample Code","href":"/api-reference/core-location-get-rest-key-resources-walking-geopositions-routing-api-with-walking-profile","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/{resources}/walking/{geopositions} GET Core Location Routing API with Walking Profile routingAPI stateless request-response"},{"id":"api:core-location-post-rest-key-snaptoroad-snap-to-road-api","kind":"API","title":"Snap to Road API","description":"Snap-To-Road API, snaps given GPS points to the road network in the most plausible way. Maximum number of points are limited to 100 only. Our USP is to take GPS points collected along a route and return a similar set of corrected & aligned data with the points matched to the road with our intelligent Snap To Road API. Now seamlessly calculate accurate distances from points which follow the geometry of the road & show accurate positions on map. This API provides a critical feature that is immensely valuable when tracking assets and for data analytics of path traversed by vehicle, people or assets. Note : The request might result multiple sub-traces. Large jumps in the timestamps (> 60s) or improbable transitions lead to trace splits if a complete matching could not be found. The algorithm might not be able to match all points. Outliers are removed if they cannot be matched successfully. Live Demo","href":"/api-reference/core-location-post-rest-key-snaptoroad-snap-to-road-api","eyebrow":"POST · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/snapToRoad POST Core Location Snap to Road API snapToRoadAPI stateless request-response"},{"id":"api:core-location-get-rest-key-still-image-still-map-image-api","kind":"API","title":"Still Map Image API","description":"The Still Map Image API creates a map based on URL parameters sent through a standard HTTP request and returns the map as an image which you can display on your application. The API lets you embed MapmyIndia Maps image according to geo-position, pixel size and zoom level of the map on your application without requiring any dynamic page loading. The image can be a retina image and markers can be added to the image to indicate position of any object.","href":"/api-reference/core-location-get-rest-key-still-image-still-map-image-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/still_image GET Core Location Still Map Image API stillMapImageAPI stateless request-response"},{"id":"api:core-location-get-api-places-textsearch-json-text-search-api","kind":"API","title":"Text Search API","description":"Text Search API is a service that aims to provide information about a list of places on the basis of a text string entered by the user. It uses the location information that is provided along with the query to try to understand the request. This API now supports Hindi language so you can now search queries in Hindi too. This APIs follow OAuth2 based security. To know more on how to create your authorization tokens, please use our authorization token URL. More details available here. Download Sample Code","href":"/api-reference/core-location-get-api-places-textsearch-json-text-search-api","eyebrow":"GET · Core Maps, Search & Routing · legacy-source","keywords":"/api/places/textsearch/json GET Core Location Text Search API AtlasTextSearchAPI stateless request-response"},{"id":"api:core-location-post-security-oauth-token-token-generation-api","kind":"API","title":"Token Generation API","description":"This API is required to generate tokens authorize the oAuth 2 based APIs. Hence, the developer would need to send a request for access token using their clientid and clientsecret to the Token Generation API. Once validated from the OAuth API, the accesstoken and the tokentype need to be sent as Authorization header with the value: {tokentype} {accesstoken} Authorization: “tokentype accesstoken”.","href":"/api-reference/core-location-post-security-oauth-token-token-generation-api","eyebrow":"POST · Core Maps, Search & Routing · legacy-source","keywords":"/security/oauth/token POST Core Location Token Generation API tokenGenerationAPI stateless request-response"},{"id":"api:core-location-post-rest-key-still-image-polyline-traveled-route-image-api","kind":"API","title":"Traveled Route Image API","description":"This API can be used to get an image of map with traveled route plotted on it. The image size can be specified; which will dynamically create an image of varying zoom levels with the start and end locations plotted on it.","href":"/api-reference/core-location-post-rest-key-still-image-polyline-traveled-route-image-api","eyebrow":"POST · Core Maps, Search & Routing · legacy-source","keywords":"/{REST_KEY}/still_image_polyline POST Core Location Traveled Route Image API stillImagePolylineAPI stateless request-response"},{"id":"api:geoanalytics-get-listingapi-list-layer-attributes-or-a-layer-bounding-box","kind":"API","title":"List layer attributes or a layer bounding box","description":"Returns documented attribute values or bbox for one Geo-Analytics layer. Supply addr, or supply geoboundtype together with geobound.","href":"/api-reference/geoanalytics-get-listingapi-list-layer-attributes-or-a-layer-bounding-box","eyebrow":"GET · Geo-Analytics Listing · legacy-source","keywords":"/listingapi GET Geo-Analytics Geo-Analytics Listing listGeoAnalyticsAttributes stateless request-response"},{"id":"api:intouch-get-alarm-this-api-will-get-all-the-alarm-configurations-for-a-user-v1-0-0","kind":"API","title":"This API will get all the alarm configurations for a user.","description":"Based on the passed token key, the API will return the list of all alarm configs.","href":"/api-reference/intouch-get-alarm-this-api-will-get-all-the-alarm-configurations-for-a-user-v1-0-0","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/alarm GET InTouch alarm stateful observe"},{"id":"api:intouch-get-alarm-this-api-will-get-all-the-alarm-configurations-for-a-user","kind":"API","title":"This API will get all the alarm configurations for a user.","description":"Based on the passed token key, the API will return the list of all alarm configs.","href":"/api-reference/intouch-get-alarm-this-api-will-get-all-the-alarm-configurations-for-a-user","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/alarm GET InTouch alarm stateful observe"},{"id":"api:intouch-post-alarm-this-api-will-create-an-alarm-v1-0-0","kind":"API","title":"This API will create an alarm.","description":"Based on the input parameters provided to this POST alarm API, a new alarm will get created for a single or multiple devices","href":"/api-reference/intouch-post-alarm-this-api-will-create-an-alarm-v1-0-0","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/alarm POST InTouch alarm createAlarm stateful command"},{"id":"api:intouch-post-alarm-this-api-will-create-an-alarm","kind":"API","title":"This API will create an alarm.","description":"Based on the input parameters provided to this POST alarm API, a new alarm will get created for a single or multiple devices","href":"/api-reference/intouch-post-alarm-this-api-will-create-an-alarm","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/alarm POST InTouch alarm createAlarm stateful command"},{"id":"api:intouch-get-alarm-alarmlog-gets-the-list-of-alarm-config-s-v1-0-0","kind":"API","title":"Gets The List Of Alarm Config(s)","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-get-alarm-alarmlog-gets-the-list-of-alarm-config-s-v1-0-0","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/alarm/alarmLog/ GET InTouch alarm stateful observe"},{"id":"api:intouch-get-alarm-alarmlog-gets-the-list-of-alarm-config-s","kind":"API","title":"Gets The List Of Alarm Config(s)","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-get-alarm-alarmlog-gets-the-list-of-alarm-config-s","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/alarm/alarmLog/ GET InTouch alarm stateful observe"},{"id":"api:intouch-delete-alarm-id-deletes-an-alarm-config-v1-0-0","kind":"API","title":"Deletes An Alarm Config","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-delete-alarm-id-deletes-an-alarm-config-v1-0-0","eyebrow":"DELETE · InTouch Telematics · legacy-source","keywords":"/alarm/{id} DELETE InTouch alarm stateful retire"},{"id":"api:intouch-delete-alarm-id-deletes-an-alarm-config","kind":"API","title":"Deletes An Alarm Config","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-delete-alarm-id-deletes-an-alarm-config","eyebrow":"DELETE · InTouch Telematics · legacy-source","keywords":"/alarm/{id} DELETE InTouch alarm stateful retire"},{"id":"api:intouch-post-alarm-id-updates-an-alarm-config-v1-0-0","kind":"API","title":"Updates An Alarm Config","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-post-alarm-id-updates-an-alarm-config-v1-0-0","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/alarm/{id} POST InTouch alarm stateful command"},{"id":"api:intouch-post-alarm-id-updates-an-alarm-config","kind":"API","title":"Updates An Alarm Config","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-post-alarm-id-updates-an-alarm-config","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/alarm/{id} POST InTouch alarm stateful command"},{"id":"api:intouch-get-alarms-this-api-will-get-all-the-alarm-configurations-for-a-user","kind":"API","title":"This API will get all the alarm configurations for a user.","description":"Based on the passed token key, the API will return the list of all alarm configs.","href":"/api-reference/intouch-get-alarms-this-api-will-get-all-the-alarm-configurations-for-a-user","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/alarms GET InTouch alarm stateful observe"},{"id":"api:intouch-post-alarms-this-api-will-create-an-alarm","kind":"API","title":"This API will create an alarm.","description":"Based on the input parameters provided to this POST alarm API, a new alarm will get created for a single or multiple devices","href":"/api-reference/intouch-post-alarms-this-api-will-create-an-alarm","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/alarms POST InTouch alarm createAlarm stateful command"},{"id":"api:intouch-get-alarms-alarmlogs-gets-the-list-of-alarm-config-s","kind":"API","title":"Gets The List Of Alarm Config(s)","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-get-alarms-alarmlogs-gets-the-list-of-alarm-config-s","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/alarms/alarmlogs/ GET InTouch alarm stateful observe"},{"id":"api:intouch-delete-alarms-id-deletes-an-alarm-config","kind":"API","title":"Deletes An Alarm Config","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-delete-alarms-id-deletes-an-alarm-config","eyebrow":"DELETE · InTouch Telematics · legacy-source","keywords":"/alarms/{id} DELETE InTouch alarm stateful retire"},{"id":"api:intouch-post-alarms-id-updates-an-alarm-config","kind":"API","title":"Updates An Alarm Config","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-post-alarms-id-updates-an-alarm-config","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/alarms/{id} POST InTouch alarm stateful command"},{"id":"api:intouch-get-devices-info-gets-the-basic-info-of-devices","kind":"API","title":"Gets the basic info of devices.","description":"This API returns the basic info of devices such as their registration number, tyre size, manufacturer etc.","href":"/api-reference/intouch-get-devices-info-gets-the-basic-info-of-devices","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/devices/info GET InTouch device basic info stateful observe"},{"id":"api:intouch-get-devices-hardwareinfo-gets-the-hardware-info-of-devices","kind":"API","title":"Gets the hardware info of devices.","description":"This API returns the hardware related info of devices such as their IMEI number, GSM number etc.","href":"/api-reference/intouch-get-devices-hardwareinfo-gets-the-hardware-info-of-devices","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/devices/hardwareinfo GET InTouch device hardware info stateful observe"},{"id":"api:intouch-get-devices-gets-the-live-data-of-devices","kind":"API","title":"Gets the live data of devices.","description":"This API returns accurate live location and related data of vehicles, assets & people with help of connected devices/sensors/mobiles to provide location awareness to users of your app. The API provides real-time visibility of your tracked objects, giving not just location information, but multiple additional fields which add value to your application. The API is capable of being used for multiple use cases: be it for transport - logistics or for personnel information services for all kinds of web or mobile development platforms.","href":"/api-reference/intouch-get-devices-gets-the-live-data-of-devices","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/devices GET InTouch device live data getDeviceById stateful observe"},{"id":"api:intouch-get-device-gets-the-live-data-of-devices","kind":"API","title":"Gets the live data of devices.","description":"This API returns accurate live location and related data of vehicles, assets & people with help of connected devices/sensors/mobiles to provide location awareness to users of your app. The API provides real-time visibility of your tracked objects, giving not just location information, but multiple additional fields which add value to your application. The API is capable of being used for multiple use cases: be it for transport - logistics or for personnel information services for all kinds of web or mobile development platforms.","href":"/api-reference/intouch-get-device-gets-the-live-data-of-devices","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/device GET InTouch devices getDeviceById stateful observe"},{"id":"api:intouch-get-device-drive-gets-drive-details-of-a-device","kind":"API","title":"Gets drive details of a device.","description":"This API is used to request the drive details of a vehicle in an account on our telematics platform. A vehicle can be a device/sensor connected to our telematics platform directly or via a third party data aggregator who utilises our telematics platform for tracking services. Drive is a list of reported geo-positions of any object (such as vehicles, assets or people) according to pre-defined conditions","href":"/api-reference/intouch-get-device-drive-gets-drive-details-of-a-device","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/device/drive GET InTouch drives getDrives stateful observe"},{"id":"api:intouch-get-devices-drives-gets-drive-details-of-a-device","kind":"API","title":"Gets drive details of a device.","description":"This API is used to request the drive details of a vehicle in an account on our telematics platform. A vehicle can be a device/sensor connected to our telematics platform directly or via a third party data aggregator who utilises our telematics platform for tracking services. Drive is a list of reported geo-positions of any object (such as vehicles, assets or people) according to pre-defined conditions","href":"/api-reference/intouch-get-devices-drives-gets-drive-details-of-a-device","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/devices/drives GET InTouch drives getDrives stateful observe"},{"id":"api:intouch-get-device-deviceid-events-gets-the-historical-location-events-of-a-device","kind":"API","title":"Gets the historical location events of a device.","description":"This API is used to get the historical location information as well as related additional information for a vehicle. This API can be used thus to create customized reports for users of your apps for different use cases, e.g.: plot the vehicle's past movements on map or get a historical graph of change in a vehicle's altitude.","href":"/api-reference/intouch-get-device-deviceid-events-gets-the-historical-location-events-of-a-device","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/device/{deviceId}/events GET InTouch events getLocationEvents stateful observe"},{"id":"api:intouch-get-devices-deviceid-events-gets-the-historical-location-events-of-a-device","kind":"API","title":"Gets the historical location events of a device.","description":"This API is used to get the historical location information as well as related additional information for a vehicle. This API can be used thus to create customized reports for users of your apps for different use cases, e.g.: plot the vehicle's past movements on map or get a historical graph of change in a vehicle's altitude.","href":"/api-reference/intouch-get-devices-deviceid-events-gets-the-historical-location-events-of-a-device","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/devices/{deviceId}/events GET InTouch events getLocationEvents stateful observe"},{"id":"api:intouch-get-geofence-gets-all-the-configured-geofence-s-v1-0-0","kind":"API","title":"Gets All The Configured Geofence(s)","description":"This API returns the list of all the configured geofences","href":"/api-reference/intouch-get-geofence-gets-all-the-configured-geofence-s-v1-0-0","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/geofence/ GET InTouch geofence stateful observe"},{"id":"api:intouch-get-geofence-gets-all-the-configured-geofence-s","kind":"API","title":"Gets All The Configured Geofence(s)","description":"This API returns the list of all the configured geofences","href":"/api-reference/intouch-get-geofence-gets-all-the-configured-geofence-s","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/geofence/ GET InTouch geofence stateful observe"},{"id":"api:intouch-post-geofence-create-a-new-geofence-v1-0-0","kind":"API","title":"Create A New Geofence","description":"This API helps to create a new geofence","href":"/api-reference/intouch-post-geofence-create-a-new-geofence-v1-0-0","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/geofence/ POST InTouch geofence stateful command"},{"id":"api:intouch-post-geofence-create-a-new-geofence","kind":"API","title":"Create A New Geofence","description":"This API helps to create a new geofence","href":"/api-reference/intouch-post-geofence-create-a-new-geofence","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/geofence/ POST InTouch geofence stateful command"},{"id":"api:intouch-get-geofence-activity-get-all-the-activities-done-by-devices-w-r-t-various-geofences","kind":"API","title":"Get all the activities done by devices w.r.t various geofences","description":"This API helps to fetch the details of all the activities, such as geofence entry time, exit time etc, which devices perform w.r.t various geofences across a defined date/time range.","href":"/api-reference/intouch-get-geofence-activity-get-all-the-activities-done-by-devices-w-r-t-various-geofences","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/geofence/activity GET InTouch geofence stateful observe"},{"id":"api:intouch-delete-geofence-id-delete-a-geofence-v1-0-0","kind":"API","title":"Delete A Geofence.","description":"This API helps to delete a geofence.","href":"/api-reference/intouch-delete-geofence-id-delete-a-geofence-v1-0-0","eyebrow":"DELETE · InTouch Telematics · legacy-source","keywords":"/geofence/{id} DELETE InTouch geofence stateful retire"},{"id":"api:intouch-delete-geofence-id-delete-a-geofence","kind":"API","title":"Delete A Geofence.","description":"This API helps to delete a geofence.","href":"/api-reference/intouch-delete-geofence-id-delete-a-geofence","eyebrow":"DELETE · InTouch Telematics · legacy-source","keywords":"/geofence/{id} DELETE InTouch geofence stateful retire"},{"id":"api:intouch-get-geofence-id-get-a-single-or-multiple-geofence-s-v1-0-0","kind":"API","title":"Get A Single Or Multiple Geofence(s).","description":"This API helps to fetch the details of a particular geofence","href":"/api-reference/intouch-get-geofence-id-get-a-single-or-multiple-geofence-s-v1-0-0","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/geofence/{id} GET InTouch geofence stateful observe"},{"id":"api:intouch-get-geofence-id-get-a-single-or-multiple-geofence-s","kind":"API","title":"Get A Single Or Multiple Geofence(s).","description":"This API helps to fetch the details of a particular geofence","href":"/api-reference/intouch-get-geofence-id-get-a-single-or-multiple-geofence-s","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/geofence/{id} GET InTouch geofence stateful observe"},{"id":"api:intouch-post-geofence-id-update-a-geofence-v1-0-0","kind":"API","title":"Update A Geofence.","description":"This API helps to update a particular geofence.","href":"/api-reference/intouch-post-geofence-id-update-a-geofence-v1-0-0","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/geofence/{id} POST InTouch geofence stateful command"},{"id":"api:intouch-post-geofence-id-update-a-geofence","kind":"API","title":"Update A Geofence.","description":"This API helps to update a particular geofence.","href":"/api-reference/intouch-post-geofence-id-update-a-geofence","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/geofence/{id} POST InTouch geofence stateful command"},{"id":"api:intouch-get-geofences-gets-all-the-configured-geofence-s","kind":"API","title":"Gets All The Configured Geofence(s)","description":"This API returns the list of all the configured geofences","href":"/api-reference/intouch-get-geofences-gets-all-the-configured-geofence-s","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/geofences GET InTouch geofence stateful observe"},{"id":"api:intouch-post-geofences-create-a-new-geofence","kind":"API","title":"Create A New Geofence","description":"This API helps to create a new geofence","href":"/api-reference/intouch-post-geofences-create-a-new-geofence","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/geofences POST InTouch geofence stateful command"},{"id":"api:intouch-get-geofences-activities-get-all-the-activities-done-by-devices-w-r-t-various-geofences","kind":"API","title":"Get all the activities done by devices w.r.t various geofences","description":"This API helps to fetch the details of all the activities, such as geofence entry time, exit time etc, which devices perform w.r.t various geofences across a defined date/time range.","href":"/api-reference/intouch-get-geofences-activities-get-all-the-activities-done-by-devices-w-r-t-various-geofences","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/geofences/activities GET InTouch geofence stateful observe"},{"id":"api:intouch-delete-geofences-id-delete-a-geofence","kind":"API","title":"Delete A Geofence.","description":"This API helps to delete a geofence.","href":"/api-reference/intouch-delete-geofences-id-delete-a-geofence","eyebrow":"DELETE · InTouch Telematics · legacy-source","keywords":"/geofences/{id} DELETE InTouch geofence stateful retire"},{"id":"api:intouch-get-geofences-id-get-a-single-or-multiple-geofence-s","kind":"API","title":"Get A Single Or Multiple Geofence(s).","description":"This API helps to fetch the details of a particular geofence","href":"/api-reference/intouch-get-geofences-id-get-a-single-or-multiple-geofence-s","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/geofences/{id} GET InTouch geofence stateful observe"},{"id":"api:intouch-post-geofences-id-update-a-geofence","kind":"API","title":"Update A Geofence.","description":"This API helps to update a particular geofence.","href":"/api-reference/intouch-post-geofences-id-update-a-geofence","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/geofences/{id} POST InTouch geofence stateful command"},{"id":"api:intouch-get-group-this-api-will-get-all-the-groups-for-a-user","kind":"API","title":"This API will get all the groups for a user.","description":"Based on the passed token key, the API will return the list of all groups.","href":"/api-reference/intouch-get-group-this-api-will-get-all-the-groups-for-a-user","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/group GET InTouch group stateful observe"},{"id":"api:intouch-post-group-this-api-will-create-a-group","kind":"API","title":"This API will create a group.","description":"Based on the input parameters provided to this POST group API, a new group will get created for a single or multiple devices","href":"/api-reference/intouch-post-group-this-api-will-create-a-group","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/group POST InTouch group stateful command"},{"id":"api:intouch-delete-group-id-deletes-a-group","kind":"API","title":"Deletes a group","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-delete-group-id-deletes-a-group","eyebrow":"DELETE · InTouch Telematics · legacy-source","keywords":"/group/{id} DELETE InTouch group stateful retire"},{"id":"api:intouch-post-group-id-updates-a-group","kind":"API","title":"Updates a group","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-post-group-id-updates-a-group","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/group/{id} POST InTouch group stateful command"},{"id":"api:intouch-get-groups-this-api-will-get-all-the-groups-for-a-user","kind":"API","title":"This API will get all the groups for a user.","description":"Based on the passed token key, the API will return the list of all groups.","href":"/api-reference/intouch-get-groups-this-api-will-get-all-the-groups-for-a-user","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/groups GET InTouch group stateful observe"},{"id":"api:intouch-post-groups-this-api-will-create-a-group","kind":"API","title":"This API will create a group.","description":"Based on the input parameters provided to this POST group API, a new group will get created for a single or multiple devices","href":"/api-reference/intouch-post-groups-this-api-will-create-a-group","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/groups POST InTouch group stateful command"},{"id":"api:intouch-delete-groups-id-deletes-a-group","kind":"API","title":"Deletes a group","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-delete-groups-id-deletes-a-group","eyebrow":"DELETE · InTouch Telematics · legacy-source","keywords":"/groups/{id} DELETE InTouch group stateful retire"},{"id":"api:intouch-post-groups-id-updates-a-group","kind":"API","title":"Updates a group","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-post-groups-id-updates-a-group","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/groups/{id} POST InTouch group stateful command"},{"id":"api:intouch-get-devices-nearby-gets-the-list-of-all-the-nearby-devices","kind":"API","title":"Gets the list of all the nearby devices.","description":"This API returns accurate live location and related data of all the nearby vehicles, assets & people, within the specified buffer range, with help of connected devices/sensors/mobiles to provide location awareness to users of your app. The API provides real-time visibility of your tracked objects, giving not just location information, but multiple additional fields which add value to your application. The API is capable of being used for multiple use cases: be it for transport - logistics or for personnel information services for all kinds of web or mobile development platforms.","href":"/api-reference/intouch-get-devices-nearby-gets-the-list-of-all-the-nearby-devices","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/devices/nearby GET InTouch nearby stateful observe"},{"id":"api:intouch-get-trips-this-api-will-get-all-the-trips-for-a-user","kind":"API","title":"This API will get all the trips for a user.","description":"Based on the passed token key, the API will return the list of all the trips.","href":"/api-reference/intouch-get-trips-this-api-will-get-all-the-trips-for-a-user","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/trips GET InTouch trips stateful observe"},{"id":"api:intouch-post-trips-this-api-will-create-a-trip","kind":"API","title":"This API will create a trip.","description":"Based on the input parameters provided, a new trip will get created.","href":"/api-reference/intouch-post-trips-this-api-will-create-a-trip","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/trips POST InTouch trips stateful command"},{"id":"api:intouch-get-trips-id-gets-the-details-of-a-single-trip","kind":"API","title":"Gets the details of a single trip","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-get-trips-id-gets-the-details-of-a-single-trip","eyebrow":"GET · InTouch Telematics · legacy-source","keywords":"/trips/{id} GET InTouch trips stateful observe"},{"id":"api:intouch-post-trips-id-close-post-api-to-close-a-trip","kind":"API","title":"POST API to close a trip.","description":"A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch","href":"/api-reference/intouch-post-trips-id-close-post-api-to-close-a-trip","eyebrow":"POST · InTouch Telematics · legacy-source","keywords":"/trips/{id}/close POST InTouch trips stateful command"},{"id":"api:mappls-ai-ml-post-blurbox-returns-the-image-in-which-objects-of-geometry-are-blurred-as-given-by-the-client","kind":"API","title":"Returns the image in which objects of geometry are blurred as given by the client.","description":"BlurBox API takes in the bounding box ( the region, area the client want to blur in the image) and then the BlurBox will automatically return the blur region within an image.","href":"/api-reference/mappls-ai-ml-post-blurbox-returns-the-image-in-which-objects-of-geometry-are-blurred-as-given-by-the-client","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/blurbox POST AI & Vision Blurring Bbox blurbox hybrid command"},{"id":"api:mappls-ai-ml-post-brand-detection-returns-the-brands-bounding-box-array-for-the-inputs-images","kind":"API","title":"Returns the Brands bounding box array for the inputs Images","description":"API will predict the bounding box co-ordinates(x1, y1, x2, y2) i.e (left most coordinate, right most coordinate) of the Brands in the given image.","href":"/api-reference/mappls-ai-ml-post-brand-detection-returns-the-brands-bounding-box-array-for-the-inputs-images","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/brand_detection POST AI & Vision Brands Detection APIs describeDatasetGet hybrid command"},{"id":"api:mappls-ai-ml-post-faceblur-returns-the-array-of-features-which-contains-objects-of-geometry-of-the-uploaded-image","kind":"API","title":"Returns the array of features which contains objects of geometry of the uploaded image.","description":"Face Blur API can automatically detect all faces within an image and blurs them. No need for manual face selection.","href":"/api-reference/mappls-ai-ml-post-faceblur-returns-the-array-of-features-which-contains-objects-of-geometry-of-the-uploaded-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/faceblur POST AI & Vision Face Detection and Blurring faceBlur hybrid command"},{"id":"api:mappls-ai-ml-post-facedetection-returns-different-output-depending-upon-the-inputs-given","kind":"API","title":"Returns different output depending upon the inputs given.","description":"Using these APIs developers can fully leverage and embed the power of AI / ML Analytics, intelligence. These APIs allow our client to integrate into their own application the power and full set of functionalities of the mGIS product and platform. It’s a fact: people have a right of getting digital privacy. Here’s one more: online publishers and businesses worldwide must respect those rights and provide visual anonymity when it’s needed. That’s why we decided to give you the fastest and easiest way to keep people’s privacy in photos. Meet Face Detection & Blurring by MapmyIndia. This tool completely automates Face Detection, Face Blurring in photos and helps you get the job done in just a few clicks without graphic editors and manual work. Keep reading to find out how it works, when it comes in handy, and how you can actually use it in MapmyIndia.","href":"/api-reference/mappls-ai-ml-post-facedetection-returns-different-output-depending-upon-the-inputs-given","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/facedetection POST AI & Vision Face Detection and Blurring faceDetection hybrid command"},{"id":"api:mappls-ai-ml-post-faceplot-returns-the-image-which-contains-objects-of-geometry-of-the-detected-face-plotted-on-it-with-the-bounding-box","kind":"API","title":"Returns the image which contains objects of geometry of the detected face plotted on it with the bounding box.","description":"This tool completely automates Face Detection, Face Blurring in photos and helps you get the job done in just a few clicks without graphic editors and manual work. Keep reading to find out how it works, when it comes in handy, and how you can actually use it in MapmyIndia. You can detect faces in an image, identify key facial features, and get the contours of detected faces. Note that the API detects faces, it does not recognize people . When you have face contour detection enabled, you also get a list of points for each facial feature that was detected. These points represent the shape of the feature. The following image illustrates how these points map to a face.","href":"/api-reference/mappls-ai-ml-post-faceplot-returns-the-image-which-contains-objects-of-geometry-of-the-detected-face-plotted-on-it-with-the-bounding-box","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/faceplot POST AI & Vision Face Detection and Blurring facePlot hybrid command"},{"id":"api:mappls-ai-ml-post-face-blur-returns-the-face-blured-images-of-the-uploaded-2d-image","kind":"API","title":"Returns the face blured images of the uploaded 2D image","description":"This API completely automates Face Detection, Face Blurring in 2D Images, without any extra effort","href":"/api-reference/mappls-ai-ml-post-face-blur-returns-the-face-blured-images-of-the-uploaded-2d-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/face_blur POST AI & Vision Face Detection and Blurring 2D API describeDataset1 hybrid command"},{"id":"api:mappls-ai-ml-post-face-detection-returns-the-bounding-box-array-for-the-inputs-image","kind":"API","title":"Returns the bounding box array for the inputs Image","description":"API will predict the bounding box co-ordinates(x1, y1, x2, y2) i.e (left most coordinate, right most coordinate) of the faces in the given 2D image.","href":"/api-reference/mappls-ai-ml-post-face-detection-returns-the-bounding-box-array-for-the-inputs-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/face_detection POST AI & Vision Face Detection and Blurring 2D API describeDatasetGet hybrid command"},{"id":"api:mappls-ai-ml-post-face-draw-returns-the-box-drawn-faces-on-the-uploaded-2d-image","kind":"API","title":"Returns the box drawn faces on the uploaded 2D image","description":"This API detects faces in 2D images and draw their box around faces.","href":"/api-reference/mappls-ai-ml-post-face-draw-returns-the-box-drawn-faces-on-the-uploaded-2d-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/face_draw POST AI & Vision Face Detection and Blurring 2D API describeDataset2 hybrid command"},{"id":"api:mappls-ai-ml-post-face-blur-pano-returns-the-face-blured-images-of-the-uploaded-panorama-image","kind":"API","title":"Returns the face blured images of the uploaded panorama image","description":"This API completely automates Face Detection, Face Blurring in panorama Images, without any extra effort","href":"/api-reference/mappls-ai-ml-post-face-blur-pano-returns-the-face-blured-images-of-the-uploaded-panorama-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/face_blur_pano POST AI & Vision Face Detection and Blurring 360 APIs describeDataset1 hybrid command"},{"id":"api:mappls-ai-ml-post-face-detection-pano-returns-the-bounding-box-array-for-the-inputs-panorama-images","kind":"API","title":"Returns the bounding box array for the inputs panorama Images","description":"API will predict the bounding box co-ordinates(x1, y1, x2, y2) i.e (left most coordinate, right most coordinate) of the faces in the given panorama image.","href":"/api-reference/mappls-ai-ml-post-face-detection-pano-returns-the-bounding-box-array-for-the-inputs-panorama-images","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/face_detection_pano POST AI & Vision Face Detection and Blurring 360 APIs describeDatasetGet hybrid command"},{"id":"api:mappls-ai-ml-post-face-draw-pano-returns-the-box-drawn-faces-on-the-uploaded-panorama-image","kind":"API","title":"Returns the box drawn faces on the uploaded panorama image","description":"Without any additional effort, This API detects faces in panorama images and draw their box around faces.","href":"/api-reference/mappls-ai-ml-post-face-draw-pano-returns-the-box-drawn-faces-on-the-uploaded-panorama-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/face_draw_pano POST AI & Vision Face Detection and Blurring 360 APIs describeDataset2 hybrid command"},{"id":"api:mappls-ai-ml-post-license-plate-blur-returns-the-license-plate-blured-images-of-the-uploaded-2d-image","kind":"API","title":"Returns the License Plate blured images of the uploaded 2D image","description":"This API completely automates License Plate Detection, License Plate Blurring in 2D Images, without any extra effort","href":"/api-reference/mappls-ai-ml-post-license-plate-blur-returns-the-license-plate-blured-images-of-the-uploaded-2d-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/license_plate_blur POST AI & Vision License Plate Detection and Blurring 2D API describeDataset1 hybrid command"},{"id":"api:mappls-ai-ml-post-license-plate-detection-returns-the-bounding-box-array-for-the-inputs-image","kind":"API","title":"Returns the bounding box array for the inputs Image","description":"API will predict the bounding box co-ordinates(x1, y1, x2, y2) i.e (left most coordinate, right most coordinate) of the License Plate in the given 2D image.","href":"/api-reference/mappls-ai-ml-post-license-plate-detection-returns-the-bounding-box-array-for-the-inputs-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/license_plate_detection POST AI & Vision License Plate Detection and Blurring 2D API describeDatasetGet hybrid command"},{"id":"api:mappls-ai-ml-post-license-plate-draw-returns-the-box-drawn-license-plate-on-the-uploaded-2d-image","kind":"API","title":"Returns the box drawn License Plate on the uploaded 2D image","description":"This API detects License Plate in 2D images and draw their box around License Plate.","href":"/api-reference/mappls-ai-ml-post-license-plate-draw-returns-the-box-drawn-license-plate-on-the-uploaded-2d-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/license_plate_draw POST AI & Vision License Plate Detection and Blurring 2D API describeDataset2 hybrid command"},{"id":"api:mappls-ai-ml-post-license-plate-blur-pano-returns-the-license-plate-blured-images-of-the-uploaded-panorama-image","kind":"API","title":"Returns the License plate blured images of the uploaded panorama image","description":"This API completely automates License plate Detection, License plate Blurring in panorama Images, without any extra effort","href":"/api-reference/mappls-ai-ml-post-license-plate-blur-pano-returns-the-license-plate-blured-images-of-the-uploaded-panorama-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/license_plate_blur_pano POST AI & Vision License Plate Detection and Blurring 360 APIs describeDataset1 hybrid command"},{"id":"api:mappls-ai-ml-post-license-plate-detection-pano-returns-the-bounding-box-array-of-license-plate-in-panorama-images","kind":"API","title":"Returns the bounding box array of License plate in panorama Images","description":"API will predict the bounding box co-ordinates(x1, y1, x2, y2) i.e (left most coordinate, right most coordinate) of the License Plate in the given panorama image.","href":"/api-reference/mappls-ai-ml-post-license-plate-detection-pano-returns-the-bounding-box-array-of-license-plate-in-panorama-images","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/license_plate_detection_pano POST AI & Vision License Plate Detection and Blurring 360 APIs describeDatasetGet hybrid command"},{"id":"api:mappls-ai-ml-post-license-plate-draw-pano-returns-the-box-drawn-license-plate-in-the-uploaded-panorama-image","kind":"API","title":"Returns the box drawn License plate in the uploaded panorama image","description":"Without any additional effort, This API detects License plate in panorama images and draw their box around License plate.","href":"/api-reference/mappls-ai-ml-post-license-plate-draw-pano-returns-the-box-drawn-license-plate-in-the-uploaded-panorama-image","eyebrow":"POST · Mappls AI / ML · source-snapshot","keywords":"/license_plate_draw_pano POST AI & Vision License Plate Detection and Blurring 360 APIs describeDataset2 hybrid command"},{"id":"api:mgis-get-aggregate-perform-aggregate-operation-on-a-single-dataset","kind":"API","title":"Perform aggregate operation on a single dataset","description":"Perform aggregate operation on a single dataset","href":"/api-reference/mgis-get-aggregate-perform-aggregate-operation-on-a-single-dataset","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/aggregate GET mGIS Dataset, Query and Validate (DQV) API aggregateOperationId stateful observe"},{"id":"api:mgis-get-catchement-query-join-fetches-the-results-of-the-query-applied-between-two-dataset-as-well-as-between-one-datset-and-user-defimed-geometry","kind":"API","title":"Fetches the results of the query applied between two dataset as well as between one datset and user defimed geometry.","description":"User can performed both the following tasks: Non Spatial Query Spatial Query For spatial query user can perform the query between 2 datasets as well as between one dataset and user defined geometry in geojson format. Whereas Non-Spatial Query is only applicable between 2 datasets.","href":"/api-reference/mgis-get-catchement-query-join-fetches-the-results-of-the-query-applied-between-two-dataset-as-well-as-between-one-datset-and-user-defimed-geometry","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/catchement_query/join GET mGIS Dataset, Query and Validate (DQV) API catchement_queryId stateful observe"},{"id":"api:mgis-get-dqv-aggregate-perform-aggregate-operation-on-a-single-dataset","kind":"API","title":"Perform aggregate operation on a single dataset","description":"Perform aggregate operation on a single dataset","href":"/api-reference/mgis-get-dqv-aggregate-perform-aggregate-operation-on-a-single-dataset","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/dqv/aggregate GET mGIS Dataset, Query and Validate (DQV) API aggregateOperationId stateful observe"},{"id":"api:mgis-get-dqv-catchement-query-join-fetches-the-results-of-the-query-applied-between-two-dataset-as-well-as-between-one-datset-and-user-defimed-geometry","kind":"API","title":"Fetches the results of the query applied between two dataset as well as between one datset and user defimed geometry.","description":"User can performed both the following tasks: Non Spatial Query Spatial Query For spatial query user can perform the query between 2 datasets as well as between one dataset and user defined geometry in geojson format. Whereas Non-Spatial Query is only applicable between 2 datasets.","href":"/api-reference/mgis-get-dqv-catchement-query-join-fetches-the-results-of-the-query-applied-between-two-dataset-as-well-as-between-one-datset-and-user-defimed-geometry","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/dqv/catchement_query/join GET mGIS Dataset, Query and Validate (DQV) API catchement_queryId stateful observe"},{"id":"api:mgis-get-dqv-expression-performs-arithmetic-geometric-aggregate-and-string-operations-on-column-s-of-a-dataset-passed-as-an-input","kind":"API","title":"Performs arithmetic,geometric,aggregate and string operations on column(s) of a dataset passed as an input.","description":"Performs arithmetic,string,geometric and aggregate operations on a column of a dataset passed as an input. Arithmetic operations are +, -, , /. String operations are concat, lower, upper, initcap, replace, length, substring. Geometric operations are area,length,latitude,longitude,centroid. Aggregate operations are count,min,max,median,stddev,sum,avg.","href":"/api-reference/mgis-get-dqv-expression-performs-arithmetic-geometric-aggregate-and-string-operations-on-column-s-of-a-dataset-passed-as-an-input","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/dqv/expression GET mGIS Dataset, Query and Validate (DQV) API expressionId stateful observe"},{"id":"api:mgis-get-dqv-geometricfunction-performs-geometric-operations","kind":"API","title":"Performs geometric operations.","description":"Performs geometric operations between two user-defined geometry as well as within the dataset. The geometric opertaions available for user defined geometry are (the brackets consists of the parameters to be passed while using the geometric function): Area (geom1) Centroid (geom1) Buffer (geom1, distance) Intersection (geom1, geom2) Distance (geom1, geom2) isEmpty (geom1) length (geom1) endPoint (geom1) (has to be a lineString or multiLineString) The geometric opertaions available for within dataset are: Area (geom1) Centroid (geom1) Buffer (geom1, distance) isEmpty (geom1) length (geom1) endPoint (geom1) (has to be a lineString or multiLineString)","href":"/api-reference/mgis-get-dqv-geometricfunction-performs-geometric-operations","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/dqv/geometricFunction GET mGIS Dataset, Query and Validate (DQV) API geometricFunctionID stateful observe"},{"id":"api:mgis-get-dqv-getboundingbox-returns-the-boundingbox-of-the-particular-layer","kind":"API","title":"Returns the BoundingBox of the particular layer.","description":"Returns the Bounding Box of the particular layer without cqlfilter and returns the bounding box of feature with cqlfilter.","href":"/api-reference/mgis-get-dqv-getboundingbox-returns-the-boundingbox-of-the-particular-layer","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/dqv/getBoundingBox GET mGIS Dataset, Query and Validate (DQV) API BoundingBoxID stateful observe"},{"id":"api:mgis-get-dqv-getdataset-fetches-the-entire-dataset","kind":"API","title":"Fetches the entire dataset.","description":"Fetches the entire dataset. You can perform 'order(sort) By' and 'groupBy' in 'query'. This has 3 cases: Only Order By Only Group By Both Order By and Group By together","href":"/api-reference/mgis-get-dqv-getdataset-fetches-the-entire-dataset","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/dqv/getDataset GET mGIS Dataset, Query and Validate (DQV) API getDatasetId stateful observe"},{"id":"api:mgis-post-dqv-query-apply-join-fetches-the-results-of-the-query-applied-between-two-dataset-as-well-as-between-one-datset-and-user-defimed-geometry","kind":"API","title":"Fetches the results of the query applied between two dataset as well as between one datset and user defimed geometry.","description":"User can performed both the following tasks: Non Spatial Query Spatial Query For spatial query user can perform the query between 2 datasets as well as between one dataset and user defined geometry in geojson format. Whereas Non-Spatial Query is only applicable between 2 datasets.","href":"/api-reference/mgis-post-dqv-query-apply-join-fetches-the-results-of-the-query-applied-between-two-dataset-as-well-as-between-one-datset-and-user-defimed-geometry","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/dqv/query_apply/join POST mGIS Dataset, Query and Validate (DQV) API applyQueryCrossId stateful command"},{"id":"api:mgis-post-dqv-query-apply-single-fetches-the-results-of-the-query-applied-on-the-single-dataset-you-cannot-pass-query-summerizevalue-and-uniquevalue-paramater-together","kind":"API","title":"Fetches the results of the query applied on the single dataset. You cannot pass query, summerizeValue and uniqueValue paramater together.","description":"You cannot pass query, summerizeValue and uniqueValue paramater together. You can perform 'order(sort) By' and 'groupBy' in 'query'. This has 3 cases: Only Order By Only Group By Both Order By and Group By together You can perform geometric operation (area and length) when queryType = 'functionBased' is passed. The query parameter is an optional paramater in this case. summerizeValue and uniqueValue paramater are not applicable in this case.","href":"/api-reference/mgis-post-dqv-query-apply-single-fetches-the-results-of-the-query-applied-on-the-single-dataset-you-cannot-pass-query-summerizevalue-and-uniquevalue-paramater-together","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/dqv/query_apply/single POST mGIS Dataset, Query and Validate (DQV) API applyQuerySingleId stateful command"},{"id":"api:mgis-get-dqv-query-validation-validates-the-query-to-be-applied-on-a-dataset","kind":"API","title":"Validates the query to be applied on a dataset.","description":"Validates the query to be applied on a dataset.","href":"/api-reference/mgis-get-dqv-query-validation-validates-the-query-to-be-applied-on-a-dataset","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/dqv/query_validation GET mGIS Dataset, Query and Validate (DQV) API queryValidateId stateful observe"},{"id":"api:mgis-get-expression-performs-arithmetic-geometric-aggregate-and-string-operations-on-column-s-of-a-dataset-passed-as-an-input","kind":"API","title":"Performs arithmetic,geometric,aggregate and string operations on column(s) of a dataset passed as an input.","description":"Performs arithmetic,string,geometric and aggregate operations on a column of a dataset passed as an input. Arithmetic operations are +, -, , /. String operations are concat, lower, upper, initcap, replace, length, substring. Geometric operations are area,length,latitude,longitude,centroid. Aggregate operations are count,min,max,median,stddev,sum,avg.","href":"/api-reference/mgis-get-expression-performs-arithmetic-geometric-aggregate-and-string-operations-on-column-s-of-a-dataset-passed-as-an-input","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/expression GET mGIS Dataset, Query and Validate (DQV) API expressionId stateful observe"},{"id":"api:mgis-get-geometricfunction-performs-geometric-operations","kind":"API","title":"Performs geometric operations.","description":"Performs geometric operations between two user-defined geometry as well as within the dataset. The geometric opertaions available for user defined geometry are (the brackets consists of the parameters to be passed while using the geometric function): Area (geom1) Centroid (geom1) Buffer (geom1, distance) Intersection (geom1, geom2) Distance (geom1, geom2) isEmpty (geom1) length (geom1) endPoint (geom1) (has to be a lineString or multiLineString) The geometric opertaions available for within dataset are: Area (geom1) Centroid (geom1) Buffer (geom1, distance) isEmpty (geom1) length (geom1) endPoint (geom1) (has to be a lineString or multiLineString)","href":"/api-reference/mgis-get-geometricfunction-performs-geometric-operations","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/geometricFunction GET mGIS Dataset, Query and Validate (DQV) API geometricFunctionID stateful observe"},{"id":"api:mgis-get-getboundingbox-returns-the-boundingbox-of-the-particular-layer","kind":"API","title":"Returns the BoundingBox of the particular layer.","description":"Returns the Bounding Box of the particular layer without cqlfilter and returns the bounding box of feature with cqlfilter.","href":"/api-reference/mgis-get-getboundingbox-returns-the-boundingbox-of-the-particular-layer","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/getBoundingBox GET mGIS Dataset, Query and Validate (DQV) API BoundingBoxID stateful observe"},{"id":"api:mgis-get-getdataset-fetches-the-entire-dataset","kind":"API","title":"Fetches the entire dataset.","description":"Fetches the entire dataset. You can perform 'order(sort) By' and 'groupBy' in 'query'. This has 3 cases: Only Order By Only Group By Both Order By and Group By together","href":"/api-reference/mgis-get-getdataset-fetches-the-entire-dataset","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/getDataset GET mGIS Dataset, Query and Validate (DQV) API getDatasetId stateful observe"},{"id":"api:mgis-get-getgeometry-returns-the-geometry-of-the-particular-layer-on-the-basis-of-the-featureid-provided-by-the-user","kind":"API","title":"Returns the geometry of the particular layer on the basis of the featureID provided by the user.","description":"Returns the geometry of the particular layer on the basis of the featureID or filter provided by the user.(Any one of the filter or featureID can be provided)","href":"/api-reference/mgis-get-getgeometry-returns-the-geometry-of-the-particular-layer-on-the-basis-of-the-featureid-provided-by-the-user","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/getGeometry GET mGIS Dataset, Query and Validate (DQV) API GetGeometryID stateful observe"},{"id":"api:mgis-post-query-apply-join-fetches-the-results-of-the-query-applied-between-two-dataset-as-well-as-between-one-datset-and-user-defimed-geometry","kind":"API","title":"Fetches the results of the query applied between two dataset as well as between one datset and user defimed geometry.","description":"User can performed both the following tasks: Non Spatial Query Spatial Query For spatial query user can perform the query between 2 datasets as well as between one dataset and user defined geometry in geojson format. Whereas Non-Spatial Query is only applicable between 2 datasets.","href":"/api-reference/mgis-post-query-apply-join-fetches-the-results-of-the-query-applied-between-two-dataset-as-well-as-between-one-datset-and-user-defimed-geometry","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/query_apply/join POST mGIS Dataset, Query and Validate (DQV) API applyQueryCrossId stateful command"},{"id":"api:mgis-post-query-apply-single-fetches-the-results-of-the-query-applied-on-the-single-dataset-you-cannot-pass-query-summerizevalue-and-uniquevalue-paramater-together","kind":"API","title":"Fetches the results of the query applied on the single dataset. You cannot pass query, summerizeValue and uniqueValue paramater together.","description":"You cannot pass query, summerizeValue and uniqueValue paramater together. You can perform 'order(sort) By' and 'groupBy' in 'query'. This has 3 cases: Only Order By Only Group By Both Order By and Group By together You can perform geometric operation (area and length) when queryType = 'functionBased' is passed. The query parameter is an optional paramater in this case. summerizeValue and uniqueValue paramater are not applicable in this case.","href":"/api-reference/mgis-post-query-apply-single-fetches-the-results-of-the-query-applied-on-the-single-dataset-you-cannot-pass-query-summerizevalue-and-uniquevalue-paramater-together","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/query_apply/single POST mGIS Dataset, Query and Validate (DQV) API applyQuerySingleId stateful command"},{"id":"api:mgis-get-query-validation-validates-the-query-to-be-applied-on-a-dataset","kind":"API","title":"Validates the query to be applied on a dataset.","description":"Validates the query to be applied on a dataset.","href":"/api-reference/mgis-get-query-validation-validates-the-query-to-be-applied-on-a-dataset","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/query_validation GET mGIS Dataset, Query and Validate (DQV) API queryValidateId stateful observe"},{"id":"api:mgis-get-describedataset-fetches-the-attribute-names-v1","kind":"API","title":"fetches the attribute names.","description":"Fetches the attribute names of the dataset except geometry in response.","href":"/api-reference/mgis-get-describedataset-fetches-the-attribute-names-v1","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/describeDataset GET mGIS Describe Dataset API describeDatasetGet stateful observe"},{"id":"api:mgis-get-describedataset-fetches-the-attribute-names","kind":"API","title":"fetches the attribute names.","description":"Fetches the attribute names of the dataset except geometry in response.","href":"/api-reference/mgis-get-describedataset-fetches-the-attribute-names","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/describeDataset GET mGIS Describe Dataset API describeDatasetGet stateful observe"},{"id":"api:mgis-get-export-feature-download-the-dataset-files-in-kml-shp-or-geojson-files-on-server","kind":"API","title":"Download the dataset files in .kml, .shp or .geojson files on server.","description":"Download the dataset files in .kml, .shp or .geojson files on server.","href":"/api-reference/mgis-get-export-feature-download-the-dataset-files-in-kml-shp-or-geojson-files-on-server","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/export_feature GET mGIS Export Feature API getLegendsImgId stateful observe"},{"id":"api:mgis-get-getgeometrytype-fetches-geometry-type-of-datasetnme","kind":"API","title":"Fetches Geometry type of datasetNme","description":"Fetches Geometry type of datasetNme includes vector and raster both.","href":"/api-reference/mgis-get-getgeometrytype-fetches-geometry-type-of-datasetnme","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/getGeometryType GET mGIS Get Feature Centroid/ Geometry Type API getgeometryID stateful observe"},{"id":"api:mgis-get-getgeometrytype-fetches-geometry-type-of-datasetnme-v1","kind":"API","title":"Fetches Geometry type of datasetNme","description":"Fetches Geometry type of datasetNme","href":"/api-reference/mgis-get-getgeometrytype-fetches-geometry-type-of-datasetnme-v1","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/getGeometryType GET mGIS Get Geometry Type API getgeometryID stateful observe"},{"id":"api:mgis-get-map-getfeatureinfo-fetches-the-feature-information-v1","kind":"API","title":"Fetches the feature information.","description":"Fetches the feature information of the dataset name of a bounding box.","href":"/api-reference/mgis-get-map-getfeatureinfo-fetches-the-feature-information-v1","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/map/getFeatureInfo GET mGIS Get Map and Get Feature Info API getFeatureInfoId stateful observe"},{"id":"api:mgis-get-map-getfeatureinfo-fetches-the-feature-information","kind":"API","title":"Fetches the feature information.","description":"Fetches the feature information of the dataset name of a bounding box.","href":"/api-reference/mgis-get-map-getfeatureinfo-fetches-the-feature-information","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/map/getFeatureInfo GET mGIS Get Map and Get Feature Info API getFeatureInfoId stateful observe"},{"id":"api:mgis-get-map-getlayerjoin-fetches-the-maptiles-of-the-dataset-name-of-a-bounding-box-for-spatial-join-between-2-datasets-as-well-as-between-one-dataset-and-userdefined-geometry-v1","kind":"API","title":"Fetches the maptiles of the dataset name of a bounding box for Spatial Join between 2 datasets as well as between one dataset and userDefined geometry.","description":"Fetches the maptiles of the dataset name of a bounding box for Spatial Join between 2 datasets as well as between one dataset and userDefined geometry.","href":"/api-reference/mgis-get-map-getlayerjoin-fetches-the-maptiles-of-the-dataset-name-of-a-bounding-box-for-spatial-join-between-2-datasets-as-well-as-between-one-dataset-and-userdefined-geometry-v1","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/map/getLayerJoin GET mGIS Get Map and Get Feature Info API stateful observe"},{"id":"api:mgis-get-map-getlayerjoin-fetches-the-maptiles-of-the-dataset-name-of-a-bounding-box-for-spatial-join-between-2-datasets-as-well-as-between-one-dataset-and-userdefined-geometry","kind":"API","title":"Fetches the maptiles of the dataset name of a bounding box for Spatial Join between 2 datasets as well as between one dataset and userDefined geometry.","description":"Fetches the maptiles of the dataset name of a bounding box for Spatial Join between 2 datasets as well as between one dataset and userDefined geometry.","href":"/api-reference/mgis-get-map-getlayerjoin-fetches-the-maptiles-of-the-dataset-name-of-a-bounding-box-for-spatial-join-between-2-datasets-as-well-as-between-one-dataset-and-userdefined-geometry","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/map/getLayerJoin GET mGIS Get Map and Get Feature Info API stateful observe"},{"id":"api:mgis-get-map-getmap-fetches-the-maptiles-of-the-dataset-name-of-a-bounding-box-v1","kind":"API","title":"Fetches the maptiles of the dataset name of a bounding box.","description":"Fetches the maptiles of the dataset name of a bounding box in response.","href":"/api-reference/mgis-get-map-getmap-fetches-the-maptiles-of-the-dataset-name-of-a-bounding-box-v1","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/map/getMap GET mGIS Get Map and Get Feature Info API getMapId stateful observe"},{"id":"api:mgis-get-map-getmap-fetches-the-maptiles-of-the-dataset-name-of-a-bounding-box","kind":"API","title":"Fetches the maptiles of the dataset name of a bounding box.","description":"Fetches the maptiles of the dataset name of a bounding box in response.","href":"/api-reference/mgis-get-map-getmap-fetches-the-maptiles-of-the-dataset-name-of-a-bounding-box","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/map/getMap GET mGIS Get Map and Get Feature Info API getMapId stateful observe"},{"id":"api:mgis-get-getlayerslist-fetches-the-names-of-all-the-datasets-available-in-the-user-s-workspace-on-the-geoserver-v1","kind":"API","title":"Fetches the names of all the datasets available in the user's workspace on the geoserver.","description":"Fetches the names of all the datasets available in the user's workspace on the geoserver.","href":"/api-reference/mgis-get-getlayerslist-fetches-the-names-of-all-the-datasets-available-in-the-user-s-workspace-on-the-geoserver-v1","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/getLayersList GET mGIS L3 (Layer List and Legends) API getLayersListId stateful observe"},{"id":"api:mgis-get-getlayerslist-fetches-the-names-of-all-the-datasets-available-in-the-user-s-workspace-on-the-geoserver","kind":"API","title":"Fetches the names of all the datasets available in the user's workspace on the geoserver.","description":"Fetches the names of all the datasets available in the user's workspace on the geoserver.","href":"/api-reference/mgis-get-getlayerslist-fetches-the-names-of-all-the-datasets-available-in-the-user-s-workspace-on-the-geoserver","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/getLayersList GET mGIS L3 (Layer List and Legends) API getLayersListId stateful observe"},{"id":"api:mgis-get-getlegendsimg-fetches-the-image-of-legends-for-the-given-dataset-v1","kind":"API","title":"Fetches the image of legends for the given dataset.","description":"Fetches the image of legends for the given dataset.","href":"/api-reference/mgis-get-getlegendsimg-fetches-the-image-of-legends-for-the-given-dataset-v1","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/getLegendsImg GET mGIS L3 (Layer List and Legends) API getLegendsImgId stateful observe"},{"id":"api:mgis-get-getlegendsimg-fetches-the-image-of-legends-for-the-given-dataset","kind":"API","title":"Fetches the image of legends for the given dataset.","description":"Fetches the image of legends for the given dataset.","href":"/api-reference/mgis-get-getlegendsimg-fetches-the-image-of-legends-for-the-given-dataset","eyebrow":"GET · mGIS Analytics · source-snapshot","keywords":"/getLegendsImg GET mGIS L3 (Layer List and Legends) API getLegendsImgId stateful observe"},{"id":"api:mgis-post-copy-style-copy-dataset-on-mgis-engine","kind":"API","title":"copy dataset on mGIS engine","description":"Creates a copy of an existing dataset and takes input of the dataset in the form of geojson and other parameters to create/publish dataset on mGIS engine, so that it can be used for manipulation/analysis/visualization on mGIS platform","href":"/api-reference/mgis-post-copy-style-copy-dataset-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/copy/style POST mGIS SAT API copydatasetPost stateful command"},{"id":"api:mgis-delete-deletefeature-deletes-the-feature-from-the-featurelist","kind":"API","title":"Deletes the feature from the featureList.","description":"Deletes the feature from the featureList on the basis of the filter value or the featureID value provided by the user.","href":"/api-reference/mgis-delete-deletefeature-deletes-the-feature-from-the-featurelist","eyebrow":"DELETE · mGIS Analytics · source-snapshot","keywords":"/deleteFeature DELETE mGIS SAT API DeleteFeature stateful retire"},{"id":"api:mgis-post-rename-style-rename-an-existing-dataset-on-mgis-engine","kind":"API","title":"Rename an existing dataset on mGIS engine","description":"Renames an existing dataset and takes input of the dataset in the form of geojson and other parameters to create/publish dataset on mGIS engine, so that it can be used for manipulation/analysis/visualization on mGIS platform","href":"/api-reference/mgis-post-rename-style-rename-an-existing-dataset-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/rename/style POST mGIS SAT API renamedatasetPost stateful command"},{"id":"api:mgis-post-sat-copy-style-duplicate-dataset-within-mgis-engine","kind":"API","title":"Duplicate dataset within mGIS engine.","description":"Produces a duplicate of an established dataset and accepts input in the form of geojson and additional parameters to generate/publish it on the mGIS engine, enabling its application for manipulation, analysis, and visualization within the mGIS platform.","href":"/api-reference/mgis-post-sat-copy-style-duplicate-dataset-within-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/sat/copy/style POST mGIS SAT API copydatasetPost stateful command"},{"id":"api:mgis-delete-sat-deletefeature-deletes-the-feature-from-the-featurelist","kind":"API","title":"Deletes the feature from the featureList.","description":"Deletes the feature from the featureList on the basis of the filter value or the featureID value provided by the user.","href":"/api-reference/mgis-delete-sat-deletefeature-deletes-the-feature-from-the-featurelist","eyebrow":"DELETE · mGIS Analytics · source-snapshot","keywords":"/sat/deleteFeature DELETE mGIS SAT API DeleteFeature stateful retire"},{"id":"api:mgis-post-sat-rename-style-rename-an-existing-dataset-on-mgis-engine","kind":"API","title":"Rename an existing dataset on mGIS engine","description":"Changes the name of an existing dataset, and accepts input in the form of geojson and additional parameters to generate/publish it on the mGIS engine. This facilitates its utilization for manipulation, analysis, and visualization within the mGIS platform.","href":"/api-reference/mgis-post-sat-rename-style-rename-an-existing-dataset-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/sat/rename/style POST mGIS SAT API renamedatasetPost stateful command"},{"id":"api:mgis-post-sat-savedataset-file-uploads-and-publishes-the-dataset-on-mgis-engine","kind":"API","title":"Uploads and publishes the dataset on mGIS engine","description":"Accepts a dataset in formats like JSON, GeoJSON, CSV, XLSX, KML, ZIP, XLT, TIF, along with additional parameters, to generate/publish it on the mGIS engine. This enables further utilization for manipulation, analysis, and visualization within the mGIS platform.","href":"/api-reference/mgis-post-sat-savedataset-file-uploads-and-publishes-the-dataset-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/sat/saveDataset/file POST mGIS SAT API PublishingFilePost stateful command"},{"id":"api:mgis-post-sat-savedataset-object-transfers-and-deploys-the-dataset-onto-the-mgis-engine","kind":"API","title":"Transfers and deploys the dataset onto the mGIS engine.","description":"Accepts a dataset in geojson format along with specified parameters to generate/publish it on the mGIS engine, enabling further manipulation, analysis, and visualization within the mGIS platform.","href":"/api-reference/mgis-post-sat-savedataset-object-transfers-and-deploys-the-dataset-onto-the-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/sat/saveDataset/object POST mGIS SAT API PublishingObjectPost stateful command"},{"id":"api:mgis-post-sat-savedataset-subset-uploads-and-publishes-the-subset-of-datasets-on-mgis-engine","kind":"API","title":"Uploads and publishes the subset of datasets on mGIS engine","description":"Generates and deploys subsets of existing datasets, filtered by specific conditions (either attribute-based or spatial), for subsequent utilization in manipulation, analysis, and visualization within the mGIS platform.","href":"/api-reference/mgis-post-sat-savedataset-subset-uploads-and-publishes-the-subset-of-datasets-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/sat/saveDataset/subset POST mGIS SAT API PublishingSubsetPost stateful command"},{"id":"api:mgis-post-sat-updatefeature-modifies-one-or-more-features-with-the-provided-updated-values","kind":"API","title":"Modifies one or more features with the provided updated values.","description":"This operation involves making changes to individual or multiple features within a dataset by applying updated values. This process allows for the refinement or adjustment of specific attributes or characteristics associated with the geographic elements, ensuring that the dataset accurately reflects the most current information.","href":"/api-reference/mgis-post-sat-updatefeature-modifies-one-or-more-features-with-the-provided-updated-values","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/sat/updateFeature POST mGIS SAT API UpdateFeature stateful command"},{"id":"api:mgis-post-sat-updategeom-updates-the-geometry-of-the-feature-on-the-basis-of-the-dataset-name-and-any-one-of-the-filter-or-featureid-provided-by-the-user","kind":"API","title":"Updates the geometry of the feature on the basis of the dataset name and any one of the filter or featureId provided by the user.","description":"Updates the geometry of the feature on the basis of the dataset name and any one of the filter or featureId provided by the user.","href":"/api-reference/mgis-post-sat-updategeom-updates-the-geometry-of-the-feature-on-the-basis-of-the-dataset-name-and-any-one-of-the-filter-or-featureid-provided-by-the-user","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/sat/updateGeom POST mGIS SAT API updateGeom stateful command"},{"id":"api:mgis-post-sat-updatestructure-add-or-delete-column-in-a-given-dataset-on-mgis-engine","kind":"API","title":"Add or delete column in a given Dataset on mGIS engine","description":"Performs operation like add and delete for columns on the given dataset table.","href":"/api-reference/mgis-post-sat-updatestructure-add-or-delete-column-in-a-given-dataset-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/sat/updateStructure POST mGIS SAT API updateStructure stateful command"},{"id":"api:mgis-post-savedataset-file-uploads-and-publishes-the-dataset-on-mgis-engine","kind":"API","title":"Uploads and publishes the dataset on mGIS engine","description":"Takes input of the dataset in the following format => JSON | json | geojson | GEOJSON | csv | CSV | xlsx | xls | XLSX | XLS | kml | KML | zip | ZIP | xlt | XLT | xlsm | XLSM | xltx | XLTX | TIF | tif along with other parameters to create/publish dataset on mGIS engine, so that it can be used for manipulation/analysis/visualization on mGIS platform","href":"/api-reference/mgis-post-savedataset-file-uploads-and-publishes-the-dataset-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/saveDataset/file POST mGIS SAT API PublishingFilePost stateful command"},{"id":"api:mgis-post-savedataset-object-uploads-and-publishes-the-dataset-on-mgis-engine","kind":"API","title":"Uploads and publishes the dataset on mGIS engine","description":"Takes input of the dataset in the form of geojson and other parameters to create/publish dataset on mGIS engine, so that it can be used for manipulation/analysis/visualization on mGIS platform","href":"/api-reference/mgis-post-savedataset-object-uploads-and-publishes-the-dataset-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/saveDataset/object POST mGIS SAT API PublishingObjectPost stateful command"},{"id":"api:mgis-post-savedataset-subset-uploads-and-publishes-the-subset-of-datasets-on-mgis-engine","kind":"API","title":"Uploads and publishes the subset of datasets on mGIS engine","description":"Creates and publishes subset of the existing datasets based on certain conditions (attributes based / spatial) so that the resultant sub-dataset can be used for further manipulation/analysis/visualization on mGIS platform","href":"/api-reference/mgis-post-savedataset-subset-uploads-and-publishes-the-subset-of-datasets-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/saveDataset/subset POST mGIS SAT API PublishingSubsetPost stateful command"},{"id":"api:mgis-post-updatefeature-updates-a-single-or-multiple-features-with-the-updated-values-provided","kind":"API","title":"Updates a single or multiple features with the updated values provided.","description":"Updates the a feature or multiple features with the updated values provided.","href":"/api-reference/mgis-post-updatefeature-updates-a-single-or-multiple-features-with-the-updated-values-provided","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/updateFeature POST mGIS SAT API UpdateFeature stateful command"},{"id":"api:mgis-post-updategeom-updates-the-geometry-of-the-feature-on-the-basis-of-the-dataset-name-and-any-one-of-the-filter-or-featureid-provided-by-the-user","kind":"API","title":"Updates the geometry of the feature on the basis of the dataset name and any one of the filter or featureId provided by the user.","description":"Updates the geometry of the feature on the basis of the dataset name and any one of the filter or featureId provided by the user.","href":"/api-reference/mgis-post-updategeom-updates-the-geometry-of-the-feature-on-the-basis-of-the-dataset-name-and-any-one-of-the-filter-or-featureid-provided-by-the-user","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/updateGeom POST mGIS SAT API updateGeom stateful command"},{"id":"api:mgis-post-updatestructure-add-or-delete-column-in-a-given-dataset-on-mgis-engine","kind":"API","title":"Add or delete column in a given Dataset on mGIS engine","description":"Performs operation like add and delete for columns on the given dataset table.","href":"/api-reference/mgis-post-updatestructure-add-or-delete-column-in-a-given-dataset-on-mgis-engine","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/updateStructure POST mGIS SAT API updateStructure stateful command"},{"id":"api:mgis-post-ai-ml-imagesegmentation-returns-the-array-of-features-which-contains-objects-of-geometry-of-the-uploaded-image","kind":"API","title":"Returns the array of features which contains objects of geometry of the uploaded image.","description":"Fetches the featureList of the uploaded image on the basis of the geotag, featureNme, bounds provided by the user. File, geotag, featureNme are the mandatory parameters.","href":"/api-reference/mgis-post-ai-ml-imagesegmentation-returns-the-array-of-features-which-contains-objects-of-geometry-of-the-uploaded-image","eyebrow":"POST · mGIS Analytics · source-snapshot","keywords":"/ai_ml/imageSegmentation POST mGIS Satellite Image Segmentation API describeDatasetGet stateful command"},{"id":"api:skydnn-ai-get-models-returns-the-details-of-all-the-models","kind":"API","title":"Returns the details of all the models","description":"Image classification and segmentation APIs enable state-of-the-art Computer Vision AI inferences to detect and catgorise objects in the photographs and generate localisation as well as map view of geospatial objects useful for a wide range of geospatial analytics and applications. On a Mission to \"Make our world better through maps, location technologies & IoT\" , Mappls is continuously enabling real time hyper-local information access through its map & location services. Skydnn APIs are a part of Skydnn AI platform and the document describes API's usage and specifications for their integration into any solution. The document covers : List of APIs along with use cases Explanation of resources and query parameters Listing of response structure and data type","href":"/api-reference/skydnn-ai-get-models-returns-the-details-of-all-the-models","eyebrow":"GET · SkyDNN AI & Vision · current-source","keywords":"/models GET AI & Vision hybrid observe"},{"id":"api:skydnn-ai-get-models-api-model-key-returns-the-details-of-provided-model","kind":"API","title":"Returns the details of provided model","description":"Image classification and segmentation APIs enable state-of-the-art Computer Vision AI inferences to detect and catgorise objects in the photographs and generate localisation as well as map view of geospatial objects useful for a wide range of geospatial analytics and applications. On a Mission to \"Make our world better through maps, location technologies & IoT\" , Mappls is continuously enabling real time hyper-local information access through its map & location services. Skydnn APIs are a part of Skydnn AI platform and the document describes API's usage and specifications for their integration into any solution. The document covers : List of APIs along with use cases Explanation of resources and query parameters Listing of response structure and data type","href":"/api-reference/skydnn-ai-get-models-api-model-key-returns-the-details-of-provided-model","eyebrow":"GET · SkyDNN AI & Vision · current-source","keywords":"/models/{api_model_key} GET AI & Vision hybrid observe"},{"id":"api:skydnn-ai-post-predict-returns-the-prediction-as-response-in-form-of-json","kind":"API","title":"Returns the prediction as response in form of JSON","description":"Image classification and segmentation APIs enable state-of-the-art Computer Vision AI inferences to detect and catgorise objects in the photographs and generate localisation as well as map view of geospatial objects useful for a wide range of geospatial analytics and applications. On a Mission to \"Make our world better through maps, location technologies & IoT\" , Mappls is continuously enabling real time hyper-local information access through its map & location services. Skydnn APIs are a part of Skydnn AI platform and the document describes API's usage and specifications for their integration into any solution. The document covers : List of APIs along with use cases Explanation of resources and query parameters Listing of response structure and data type","href":"/api-reference/skydnn-ai-post-predict-returns-the-prediction-as-response-in-form-of-json","eyebrow":"POST · SkyDNN AI & Vision · current-source","keywords":"/predict POST AI & Vision hybrid command"},{"id":"api:skydnn-ai-get-server-whoami-returns-the-current-models-in-port","kind":"API","title":"Returns the current models in port","description":"Image classification and segmentation APIs enable state-of-the-art Computer Vision AI inferences to detect and catgorise objects in the photographs and generate localisation as well as map view of geospatial objects useful for a wide range of geospatial analytics and applications. On a Mission to \"Make our world better through maps, location technologies & IoT\" , Mappls is continuously enabling real time hyper-local information access through its map & location services. Skydnn APIs are a part of Skydnn AI platform and the document describes API's usage and specifications for their integration into any solution. The document covers : List of APIs along with use cases Explanation of resources and query parameters Listing of response structure and data type","href":"/api-reference/skydnn-ai-get-server-whoami-returns-the-current-models-in-port","eyebrow":"GET · SkyDNN AI & Vision · current-source","keywords":"/server/whoami GET AI & Vision hybrid observe"},{"id":"api:workmate-get-clients-to-get-all-your-client-details","kind":"API","title":"To get all your client details","description":"Get all your client details that comes under your organization. Using this API you will be able to identify the client's unique id, name, address,lat, long, and the contact person details. Also, you can get client's department details belong to the client.","href":"/api-reference/workmate-get-clients-to-get-all-your-client-details","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/clients GET Workmate Client Management getClient stateful observe"},{"id":"api:workmate-post-clients-to-create-new-client","kind":"API","title":"To create new client","description":"Create Client API allows you to add a new client to your organization. Using this API, You can create a new client with a name, address, lat,long, contact details, Department along with their contact details.","href":"/api-reference/workmate-post-clients-to-create-new-client","eyebrow":"POST · Workmate Workforce · legacy-source","keywords":"/clients POST Workmate Client Management createClient stateful command"},{"id":"api:workmate-get-configurations-categories-to-get-the-list-of-client-category-in-an-account","kind":"API","title":"To get the list of client category in an account","description":"It gives all the client categories in an particular account. Category id can be used to create a client.","href":"/api-reference/workmate-get-configurations-categories-to-get-the-list-of-client-category-in-an-account","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/configurations/categories GET Workmate Company Configurations getclientCategories stateful observe"},{"id":"api:workmate-get-configurations-forms-to-get-the-form-s-id-and-their-details-from-your-account","kind":"API","title":"To get the form's Id and their details from your account.","description":"It gives all the forms which are created under your account. using this API you can get the unique Ids of different form and it can be used in custom form data API.","href":"/api-reference/workmate-get-configurations-forms-to-get-the-form-s-id-and-their-details-from-your-account","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/configurations/forms GET Workmate Company Configurations getForms stateful observe"},{"id":"api:workmate-get-reports-attendances-get-users-attendance-details-with-travelled-distance","kind":"API","title":"Get users attendance details with travelled distance.","description":"These APIs follow OAuth2 based security. To know more about how to create your authorization tokens, please use our authorization token URL. More details available here. The API leverages OAuth 2.0 based security. Hence, the developer would need to send a request for an access token using their clientid and clientsecret to the OAuth API. Once validated from the OAuth API, the accesstoken and the tokentype need to be sent as Authorization header with the value: \"{tokentype} {accesstoken}”. Authorization : tokentype accesstoken.","href":"/api-reference/workmate-get-reports-attendances-get-users-attendance-details-with-travelled-distance","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/reports/attendances GET Workmate Reports gattendanceetAttendanceData stateful observe"},{"id":"api:workmate-get-reports-forms-formid-to-get-form-based-check-in-out-details","kind":"API","title":"To get form based check in/out details","description":"Get the complete detail about the check in/check-out activity against the particular form. Get the form Id from the custom form API.","href":"/api-reference/workmate-get-reports-forms-formid-to-get-form-based-check-in-out-details","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/reports/forms/{formId} GET Workmate Reports getCustomFormsData stateful observe"},{"id":"api:workmate-get-reports-movements-userid-get-users-movement-details","kind":"API","title":"Get users movement details","description":"Get individual users location data which includes address, time, speed, phones's battery level.","href":"/api-reference/workmate-get-reports-movements-userid-get-users-movement-details","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/reports/movements/{userId} GET Workmate Reports getMovementData stateful observe"},{"id":"api:workmate-get-tasklists-to-get-the-task-list-details","kind":"API","title":"To get the task list details.","description":"These APIs follow OAuth2 based security. To know more about how to create your authorization tokens, please use our authorization token URL. More details available here. The API leverages OAuth 2.0 based security. Hence, the developer would need to send a request for an access token using their clientid and clientsecret to the OAuth API. Once validated from the OAuth API, the accesstoken and the tokentype need to be sent as Authorization header with the value: \"{tokentype} {accesstoken}”. Authorization : tokentype accesstoken.","href":"/api-reference/workmate-get-tasklists-to-get-the-task-list-details","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/taskLists GET Workmate Task Management getTaskList stateful observe"},{"id":"api:workmate-get-tasks-to-get-the-list-of-tasks-and-their-details","kind":"API","title":"To get the list of tasks and their details","description":"These APIs follow OAuth2 based security. To know more about how to create your authorization tokens, please use our authorization token URL. More details available here. The API leverages OAuth 2.0 based security. Hence, the developer would need to send a request for an access token using their clientid and clientsecret to the OAuth API. Once validated from the OAuth API, the accesstoken and the tokentype need to be sent as Authorization header with the value: \"{tokentype} {accesstoken}”. Authorization : tokentype accesstoken.","href":"/api-reference/workmate-get-tasks-to-get-the-list-of-tasks-and-their-details","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/tasks GET Workmate Task Management getTask stateful observe"},{"id":"api:workmate-post-tasks-to-create-new-task","kind":"API","title":"To create new Task","description":"Create Task API allows you to assign a new Task to your users. Using this API, You can Assign a new task with a task summary, description, assigned to user, task owner, the priority of the task, task location","href":"/api-reference/workmate-post-tasks-to-create-new-task","eyebrow":"POST · Workmate Workforce · legacy-source","keywords":"/tasks POST Workmate Task Management createTask stateful command"},{"id":"api:workmate-get-tasks-taskid-to-get-the-task-details-for-the-given-task-id","kind":"API","title":"To get the task details for the given task id.","description":"These APIs follow OAuth2 based security. To know more about how to create your authorization tokens, please use our authorization token URL. More details available here. The API leverages OAuth 2.0 based security. Hence, the developer would need to send a request for an access token using their clientid and clientsecret to the OAuth API. Once validated from the OAuth API, the accesstoken and the tokentype need to be sent as Authorization header with the value: \"{tokentype} {accesstoken}”. Authorization : tokentype accesstoken.","href":"/api-reference/workmate-get-tasks-taskid-to-get-the-task-details-for-the-given-task-id","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/tasks/{taskId} GET Workmate Task Management getTaskbyId stateful observe"},{"id":"api:workmate-put-tasks-taskid-to-update-the-task-description-status","kind":"API","title":"To update the task description & status.","description":"These APIs follow OAuth2 based security. To know more about how to create your authorization tokens, please use our authorization token URL. More details available here. The API leverages OAuth 2.0 based security. Hence, the developer would need to send a request for an access token using their clientid and clientsecret to the OAuth API. Once validated from the OAuth API, the accesstoken and the tokentype need to be sent as Authorization header with the value: \"{tokentype} {accesstoken}”. Authorization : tokentype accesstoken.","href":"/api-reference/workmate-put-tasks-taskid-to-update-the-task-description-status","eyebrow":"PUT · Workmate Workforce · legacy-source","keywords":"/tasks/{taskId} PUT Workmate Task Management updateTask stateful transition"},{"id":"api:workmate-get-users-to-get-all-the-user-details-which-belongs-to-your-organization","kind":"API","title":"To get all the user details which belongs to your organization.","description":"Gives all the users details of your organization. Using this API, you will be able to identify the workmate user id, workplace location, employee Id and other important details related to a user profile. You can only get the list of users who belongs to your organization.","href":"/api-reference/workmate-get-users-to-get-all-the-user-details-which-belongs-to-your-organization","eyebrow":"GET · Workmate Workforce · legacy-source","keywords":"/users GET Workmate User Details getUsers stateful observe"},{"id":"api-generation:intouch-get-alarm-10c842d182","kind":"API generation","title":"GET /alarm generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-get-alarm-10c842d182","eyebrow":"GET · InTouch Telematics · 0 review signals","keywords":"/alarm InTouch stateful v1-0-0 1.0.0 This API will get all the alarm configurations for a user. v2-0-0 2.0.0 This API will get all the alarm configurations for a user."},{"id":"api-generation:intouch-post-alarm-8579e8cb93","kind":"API generation","title":"POST /alarm generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-post-alarm-8579e8cb93","eyebrow":"POST · InTouch Telematics · 0 review signals","keywords":"/alarm InTouch stateful v1-0-0 1.0.0 This API will create an alarm. v2-0-0 2.0.0 This API will create an alarm."},{"id":"api-generation:intouch-delete-alarm-id-ca6df54f47","kind":"API generation","title":"DELETE /alarm/{id} generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-delete-alarm-id-ca6df54f47","eyebrow":"DELETE · InTouch Telematics · 0 review signals","keywords":"/alarm/{id} InTouch stateful v1-0-0 1.0.0 Deletes An Alarm Config v2-0-0 2.0.0 Deletes An Alarm Config"},{"id":"api-generation:intouch-post-alarm-id-352bd7eab8","kind":"API generation","title":"POST /alarm/{id} generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-post-alarm-id-352bd7eab8","eyebrow":"POST · InTouch Telematics · 0 review signals","keywords":"/alarm/{id} InTouch stateful v1-0-0 1.0.0 Updates An Alarm Config v2-0-0 2.0.0 Updates An Alarm Config"},{"id":"api-generation:intouch-get-alarm-alarmlog-0de27f90fb","kind":"API generation","title":"GET /alarm/alarmLog/ generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-get-alarm-alarmlog-0de27f90fb","eyebrow":"GET · InTouch Telematics · 0 review signals","keywords":"/alarm/alarmLog/ InTouch stateful v1-0-0 1.0.0 Gets The List Of Alarm Config(s) v2-0-0 2.0.0 Gets The List Of Alarm Config(s)"},{"id":"api-generation:intouch-get-geofence-0428994c0e","kind":"API generation","title":"GET /geofence/ generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-get-geofence-0428994c0e","eyebrow":"GET · InTouch Telematics · 0 review signals","keywords":"/geofence/ InTouch stateful v1-0-0 1.0.0 Gets All The Configured Geofence(s) v2-0-0 2.0.0 Gets All The Configured Geofence(s)"},{"id":"api-generation:intouch-post-geofence-9930a2a5a4","kind":"API generation","title":"POST /geofence/ generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-post-geofence-9930a2a5a4","eyebrow":"POST · InTouch Telematics · 0 review signals","keywords":"/geofence/ InTouch stateful v1-0-0 1.0.0 Create A New Geofence v2-0-0 2.0.0 Create A New Geofence"},{"id":"api-generation:intouch-delete-geofence-id-acd58f4735","kind":"API generation","title":"DELETE /geofence/{id} generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-delete-geofence-id-acd58f4735","eyebrow":"DELETE · InTouch Telematics · 0 review signals","keywords":"/geofence/{id} InTouch stateful v1-0-0 1.0.0 Delete A Geofence. v2-0-0 2.0.0 Delete A Geofence."},{"id":"api-generation:intouch-get-geofence-id-9d8bafa2d5","kind":"API generation","title":"GET /geofence/{id} generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-get-geofence-id-9d8bafa2d5","eyebrow":"GET · InTouch Telematics · 0 review signals","keywords":"/geofence/{id} InTouch stateful v1-0-0 1.0.0 Get A Single Or Multiple Geofence(s). v2-0-0 2.0.0 Get A Single Or Multiple Geofence(s)."},{"id":"api-generation:intouch-post-geofence-id-83a7719be5","kind":"API generation","title":"POST /geofence/{id} generation comparison","description":"Compare v1-0-0 and v2-0-0 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/intouch-post-geofence-id-83a7719be5","eyebrow":"POST · InTouch Telematics · 0 review signals","keywords":"/geofence/{id} InTouch stateful v1-0-0 1.0.0 Update A Geofence. v2-0-0 2.0.0 Update A Geofence."},{"id":"api-generation:mgis-get-describedataset-855417da71","kind":"API generation","title":"GET /describeDataset generation comparison","description":"Compare v1 and v2 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/mgis-get-describedataset-855417da71","eyebrow":"GET · mGIS Analytics · 3 review signals","keywords":"/describeDataset mGIS stateful v1 V1.0.0 fetches the attribute names. v2 V2.0.0 fetches the attribute names. Response status no longer declared: 404 Response status no longer declared: 422 Declared server URL changed"},{"id":"api-generation:mgis-get-getgeometrytype-97af5b353e","kind":"API generation","title":"GET /getGeometryType generation comparison","description":"Compare v1 and v2 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/mgis-get-getgeometrytype-97af5b353e","eyebrow":"GET · mGIS Analytics · 2 review signals","keywords":"/getGeometryType mGIS stateful v1 V1.0.0 Fetches Geometry type of datasetNme v2 V2.0.0 Fetches Geometry type of datasetNme Response status no longer declared: 422 Declared server URL changed"},{"id":"api-generation:mgis-get-getlayerslist-7a2d5959c7","kind":"API generation","title":"GET /getLayersList generation comparison","description":"Compare v1 and v2 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/mgis-get-getlayerslist-7a2d5959c7","eyebrow":"GET · mGIS Analytics · 1 review signals","keywords":"/getLayersList mGIS stateful v1 V1.0.0 Fetches the names of all the datasets available in the user's workspace on the geoserver. v2 V1.0.0 Fetches the names of all the datasets available in the user's workspace on the geoserver. Declared server URL changed"},{"id":"api-generation:mgis-get-getlegendsimg-eed36ebbd0","kind":"API generation","title":"GET /getLegendsImg generation comparison","description":"Compare v1 and v2 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/mgis-get-getlegendsimg-eed36ebbd0","eyebrow":"GET · mGIS Analytics · 1 review signals","keywords":"/getLegendsImg mGIS stateful v1 V1.0.0 Fetches the image of legends for the given dataset. v2 V1.0.0 Fetches the image of legends for the given dataset. Declared server URL changed"},{"id":"api-generation:mgis-get-map-getfeatureinfo-6dd132c52b","kind":"API generation","title":"GET /map/getFeatureInfo generation comparison","description":"Compare v1 and v2 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/mgis-get-map-getfeatureinfo-6dd132c52b","eyebrow":"GET · mGIS Analytics · 0 review signals","keywords":"/map/getFeatureInfo mGIS stateful v1 V2.0.0 Fetches the feature information. v2 V2.0.0 Fetches the feature information."},{"id":"api-generation:mgis-get-map-getlayerjoin-9a1aac1c53","kind":"API generation","title":"GET /map/getLayerJoin generation comparison","description":"Compare v1 and v2 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/mgis-get-map-getlayerjoin-9a1aac1c53","eyebrow":"GET · mGIS Analytics · 0 review signals","keywords":"/map/getLayerJoin mGIS stateful v1 V2.0.0 Fetches the maptiles of the dataset name of a bounding box for Spatial Join between 2 datasets as well as between one dataset and userDefined geometry. v2 V2.0.0 Fetches the maptiles of the dataset name of a bounding box for Spatial Join between 2 datasets as well as between one dataset and userDefined geometry."},{"id":"api-generation:mgis-get-map-getmap-ee5f026cd2","kind":"API generation","title":"GET /map/getMap generation comparison","description":"Compare v1 and v2 exact source declarations, compatibility signals, and migration checks.","href":"/api-generations/mgis-get-map-getmap-ee5f026cd2","eyebrow":"GET · mGIS Analytics · 0 review signals","keywords":"/map/getMap mGIS stateful v1 V2.0.0 Fetches the maptiles of the dataset name of a bounding box. v2 V2.0.0 Fetches the maptiles of the dataset name of a bounding box."},{"id":"sdk-guide:github","kind":"SDK & guide","title":"Mappls API Organization Guide","description":"is a ✨special ✨ repository that you can use to add README.md to your public organization profile, visible to anyone.","href":"/reference/github","eyebrow":"Guide · current","keywords":".github maps Unspecified"},{"id":"sdk-guide:flutter-mapmyindia-gl","kind":"SDK & guide","title":"Flutter MapmyIndia GL","description":"A Mappls sdk for maps, search places, routes navigation, tracking telematics, widgets deep links, offline automotive, capture feedback across Flutter.","href":"/sdks/flutter-mapmyindia-gl","eyebrow":"SDK · deprecated","keywords":"flutter-mapmyindia-gl maps search-places routes-navigation tracking-telematics widgets-deep-links offline-automotive capture-feedback Flutter Dart oauth2 api-key"},{"id":"sdk-guide:mapmyindia-angular-sample-websdk-rest","kind":"SDK & guide","title":"Angular Sample for MapmyIndia Interactive Maps JS SDK & MapmyIndia RESTful APIs for Web","description":"Angular Sample for MapmyIndia Interactive Maps JS SDK & MapmyIndia RESTful APIs for Web","href":"/reference/mapmyindia-angular-sample-websdk-rest","eyebrow":"Sample · sample","keywords":"mapmyindia-angular-sample-webSDK-REST maps search-places identity-platform Web REST JSON JavaScript HTML CSS oauth2 api-key"},{"id":"sdk-guide:mapmyindia-api-addendums","kind":"SDK & guide","title":"Transaction Definitions","description":"This repository has the useful addendum like updated transaction definitions, category codes for Nearby Places Search, Branding Guidelines and other useful info for using MapmyIndia SDKs & APIs","href":"/reference/mapmyindia-api-addendums","eyebrow":"Guide · legacy","keywords":"mapmyindia-api-addendums maps search-places routes-navigation gis-analytics capture-feedback Unspecified"},{"id":"sdk-guide:mapmyindia-geoanalytics-api-web","kind":"SDK & guide","title":"MapmyIndia Geo-Analytics APIs !","description":"MapmyIndia GeoAnalytics APIs - MapmyIndia’s Data served through convenient and easy to use web APIs","href":"/reference/mapmyindia-geoanalytics-api-web","eyebrow":"REST API · legacy","keywords":"mapmyindia-geoanalytics-api-web maps gis-analytics Web api-key"},{"id":"sdk-guide:mapmyindia-interactive-map-js-api","kind":"SDK & guide","title":"MapmyIndia Interactive Map JS API !","description":"Integrate Map APIs to visualize maps, accurate directions, geo-coding and traffic flow","href":"/sdks/mapmyindia-interactive-map-js-api","eyebrow":"SDK · legacy","keywords":"mapmyindia-interactive-map-js-api maps search-places routes-navigation gis-analytics widgets-deep-links Web REST api-key"},{"id":"sdk-guide:mapmyindia-intouch-android-sdk","kind":"SDK & guide","title":"Mapmyindia Intouch Android SDK","description":"A Mappls sdk for tracking telematics, workforce, gis analytics, widgets deep links, identity platform across Android.","href":"/sdks/mapmyindia-intouch-android-sdk","eyebrow":"SDK · deprecated","keywords":"mapmyindia-intouch-android-sdk tracking-telematics workforce gis-analytics widgets-deep-links identity-platform Android Java Text Kotlin oauth2"},{"id":"sdk-guide:mapmyindia-intouch-ios-sdk","kind":"SDK & guide","title":"MapmyIndia Intouch iOS SDK","description":"A Mappls sdk for maps, tracking telematics, workforce, gis analytics, identity platform across iOS.","href":"/sdks/mapmyindia-intouch-ios-sdk","eyebrow":"SDK · deprecated","keywords":"mapmyindia-intouch-ios-sdk maps tracking-telematics workforce gis-analytics identity-platform iOS Text oauth2"},{"id":"sdk-guide:mapmyindia-intouch-react-native-sdk","kind":"SDK & guide","title":"Mapmyindia Intouch React Native SDK","description":"A Mappls sdk for tracking telematics, workforce, gis analytics, identity platform across React Native.","href":"/sdks/mapmyindia-intouch-react-native-sdk","eyebrow":"SDK · deprecated","keywords":"mapmyindia-intouch-react-native-sdk tracking-telematics workforce gis-analytics identity-platform React Native Groovy Text JavaScript oauth2"},{"id":"sdk-guide:mapmyindia-intouch-rest-apis","kind":"SDK & guide","title":"Mapmyindia Intouch REST Apis","description":"A Mappls rest api for tracking telematics across REST.","href":"/reference/mapmyindia-intouch-rest-apis","eyebrow":"REST API · deprecated","keywords":"mapmyindia-intouch-rest-apis tracking-telematics REST"},{"id":"sdk-guide:mapmyindia-intouch-web-plugins","kind":"SDK & guide","title":"Mapmyindia Intouch Web Plugins","description":"A Mappls widget for tracking telematics, widgets deep links, capture feedback across Web, Widgets/Deep links.","href":"/reference/mapmyindia-intouch-web-plugins","eyebrow":"Widget · legacy","keywords":"mapmyindia-intouch-web-plugins tracking-telematics widgets-deep-links capture-feedback Web Widgets/Deep links"},{"id":"sdk-guide:mapmyindia-map-cordova-ionic-beta","kind":"SDK & guide","title":"MapmyIndia Map SDK for Cordova/Ionic - Beta 1","description":"MapmyIndia Map library for Cordova/Ionic - Beta 1 Hybrid SDK","href":"/reference/mapmyindia-map-cordova-ionic-beta","eyebrow":"Guide · deprecated","keywords":"mapmyindia-map-cordova-ionic-beta maps search-places gis-analytics widgets-deep-links Cordova/Ionic JavaScript Text api-key"},{"id":"sdk-guide:mapmyindia-map-react-native-beta","kind":"SDK & guide","title":"Mapmyindia Maps SDK for React Native beta","description":"MapmyIndia Map library for React Native - Beta release Hybrid SDK","href":"/reference/mapmyindia-map-react-native-beta","eyebrow":"Guide · deprecated","keywords":"mapmyindia-map-react-native-beta maps search-places routes-navigation gis-analytics capture-feedback identity-platform React Native oauth2 api-key licensed-entitlement"},{"id":"sdk-guide:mapmyindia-maps-vectorsdk-android","kind":"SDK & guide","title":"MapmyIndia Vector Map Android SDK","description":"MapmyIndia Vector Maps SDK for Native Android Development with REST API Kit","href":"/sdks/mapmyindia-maps-vectorsdk-android","eyebrow":"SDK · deprecated","keywords":"mapmyindia-maps-vectorSDK-android maps search-places routes-navigation tracking-telematics gis-analytics widgets-deep-links capture-feedback Android api-key"},{"id":"sdk-guide:mapmyindia-maps-vectorsdk-ios","kind":"SDK & guide","title":"Mapmyindia Maps VectorSDK IOS","description":"MapmyIndia Vector Maps SDK for Native iOS Development with REST API Kit","href":"/sdks/mapmyindia-maps-vectorsdk-ios","eyebrow":"SDK · deprecated","keywords":"mapmyindia-maps-vectorSDK-iOS maps search-places routes-navigation widgets-deep-links capture-feedback identity-platform iOS api-key"},{"id":"sdk-guide:mapmyindia-mgis-apis","kind":"SDK & guide","title":"Mappls mGIS APIs","description":"Using these APIs developers can fully leverage and embed the power of GeoSpatial Analytics, GIS and location intelligence and AI. These APIs allow a developer to integrate into their own application the power and full set of functionalities of the mGIS product and platform.","href":"/reference/mapmyindia-mgis-apis","eyebrow":"REST API · legacy","keywords":"mapmyindia-mgis-apis maps search-places routes-navigation gis-analytics ai-vision capture-feedback REST Text"},{"id":"sdk-guide:mapmyindia-mgis-libraries","kind":"SDK & guide","title":"Mapmyindia MGIS Libraries","description":"A Mappls guide for maps, gis analytics, widgets deep links, capture feedback.","href":"/reference/mapmyindia-mgis-libraries","eyebrow":"Guide · legacy","keywords":"mapmyindia-mgis-libraries maps gis-analytics widgets-deep-links capture-feedback Unspecified HTML Text JavaScript"},{"id":"sdk-guide:mapmyindia-nearby-covid-places","kind":"SDK & guide","title":"Mapmyindia Nearby Covid Places","description":"MapmyIndia's easy to integrate Nearby COVID Places Search Widget for Apps. Easily integrate the simple JS widget into your codebase and help your users discover Nearby COVID Vaccination Centres. Help your users discover government approved Vaccination Centres across India during this pandemic.","href":"/reference/mapmyindia-nearby-covid-places","eyebrow":"Widget · deprecated","keywords":"mapmyindia-nearby-covid-places maps search-places widgets-deep-links capture-feedback Web HTML JavaScript CSS Text"},{"id":"sdk-guide:mapmyindia-places-n-directions-web-sdk","kind":"SDK & guide","title":"Mapmyindia Places N Directions Web SDK","description":"MapmyIndia Places and Directions Library for Web SDKs provided by MapmyIndia. This library is compatible with both our Web SDKs - Vector Maps & our legacy Raster Maps.","href":"/sdks/mapmyindia-places-n-directions-web-sdk","eyebrow":"SDK · deprecated","keywords":"mapmyindia-places-n-directions-web-sdk other Web"},{"id":"sdk-guide:mapmyindia-purejs-sample-websdk-rest","kind":"SDK & guide","title":"MapmyIndia Interactive Maps JS SDK & MapmyIndia RESTful APIs for Web in Pure JS","description":"PureJS Sample for MapmyIndia Interactive Maps JS SDK & MapmyIndia RESTful APIs for Web","href":"/reference/mapmyindia-purejs-sample-websdk-rest","eyebrow":"Sample · sample","keywords":"mapmyindia-pureJS-sample-webSDK-REST maps search-places routes-navigation tracking-telematics identity-platform Web REST HTML JavaScript Text oauth2 api-key"},{"id":"sdk-guide:mapmyindia-rest-api","kind":"SDK & guide","title":"Mapmyindia REST API","description":"Building Blocks to Add Powerful Location Intelligence & Mapping Functionality to your Apps","href":"/reference/mapmyindia-rest-api","eyebrow":"REST API · deprecated","keywords":"mapmyindia-rest-api maps search-places routes-navigation gis-analytics capture-feedback REST api-key"},{"id":"sdk-guide:mapmyindia-restapi-cordova-ionic-beta","kind":"SDK & guide","title":"MapmyIndia REST APIs for Cordova/Ionic - Beta 1","description":"MapmyIndia REST APIs for Cordova/Ionic - Beta 1 Hybrid SDK","href":"/sdks/mapmyindia-restapi-cordova-ionic-beta","eyebrow":"SDK · deprecated","keywords":"mapmyindia-restapi-cordova-ionic-beta search-places routes-navigation widgets-deep-links Cordova/Ionic JavaScript Text JSX oauth2 api-key"},{"id":"sdk-guide:mapmyindia-restapi-react-native-beta","kind":"SDK & guide","title":"Mapmyindia REST API SDK for React Native - beta","description":"A Mappls sdk for maps, search places, routes navigation, gis analytics, identity platform across React Native.","href":"/sdks/mapmyindia-restapi-react-native-beta","eyebrow":"SDK · deprecated","keywords":"mapmyindia-restapi-react-native-beta maps search-places routes-navigation gis-analytics identity-platform React Native JavaScript Text oauth2 api-key licensed-entitlement"},{"id":"sdk-guide:mapmyindia-vector-maps-js-web-sdk","kind":"SDK & guide","title":"Mapmyindia Vector Maps JS Web SDK","description":"MapmyIndia's Latest Vector Maps Web SDK for rendering beautifully interactive, fluid maps that are powered by browser based WebGL.","href":"/sdks/mapmyindia-vector-maps-js-web-sdk","eyebrow":"SDK · deprecated","keywords":"mapmyindia-vector-maps-js-web-SDK maps search-places routes-navigation gis-analytics widgets-deep-links Web HTML Text JavaScript api-key"},{"id":"sdk-guide:mapmyindia-workmate-apis","kind":"SDK & guide","title":"Mappls by MapmyIndia-Workmate-Apis","description":"Powerful work force management APIs helping users get all the pertinent data related to their org such as live location of employees, client details and task details etc. Mappls Workmate easily integrates with existing cloud services via our APIs. These APIs help to make the ops efficient by providing location intellegence to your solutions.","href":"/reference/mapmyindia-workmate-apis","eyebrow":"REST API · legacy","keywords":"mapmyindia-workmate-apis maps workforce identity-platform REST oauth2"},{"id":"sdk-guide:mappls-ai-apis","kind":"SDK & guide","title":"MAPPLS AI / ML APIs","description":"Revolutionize spatial analysis with our AI-ML API's, delivering unparalleled insights and predictive capabilities for optimized decision-making.","href":"/reference/mappls-ai-apis","eyebrow":"REST API · current","keywords":"mappls-ai-apis maps search-places workforce gis-analytics ai-vision capture-feedback identity-platform REST AI/MCP licensed-entitlement"},{"id":"sdk-guide:mappls-android-compose-demo","kind":"SDK & guide","title":"Mappls Vector Map Android SDK JetPack Compose","description":"A Mappls sample for maps, search places, routes navigation, gis analytics, widgets deep links, capture feedback across Android.","href":"/reference/mappls-android-compose-demo","eyebrow":"Sample · sample","keywords":"mappls-android-compose-demo maps search-places routes-navigation gis-analytics widgets-deep-links capture-feedback Android Groovy Text XML Kotlin oauth2 api-key"},{"id":"sdk-guide:mappls-android-sdk","kind":"SDK & guide","title":"Mappls Android SDK","description":"A collection of Mappls's Map and others SDKs for Native android Development.","href":"/sdks/mappls-android-sdk","eyebrow":"SDK · current","keywords":"mappls-android-sdk maps search-places routes-navigation tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform Android static-key-2025 oauth2 api-key"},{"id":"sdk-guide:mappls-annotation-extension-ios-distribution","kind":"SDK & guide","title":"Mappls Annotation Extension for iOS","description":"Mappls Annotation Extension Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-annotation-extension-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-annotation-extension-ios-distribution maps search-places tracking-telematics capture-feedback identity-platform iOS Swift"},{"id":"sdk-guide:mappls-annotation-extension-ios-distribution-base","kind":"SDK & guide","title":"Mappls Annotation Extension for iOS","description":"A versioned iOS distribution package used to integrate maps, search places, tracking telematics, capture feedback, identity platform into an application.","href":"/sdks/mappls-annotation-extension-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-annotation-extension-ios-distribution-base maps search-places tracking-telematics capture-feedback identity-platform iOS Swift"},{"id":"sdk-guide:mappls-api-core-ios-distribution","kind":"SDK & guide","title":"[MapplsAPICore]()","description":"Mappls API Core Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-api-core-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-api-core-ios-distribution routes-navigation tracking-telematics capture-feedback identity-platform iOS"},{"id":"sdk-guide:mappls-api-kit-ios-distribution","kind":"SDK & guide","title":"[MapplsAPIKit (REST API Kit for iOS)]()","description":"Mappls API Kit Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-api-kit-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-api-kit-ios-distribution maps search-places routes-navigation tracking-telematics workforce gis-analytics capture-feedback identity-platform iOS Objective-C Swift Text oauth2 api-key"},{"id":"sdk-guide:mappls-api-kit-ios-distribution-base","kind":"SDK & guide","title":"[MapplsAPIKit (REST API Kit for iOS)]()","description":"Mappls API Kit Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-api-kit-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-api-kit-ios-distribution-base maps search-places routes-navigation tracking-telematics workforce capture-feedback identity-platform iOS Objective-C Swift Text oauth2 api-key"},{"id":"sdk-guide:mappls-app-widgets","kind":"SDK & guide","title":"Mappls App Widgets","description":"Using Mappls App Widgets, you can embed latest features of Mappls app in a universal, cross-platform mechanism and perform visualization of a place, get immersive 3D metaverse visuals, and display Realviews - panoramic images. You don't need a Mappls API credential to use most of these Mappls App widgets.","href":"/reference/mappls-app-widgets","eyebrow":"Deep link · current","keywords":"mappls-app-widgets search-places widgets-deep-links Widgets/Deep links"},{"id":"sdk-guide:mappls-camera-ios-distribution","kind":"SDK & guide","title":"MapplsCamera SDK for iOS","description":"A versioned iOS distribution package used to integrate maps, search places, tracking telematics, offline automotive, capture feedback, identity platform into an application.","href":"/sdks/mappls-camera-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-camera-ios-distribution maps search-places tracking-telematics offline-automotive capture-feedback identity-platform iOS Swift api-key signed-request"},{"id":"sdk-guide:mappls-camera-sdk-android","kind":"SDK & guide","title":"Mappls Camera SDK","description":"A Mappls sdk for maps, search places, tracking telematics, workforce, widgets deep links, offline automotive, capture feedback across Android.","href":"/sdks/mappls-camera-sdk-android","eyebrow":"SDK · current","keywords":"mappls-camera-sdk-android maps search-places tracking-telematics workforce widgets-deep-links offline-automotive capture-feedback Android Kotlin Groovy api-key"},{"id":"sdk-guide:mappls-camera-sdk-ios","kind":"SDK & guide","title":"MapplsCamera SDK for iOS","description":"A Mappls sdk for maps, search places, tracking telematics, offline automotive, capture feedback, identity platform across iOS.","href":"/sdks/mappls-camera-sdk-ios","eyebrow":"SDK · current","keywords":"mappls-camera-sdk-ios maps search-places tracking-telematics offline-automotive capture-feedback identity-platform iOS Swift api-key signed-request"},{"id":"sdk-guide:mappls-direction-ui-ios-distribution","kind":"SDK & guide","title":"MapplsDirectionUI for iOS","description":"Mappls Direction UI Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-direction-ui-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-direction-ui-ios-distribution maps search-places routes-navigation tracking-telematics capture-feedback identity-platform iOS Swift Objective-C Text"},{"id":"sdk-guide:mappls-direction-ui-ios-distribution-base","kind":"SDK & guide","title":"MapplsDirectionUI for iOS","description":"A versioned iOS distribution package used to integrate maps, search places, routes navigation, tracking telematics, capture feedback, identity platform into an application.","href":"/sdks/mappls-direction-ui-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-direction-ui-ios-distribution-base maps search-places routes-navigation tracking-telematics capture-feedback identity-platform iOS Swift Objective-C Text"},{"id":"sdk-guide:mappls-drivingrange-plugin-ios-distribution","kind":"SDK & guide","title":"MapplsDrivingRangePlugin for iOS","description":"Mappls Driving Range Plugin Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-drivingrange-plugin-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-drivingrange-plugin-ios-distribution maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-drivingrange-plugin-ios-distribution-base","kind":"SDK & guide","title":"MapplsDrivingRangePlugin for iOS","description":"A versioned iOS distribution package used to integrate maps, routes navigation, tracking telematics, widgets deep links, capture feedback, identity platform into an application.","href":"/sdks/mappls-drivingrange-plugin-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-drivingrange-plugin-ios-distribution-base maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-feedback-kit-ios-distribution","kind":"SDK & guide","title":"MapplsFeedbackKit for iOS","description":"Mappls Feedback Kit Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-feedback-kit-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-feedback-kit-ios-distribution search-places tracking-telematics widgets-deep-links offline-automotive capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-feedback-kit-ios-distribution-base","kind":"SDK & guide","title":"MapplsFeedbackKit for iOS","description":"A versioned iOS distribution package used to integrate search places, tracking telematics, widgets deep links, offline automotive, capture feedback, identity platform into an application.","href":"/sdks/mappls-feedback-kit-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-feedback-kit-ios-distribution-base search-places tracking-telematics widgets-deep-links offline-automotive capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-feedback-uikit-ios-distribution","kind":"SDK & guide","title":"MapplsFeedbackUIKit for iOS","description":"Mappls Feedback UI Kit Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-feedback-uikit-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-feedback-uikit-ios-distribution maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-feedback-uikit-ios-distribution-base","kind":"SDK & guide","title":"MapplsFeedbackUIKit for iOS","description":"A versioned iOS distribution package used to integrate maps, routes navigation, tracking telematics, widgets deep links, capture feedback, identity platform into an application.","href":"/sdks/mappls-feedback-uikit-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-feedback-uikit-ios-distribution-base maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-flutter-sdk","kind":"SDK & guide","title":"Mappls Flutter SDK","description":"This SDK is wrapper for Flutter on Native Map SDK to support on Android and iOS.","href":"/sdks/mappls-flutter-sdk","eyebrow":"SDK · current","keywords":"mappls-flutter-sdk maps search-places routes-navigation tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform Flutter static-key-2025 oauth2 api-key"},{"id":"sdk-guide:mappls-geoanalytics-ios-distribution","kind":"SDK & guide","title":"MapplsGeoanalytics Plugin for iOS","description":"Mappls Geoanalytics Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-geoanalytics-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-geoanalytics-ios-distribution maps search-places tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-geoanalytics-ios-distribution-base","kind":"SDK & guide","title":"MapplsGeoanalytics Plugin for iOS","description":"Mappls Geoanalytics Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-geoanalytics-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-geoanalytics-ios-distribution-base maps search-places tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-geofence-ui-ios-distribution","kind":"SDK & guide","title":"MapplsGeofenceUI Plugin for iOS","description":"Mappls Geofence UI Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-geofence-ui-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-geofence-ui-ios-distribution maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-geofence-ui-ios-distribution-base","kind":"SDK & guide","title":"MapplsGeofenceUI Plugin for iOS","description":"A versioned iOS distribution package used to integrate maps, routes navigation, tracking telematics, widgets deep links, capture feedback, identity platform into an application.","href":"/sdks/mappls-geofence-ui-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-geofence-ui-ios-distribution-base maps routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-insight-sdk","kind":"SDK & guide","title":"Mappls Insight Embeddable Visualizations","description":"Mappls advanced analytics engine: Insight transforms raw data into impactful visualizations and interactive dashboards, easily shared and embedded.","href":"/sdks/mappls-insight-sdk","eyebrow":"SDK · current","keywords":"mappls-insight-sdk gis-analytics offline-automotive capture-feedback identity-platform Web HTML oauth2"},{"id":"sdk-guide:mappls-intouch-android-sdk","kind":"SDK & guide","title":"Mappls Intouch Android SDK","description":"A Mappls sdk for tracking telematics, workforce, gis analytics, widgets deep links, capture feedback across Android.","href":"/sdks/mappls-intouch-android-sdk","eyebrow":"SDK · current","keywords":"mappls-intouch-android-sdk tracking-telematics workforce gis-analytics widgets-deep-links capture-feedback Android oauth2 api-key"},{"id":"sdk-guide:mappls-intouch-ios-distribution","kind":"SDK & guide","title":"Mappls Intouch IOS Distribution","description":"Mappls Intouch iOS Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-intouch-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-intouch-ios-distribution tracking-telematics iOS"},{"id":"sdk-guide:mappls-intouch-ios-distribution-base","kind":"SDK & guide","title":"Mappls Intouch IOS Distribution Base","description":"A versioned iOS distribution package used to integrate tracking telematics into an application.","href":"/sdks/mappls-intouch-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-intouch-ios-distribution-base tracking-telematics iOS"},{"id":"sdk-guide:mappls-intouch-ios-sdk","kind":"SDK & guide","title":"[Mappls Intouch SDK]()","description":"A Mappls sdk for tracking telematics, workforce, gis analytics, capture feedback across iOS.","href":"/sdks/mappls-intouch-ios-sdk","eyebrow":"SDK · current","keywords":"mappls-intouch-ios-sdk tracking-telematics workforce gis-analytics capture-feedback iOS oauth2"},{"id":"sdk-guide:mappls-intouch-rest-apis","kind":"SDK & guide","title":"Mappls Intouch REST Apis","description":"A Mappls rest api for routes navigation, tracking telematics, capture feedback, identity platform across REST.","href":"/reference/mappls-intouch-rest-apis","eyebrow":"REST API · current","keywords":"mappls-intouch-rest-apis routes-navigation tracking-telematics capture-feedback identity-platform REST oauth2"},{"id":"sdk-guide:mappls-ios-sdk","kind":"SDK & guide","title":"Mappls iOS SDK","description":"A collection of Mappls's Map and others SDKs for Native iOS Development.","href":"/sdks/mappls-ios-sdk","eyebrow":"SDK · current","keywords":"mappls-ios-sdk maps search-places routes-navigation tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform iOS static-key-2025 oauth2"},{"id":"sdk-guide:mappls-lms-ios-distribution","kind":"SDK & guide","title":"Mappls LMS IOS Distribution","description":"A versioned iOS distribution package used to integrate Mappls capabilities into an application.","href":"/sdks/mappls-lms-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-lms-ios-distribution other iOS"},{"id":"sdk-guide:mappls-lms-ios-distribution-base","kind":"SDK & guide","title":"Mappls LMS IOS Distribution Base","description":"A versioned iOS distribution package used to integrate Mappls capabilities into an application.","href":"/sdks/mappls-lms-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-lms-ios-distribution-base other iOS"},{"id":"sdk-guide:mappls-location-capture-android-sdk","kind":"SDK & guide","title":"Mappls Location Capture SDK","description":"A lightweight, on-demand location capture SDK for Android that enables applications to fetch a user’s current location efficiently with accuracy limits, timeout control, and minimal battery usage. The SDK supports single-shot and subscribed location fetching without continuous tracking.","href":"/sdks/mappls-location-capture-android-sdk","eyebrow":"SDK · current","keywords":"mappls-location-capture-android-sdk search-places tracking-telematics workforce widgets-deep-links capture-feedback Android Kotlin Groovy Java"},{"id":"sdk-guide:mappls-location-capture-ios-sdk","kind":"SDK & guide","title":"Mappls Location Capture IOS SDK","description":"A Mappls sdk for capture feedback across iOS.","href":"/sdks/mappls-location-capture-ios-sdk","eyebrow":"SDK · current","keywords":"mappls-location-capture-ios-sdk capture-feedback iOS"},{"id":"sdk-guide:mappls-location-capture-sdk-ios-distribution","kind":"SDK & guide","title":"Mappls Location Capture SDK (iOS)","description":"A versioned iOS distribution package used to integrate tracking telematics, workforce, capture feedback into an application.","href":"/sdks/mappls-location-capture-sdk-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-location-capture-sdk-ios-distribution tracking-telematics workforce capture-feedback iOS XML Swift"},{"id":"sdk-guide:mappls-map-ios-distribution","kind":"SDK & guide","title":"[Mappls Map SDK]()","description":"Mappls Map Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-map-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-map-ios-distribution maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Text Swift Objective-C oauth2 api-key"},{"id":"sdk-guide:mappls-map-ios-distribution-base","kind":"SDK & guide","title":"[Mappls Map SDK]()","description":"Mappls Map Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-map-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-map-ios-distribution-base maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Text Swift Objective-C oauth2 api-key"},{"id":"sdk-guide:mappls-map-move-ios-distribution-base","kind":"SDK & guide","title":"[Mappls Map SDK]()","description":"mappls-map-move-ios-distribution-base","href":"/sdks/mappls-map-move-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-map-move-ios-distribution-base maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Text Swift Objective-C oauth2 api-key"},{"id":"sdk-guide:mappls-nearby-finder-ios-distribution","kind":"SDK & guide","title":"[Custom Search Nearby Records](Custom-Search-Nearby-Records)","description":"mappls-nearby-finder-ios-distribution","href":"/sdks/mappls-nearby-finder-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-nearby-finder-ios-distribution maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Ruby Swift api-key"},{"id":"sdk-guide:mappls-nearby-finder-ios-distribution-base","kind":"SDK & guide","title":"[Custom Search Nearby Records](Custom-Search-Nearby-Records)","description":"A versioned iOS distribution package used to integrate maps, search places, routes navigation, tracking telematics, widgets deep links, capture feedback, identity platform into an application.","href":"/sdks/mappls-nearby-finder-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-nearby-finder-ios-distribution-base maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Ruby Swift api-key"},{"id":"sdk-guide:mappls-nearby-ui-ios-distribution","kind":"SDK & guide","title":"Mappls Nearby Search Widget for iOS","description":"Mappls Nearby UI Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-nearby-ui-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-nearby-ui-ios-distribution maps search-places tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-nearby-ui-ios-distribution-base","kind":"SDK & guide","title":"Mappls Nearby Search Widget for iOS","description":"A versioned iOS distribution package used to integrate maps, search places, tracking telematics, widgets deep links, capture feedback, identity platform into an application.","href":"/sdks/mappls-nearby-ui-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-nearby-ui-ios-distribution-base maps search-places tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-raster-catalogue-ios-distribution","kind":"SDK & guide","title":"MapplsRasterCatalogue Plugin for iOS","description":"Mappls Raster Catalogue Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-raster-catalogue-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-raster-catalogue-ios-distribution maps tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-raster-catalogue-ios-distribution-base","kind":"SDK & guide","title":"MapplsRasterCatalogue Plugin for iOS","description":"A versioned iOS distribution package used to integrate maps, tracking telematics, gis analytics, widgets deep links, capture feedback, identity platform into an application.","href":"/sdks/mappls-raster-catalogue-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-raster-catalogue-ios-distribution-base maps tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-react-native-intouch-sdk","kind":"SDK & guide","title":"Mappls Intouch React Native SDK","description":"This SDK is wrapper for ReactNative on Native SDKs (IntouchCore, IntouchAPI) to support on Android and iOS.","href":"/sdks/mappls-react-native-intouch-sdk","eyebrow":"SDK · current","keywords":"mappls-react-native-intouch-sdk tracking-telematics workforce capture-feedback React Native"},{"id":"sdk-guide:mappls-react-native-sdk","kind":"SDK & guide","title":"Mappls React Native SDK","description":"A Mappls sdk for maps, search places, routes navigation, tracking telematics, gis analytics, widgets deep links, capture feedback, identity platform across React Native.","href":"/sdks/mappls-react-native-sdk","eyebrow":"SDK · current","keywords":"mappls-react-native-sdk maps search-places routes-navigation tracking-telematics gis-analytics widgets-deep-links capture-feedback identity-platform React Native static-key-2025 oauth2 api-key"},{"id":"sdk-guide:mappls-rest-apis","kind":"SDK & guide","title":"Mappls Map APIs (REST) !","description":"Building Blocks to Add Powerful Location Intelligence & Mapping Functionality to your Apps","href":"/reference/mappls-rest-apis","eyebrow":"REST API · current","keywords":"mappls-rest-apis maps search-places routes-navigation gis-analytics capture-feedback identity-platform REST static-key-2025 oauth2 api-key"},{"id":"sdk-guide:mappls-ui-widget-ios-distribution","kind":"SDK & guide","title":"MapplsUIWidgets - UI Components SDK for iOS","description":"Mappls UI Widget Native for iOS distributed via the SPM (Swift Package Manager).","href":"/sdks/mappls-ui-widget-ios-distribution","eyebrow":"Distribution · distribution","keywords":"mappls-ui-widget-ios-distribution maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-ui-widget-ios-distribution-base","kind":"SDK & guide","title":"MapplsUIWidgets - UI Components SDK for iOS","description":"A versioned iOS distribution package used to integrate maps, search places, routes navigation, tracking telematics, widgets deep links, capture feedback, identity platform into an application.","href":"/sdks/mappls-ui-widget-ios-distribution-base","eyebrow":"Distribution · distribution","keywords":"mappls-ui-widget-ios-distribution-base maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform iOS Swift Text"},{"id":"sdk-guide:mappls-web-maps","kind":"SDK & guide","title":"Sign up for Mappls","description":"A Mappls guide for maps, search places, routes navigation, gis analytics, widgets deep links, capture feedback, identity platform across Web.","href":"/reference/mappls-web-maps","eyebrow":"Guide · current","keywords":"mappls-web-maps maps search-places routes-navigation gis-analytics widgets-deep-links capture-feedback identity-platform Web JavaScript licensed-entitlement"},{"id":"sdk-guide:mappls-web-maps-js","kind":"SDK & guide","title":"Mappls Web Maps JS","description":"Mappls's Latest Vector Maps Web SDK for rendering beautifully interactive, fluid maps that are powered by browser based WebGL.","href":"/reference/mappls-web-maps-js","eyebrow":"Guide · current","keywords":"mappls-web-maps-js maps search-places routes-navigation gis-analytics widgets-deep-links capture-feedback identity-platform Web HTML Text JavaScript static-key-2025 oauth2 api-key"},{"id":"sdk-guide:mappls-web-plugins","kind":"SDK & guide","title":"Mappls Web Plugins","description":"Web plugins provided by Mappls. This library is compatible with both our Web SDKs - Vector Maps & our legacy Raster Maps.","href":"/reference/mappls-web-plugins","eyebrow":"Widget · current","keywords":"mappls-web-plugins maps search-places routes-navigation tracking-telematics widgets-deep-links capture-feedback identity-platform Web Widgets/Deep links static-key-2025 oauth2 api-key"},{"id":"sdk-guide:mappls-workmate-android-sdk","kind":"SDK & guide","title":"Workmate SDK - Android","description":"Native Android SDK for our Workforce Management & Automation Solution - Workmate","href":"/sdks/mappls-workmate-android-sdk","eyebrow":"SDK · current","keywords":"mappls-workmate-android-sdk tracking-telematics workforce identity-platform Android"},{"id":"sdk-guide:skydnn-aiapi-docs","kind":"SDK & guide","title":"Skydnn AI APIs","description":"A Mappls rest api for maps, gis analytics, ai vision, capture feedback across REST, AI/MCP.","href":"/reference/skydnn-aiapi-docs","eyebrow":"REST API · current","keywords":"skydnn-aiapi-docs maps gis-analytics ai-vision capture-feedback REST AI/MCP"},{"id":"sdk-guide:v1-2-0-logs","kind":"SDK & guide","title":"V1.2.0 Logs","description":"Retail and Logistics Logs for 1.2.0","href":"/reference/v1-2-0-logs","eyebrow":"Sample · current","keywords":"v1.2.0-logs other Unspecified"},{"id":"migration:core-rest-generation","kind":"Migration","title":"Core REST: MapmyIndia generation to Mappls contracts","description":"Move trusted-server integrations across host, path, authentication, schema, and quota generations with contract evidence instead of string replacement.","href":"/migrate/core-rest-generation","eyebrow":"REST · high risk · direct-lineage","keywords":"Maps, search, routing, and geospatial APIs hybrid mapmyindia-api-addendums mapmyindia-rest-api mappls-rest-apis Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:web-maps-and-plugins","kind":"Migration","title":"Web maps and plugins: legacy scripts to a governed browser boundary","description":"Replace global-script assumptions with explicit origin restrictions, lifecycle ownership, typed adapters, accessible fallbacks, and measured rendering parity.","href":"/migrate/web-maps-and-plugins","eyebrow":"Web · high risk · adjacent-evidence","keywords":"Maps, places, directions, analytics, telematics, and widgets hybrid mapmyindia-geoanalytics-api-web mapmyindia-interactive-map-js-api mapmyindia-intouch-web-plugins mapmyindia-nearby-covid-places mapmyindia-places-n-directions-web-sdk mapmyindia-vector-maps-js-web-sdk mappls-web-maps mappls-web-maps-js mappls-web-plugins Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Rendering parity covers camera, bounds, projection, markers, layers, controls, gestures, accessibility, printing, and high-density datasets. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:intouch-android","kind":"Migration","title":"InTouch Android SDK lineage","description":"Migrate tracking journeys as consent-aware state machines, preserving session identity, offline queues, background policy, and event ordering across SDK lines.","href":"/migrate/intouch-android","eyebrow":"Android · critical risk · direct-lineage","keywords":"Tracking, telematics, events, geofences, and workforce stateful mapmyindia-intouch-android-sdk mappls-intouch-android-sdk Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Consent, notification, background-location, reboot, reinstall, offline buffering, clock skew, and logout behavior are journey-tested. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:intouch-react-native","kind":"Migration","title":"InTouch React Native bridge lineage","description":"Align JavaScript, wrapper, and both native dependency graphs while keeping tracking identity and recovery above the bridge.","href":"/migrate/intouch-react-native","eyebrow":"React Native · critical risk · direct-lineage","keywords":"Cross-platform tracking and workforce stateful mapmyindia-intouch-react-native-sdk mappls-react-native-intouch-sdk Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Android and iOS are accepted separately; success on one platform never stands in for the other. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:intouch-ios","kind":"Migration","title":"InTouch iOS SDK lineage","description":"Move the explicitly deprecated MapmyIndia iOS tracking line to a release-qualified Mappls SDK while preserving durable session identity, consent, background execution, event order, and unknown-outcome recovery.","href":"/migrate/intouch-ios","eyebrow":"iOS · critical risk · direct-lineage","keywords":"Tracking, telematics, consent, events, and geofences stateful mapmyindia-intouch-ios-sdk mappls-intouch-ios-sdk Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Consent, precise/reduced location, background modes, scenes, suspension, force quit, reboot, offline buffering, clock skew, logout, and data retirement are journey-tested. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:intouch-rest-generation","kind":"Migration","title":"InTouch REST contract generation","description":"Re-contract a stateful telematics integration without confusing a newer repository name with a confirmed endpoint or write-compatible product generation.","href":"/migrate/intouch-rest-generation","eyebrow":"REST · critical risk · selection-required","keywords":"Assets, trips, events, geofences, and telematics stateful mapmyindia-intouch-rest-apis mappls-intouch-rest-apis Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Every aggregate has a transition table, idempotency identity, event-order rule, reconciliation query, retention policy, and retirement path. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:cordova-ionic-exit","kind":"Migration","title":"Cordova and Ionic: stabilize, then migrate by journey","description":"Turn an aging hybrid integration into replaceable application capabilities, then move complete journeys to a confirmed web, native, or cross-platform target.","href":"/migrate/cordova-ionic-exit","eyebrow":"Cordova · critical risk · selection-required","keywords":"Hybrid maps, search, routing, and widgets hybrid mapmyindia-map-cordova-ionic-beta mapmyindia-restapi-cordova-ionic-beta mappls-react-native-sdk mappls-flutter-sdk mappls-rest-apis Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Deep links, authentication return paths, analytics identity, local storage, accessibility, navigation, and app-update behavior survive mixed old/new screens. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:react-native-maps","kind":"Migration","title":"React Native maps and REST wrappers","description":"Move beta-era bridges to a release-specific Mappls wrapper while testing the Android and iOS implementations as separate products.","href":"/migrate/react-native-maps","eyebrow":"React Native · high risk · direct-lineage","keywords":"Maps, places, routes, and geospatial UI hybrid mapmyindia-map-react-native-beta mapmyindia-restapi-react-native-beta mappls-react-native-sdk Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Camera, projection, annotations, layers, gestures, events, deep links, accessibility, and teardown are verified independently on Android and iOS. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:flutter-map-lineage","kind":"Migration","title":"Flutter map plugin lineage","description":"Replace the explicitly obsolete MapmyIndia Flutter plugin with a release-qualified Mappls line while treating Dart, Android, iOS, and native SDK versions as one reproducible compatibility graph.","href":"/migrate/flutter-map-lineage","eyebrow":"Flutter · high risk · direct-lineage","keywords":"Maps, places, routes, platform views, and cross-platform lifecycle hybrid flutter-mapmyindia-gl mappls-flutter-sdk Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Dart/Flutter, Android/iOS SDKs, platform views, renderer, permissions, callbacks, restoration, release archives, accessibility, and performance are accepted separately per platform. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:android-map-lineage","kind":"Migration","title":"Android vector map SDK lineage","description":"Move the explicitly deprecated MapmyIndia vector SDK line to an approved Mappls Android release through a narrow application map boundary and a clean device/release qualification matrix.","href":"/migrate/android-map-lineage","eyebrow":"Android · high risk · direct-lineage","keywords":"Maps, camera, annotations, places, routes, and native lifecycle hybrid mapmyindia-maps-vectorsdk-android mappls-android-sdk Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Gradle/AGP/Kotlin/JDK, Android API/ABI, renderer, lifecycle, permissions, process recreation, accessibility, memory, battery, and release signing are qualified together. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:ios-map-packages","kind":"Migration","title":"iOS map and API package lineage","description":"Resolve modular Swift package/distribution lines as one compatible release set and keep Mappls symbols behind testable Swift protocols.","href":"/migrate/ios-map-packages","eyebrow":"iOS · high risk · direct-lineage","keywords":"Maps, places, routing, UI extensions, and capture hybrid mapmyindia-maps-vectorsdk-ios mappls-ios-sdk mappls-map-ios-distribution mappls-api-kit-ios-distribution Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Swift/Xcode/deployment targets, package/binary checksums, privacy manifests, purpose strings, scenes, background modes, and extension packages are resolved together. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:mgis-workspace-generation","kind":"Migration","title":"mGIS and GeoAnalytics workspace generation","description":"Contain legacy mGIS API/library contracts behind a durable workspace seam, then select the entitled current dataset, web-method, analysis, and deployment surfaces without inventing replacement endpoints.","href":"/migrate/mgis-workspace-generation","eyebrow":"Web · critical risk · selection-required","keywords":"Datasets, layers, styles, spatial analysis, visualization, publication, and export stateful mapmyindia-mgis-apis mapmyindia-mgis-libraries mappls-web-maps-js mappls-rest-apis Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Dataset ingestion, validation, immutable versioning, publication, style, analysis, export, share/revoke, lineage, privacy, residency, retention, backup, reconciliation, and retirement are tested end to end. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"migration:workmate-workforce","kind":"Migration","title":"Workmate and workforce journeys","description":"Reframe deprecated Workmate surfaces around durable workforce aggregates, then select the entitled Mappls modules that satisfy each complete journey.","href":"/migrate/workmate-workforce","eyebrow":"Android · critical risk · selection-required","keywords":"Tasks, workers, attendance, proof, and operational tracking stateful mapmyindia-workmate-apis mappls-workmate-android-sdk mappls-intouch-android-sdk mappls-location-capture-android-sdk mappls-rest-apis Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together. Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption. Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data. Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies. Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover. Assignment, accept, travel, arrive, proof, exception, complete, cancel, sync, supervisor correction, offboarding, and audit retention are tested end to end. The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region. Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator. Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences. A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression."},{"id":"tutorial:first-web-map","kind":"Tutorial","title":"Put your first Mappls map on the web","description":"Create a key, restrict it to localhost, load Web Maps JS, and add a marker.","href":"/tutorials/first-web-map","eyebrow":"Beginner · 10 min","keywords":"A responsive map with a styled point of interest. Web maps invalid or origin-restricted key SDK load timeout zero-size or detached container"},{"id":"tutorial:address-autocomplete","kind":"Tutorial","title":"Build address autocomplete that users trust","description":"Debounce input, apply bias, handle keyboard selection, and retain the Mappls Pin.","href":"/tutorials/address-autocomplete","eyebrow":"Beginner · 20 min","keywords":"An accessible, resilient delivery-address field. Web REST search-places out-of-order response no suggestions or ambiguous address quota or authentication denial"},{"id":"tutorial:android-map","kind":"Tutorial","title":"Add Mappls to an Android app","description":"Configure the repository and BoM, initialize the SDK, and manage MapView lifecycle.","href":"/tutorials/android-map","eyebrow":"Beginner · 25 min","keywords":"A native Kotlin map screen with lifecycle-safe setup. Android maps dependency/version mismatch permission revoked while active activity recreated after process death"},{"id":"tutorial:ios-map","kind":"Tutorial","title":"Add Mappls to an iOS app with Swift Package Manager","description":"Select distribution packages, configure credentials, and render the native map.","href":"/tutorials/ios-map","eyebrow":"Beginner · 25 min","keywords":"A native Swift map screen. iOS maps package resolution conflict view recreated with duplicate delegates location authorization changes at runtime"},{"id":"tutorial:route-preview","kind":"Tutorial","title":"Build a route preview with alternatives","description":"Resolve endpoints, request alternatives, decode geometry, and explain toll/time trade-offs.","href":"/tutorials/route-preview","eyebrow":"Intermediate · 35 min","keywords":"A production-pattern route comparison view. Web REST routes-navigation maps one endpoint is unresolved provider returns no route late response targets an obsolete itinerary"},{"id":"tutorial:nearby-discovery","kind":"Tutorial","title":"Create a nearby discovery experience","description":"Combine category search, viewport updates, result cards, and map selection.","href":"/tutorials/nearby-discovery","eyebrow":"Intermediate · 40 min","keywords":"A map-and-list place explorer. Web search-places maps location unavailable provider results outside requested radius selected place disappears after filter change"},{"id":"tutorial:delivery-eta","kind":"Tutorial","title":"Track a delivery with a trustworthy ETA","description":"Join asset telemetry, map matching, route progress, ETA refresh, and customer visibility.","href":"/tutorials/delivery-eta","eyebrow":"Advanced · 90 min","keywords":"A stateful live-delivery journey with recovery and replay. REST Web intouch-telematics routes-navigation telemetry silence route deviation or closed road provider close succeeds after local timeout"},{"id":"tutorial:workmate-task-lifecycle","kind":"Tutorial","title":"Automate a complete Workmate task lifecycle","description":"Provision workers, dispatch jobs, consume transitions, enforce proof, and reconcile closure.","href":"/tutorials/workmate-task-lifecycle","eyebrow":"Advanced · 2 hr","keywords":"An idempotent field-service integration. REST Android workmate assignee rejects or becomes unavailable proof is incomplete or rejected provider timeout after accepting a command"},{"id":"tutorial:fleet-geofences","kind":"Tutorial","title":"Build fleet geofence operations","description":"Create zones, process enter/exit events, suppress noise, and power an exception queue.","href":"/tutorials/fleet-geofences","eyebrow":"Advanced · 75 min","keywords":"An operations-ready geofence monitor. REST Web intouch-telematics maps invalid or oversized geometry duplicate provider activity rule retirement fails after local request"},{"id":"tutorial:gis-site-selection","kind":"Tutorial","title":"Build a reproducible site-selection model","description":"Publish layers, generate catchments, join signals, score candidates, and share results.","href":"/tutorials/gis-site-selection","eyebrow":"Advanced · 2 hr","keywords":"A governed retail expansion analysis. REST Web gis-analytics source schema or CRS drift processing fails after partial compute expired or revoked share is requested"},{"id":"tutorial:offline-package-update","kind":"Tutorial","title":"Design an interruption-safe offline map update","description":"Verify packages, stage data, check compatibility, switch atomically, and roll back.","href":"/tutorials/offline-package-update","eyebrow":"Advanced · 90 min","keywords":"A resilient embedded update state machine. Automotive Linux offline-automotive insufficient storage signature or compatibility mismatch first boot fails after activation"},{"id":"tutorial:mappls-mcp-agent","kind":"Tutorial","title":"Give an AI agent grounded Mappls tools","description":"Run the MCP server, scope credentials, call search and routing tools, and inspect provenance.","href":"/tutorials/mappls-mcp-agent","eyebrow":"Intermediate · 30 min","keywords":"An agent that can reason about real places without inventing APIs. MCP ai-location search-places routes-navigation remote client is rejected by auth, URL, host, origin, size, or capacity controls authorization-server lifecycle or revocation is unavailable configured profile does not advertise a planned tool approval expires before execution provider result lacks provenance or conflicts with prior context"},{"id":"tutorial:a2a-solution-coordination","kind":"Tutorial","title":"Coordinate a complete Mappls A2A journey","description":"Validate fixture or OAuth A2A identity, select offline or purpose-bound live-read authority, delegate one exact structured task, reconcile a lost response, bind the server task identity, and review an immutable artifact.","href":"/tutorials/a2a-solution-coordination","eyebrow":"Advanced · 90 min","keywords":"A restart-safe OAuth-capable host that keeps transport identity, provider-read purpose, protocol completion, human acceptance, entitlement, writes, and production approval separate. MCP ai-location search-places routes-navigation intouch-telematics Agent Card changes profile, authority, protocol, skill, size, OAuth metadata, or scope authorization is missing, expired, revoked, wrong-audience, or tenant-mismatched purpose or data class is incompatible with the selected live skill transport outcome is ambiguous and context resolves to zero or multiple tasks task or context identity drifts artifact is nonterminal, unstructured, oversized, or elevates provider calls or writes review names a stale digest or aggregate version exact idempotency key is replayed with changed intent"},{"id":"tutorial:mcp-client-identity","kind":"Tutorial","title":"Provision and validate a remote MCP client","description":"Approve exact authority, deliver a signed pre-registration event, inspect discovery, validate PKCE and resource binding, then revoke without transporting a token or secret.","href":"/tutorials/mcp-client-identity","eyebrow":"Advanced · 55 min","keywords":"A replay-safe client identity journey with durable registration, request checks, revocation, and audit evidence. MCP ai-location signature is wrong, stale, replayed with changed bytes, or too large authorization-server mutation succeeds but the response is lost callback, resource audience, PKCE method, or requested scope drifts revocation targets an unknown or already retired external identity"},{"id":"tutorial:webhook-reliability","kind":"Tutorial","title":"Consume Mappls events exactly once in effect","description":"Verify signatures, deduplicate deliveries, order per aggregate, retry, and replay safely.","href":"/tutorials/webhook-reliability","eyebrow":"Advanced · 55 min","keywords":"A production webhook ingestion pipeline. REST intouch-telematics workmate gis-analytics DNS changes to any non-public address receiver returns a redirect ownership challenge expires or is superseded signature is stale or invalid database commits but response is lost event arrives before its prerequisite"},{"id":"tutorial:oauth-server-integration","kind":"Tutorial","title":"Call Mappls safely from a trusted server","description":"Exchange OAuth client credentials, keep tokens in bearer headers, call typed Search and Route operations, preserve provenance, and bound retry.","href":"/tutorials/oauth-server-integration","eyebrow":"Intermediate · 35 min","keywords":"A credential-safe live server boundary with typed errors, timeout, retry, and provider provenance. REST search-places routes-navigation intouch-telematics token endpoint denied or unavailable provider returns 429 or 5xx timeout occurs after a stateful provider commit"},{"id":"tutorial:react-native-map","kind":"Tutorial","title":"Build a cross-platform React Native map","description":"Install the native wrapper, configure both platforms, add annotations, and handle cleanup.","href":"/tutorials/react-native-map","eyebrow":"Intermediate · 45 min","keywords":"One map experience across Android and iOS. React Native maps wrapper/native version skew bridge receives events after unmount one platform denies location permission"},{"id":"tutorial:flutter-map","kind":"Tutorial","title":"Build a Flutter map and place picker","description":"Configure native keys, render the map, and return a validated place to your form.","href":"/tutorials/flutter-map","eyebrow":"Intermediate · 45 min","keywords":"A reusable cross-platform location field. Flutter maps search-places plugin/native SDK mismatch late suggestion after widget disposal camera moved after a prior selection"},{"id":"tutorial:deep-link-campaign","kind":"Tutorial","title":"Create a zero-SDK location campaign","description":"Build safe place links, add fallback behavior, instrument hand-offs, and test every device.","href":"/tutorials/deep-link-campaign","eyebrow":"Beginner · 15 min","keywords":"A campaign that opens a useful Mappls experience everywhere. Deep links app-widgets-deep-links app not installed link association misconfigured messaging client strips or rewrites parameters"},{"id":"tutorial:rest-geocode-service","kind":"Tutorial","title":"Build a server-side geocoding boundary","description":"Resolve addresses on a trusted server, retain provider identity, and return a narrow application contract.","href":"/tutorials/rest-geocode-service","eyebrow":"Beginner · 25 min","keywords":"A credential-safe geocoding service with typed errors and provenance. REST search-places invalid address input no candidate or multiple candidates token, quota, or provider timeout"},{"id":"tutorial:reverse-geocode-check-in","kind":"Tutorial","title":"Turn a device fix into a trustworthy check-in","description":"Reverse geocode accuracy-bearing coordinates, preserve consent, and distinguish evidence from an address label.","href":"/tutorials/reverse-geocode-check-in","eyebrow":"Beginner · 30 min","keywords":"A privacy-aware check-in that retains both raw evidence and human-readable context. REST search-places capture-feedback permission or consent absent stale or inaccurate fix reverse geocoder returns no address"},{"id":"tutorial:static-map-receipt","kind":"Tutorial","title":"Generate static maps for receipts and notifications","description":"Render bounded server-side map imagery with safe markers, caching, attribution, and fallback text.","href":"/tutorials/static-map-receipt","eyebrow":"Beginner · 20 min","keywords":"A deterministic map image pipeline for non-interactive surfaces. REST maps render service timeout unsupported or excessive geometry email proxy strips the image"},{"id":"tutorial:web-widget-place-picker","kind":"Tutorial","title":"Embed a place picker widget","description":"Mount a bounded widget, synchronize selection with your form, and preserve the selected Mappls Pin.","href":"/tutorials/web-widget-place-picker","eyebrow":"Beginner · 25 min","keywords":"An accessible embedded place picker with explicit host-page ownership. Widgets Web app-widgets-deep-links search-places widget script or frame blocked message schema/version changes duplicate or late terminal callback host text edited after widget selection"},{"id":"tutorial:navigation-deep-link","kind":"Tutorial","title":"Hand off to navigation with a resilient deep link","description":"Encode a known place, protect campaign parameters, and provide browser and store fallbacks.","href":"/tutorials/navigation-deep-link","eyebrow":"Beginner · 20 min","keywords":"A tested app-to-navigation hand-off across installed and uninstalled states. Deep links app-widgets-deep-links routes-navigation app absent or association invalid unsupported travel profile device is offline at hand-off"},{"id":"tutorial:cordova-map","kind":"Tutorial","title":"Ship a Mappls map in Cordova and Ionic","description":"Separate web and native configuration, wait for device readiness, and clean up plugin state safely.","href":"/tutorials/cordova-map","eyebrow":"Intermediate · 50 min","keywords":"A hybrid map screen with lifecycle-safe native bridge handling. Cordova maps search-places JavaScript calls before device readiness native view survives page teardown platform/plugin version mismatch"},{"id":"tutorial:xamarin-map","kind":"Tutorial","title":"Integrate Mappls into a Xamarin application","description":"Configure platform projects, isolate credentials, bridge native lifecycle, and preserve location identity in shared code.","href":"/tutorials/xamarin-map","eyebrow":"Intermediate · 55 min","keywords":"A shared-code location feature backed by correctly owned native map views. Xamarin maps search-places NuGet/native dependency conflict renderer recreated without disposal one platform returns a partial place result"},{"id":"tutorial:distance-matrix-dispatch","kind":"Tutorial","title":"Rank responders with a distance matrix","description":"Batch eligible origins, interpret unreachable pairs, apply deterministic tie-breaks, and keep dispatch explainable.","href":"/tutorials/distance-matrix-dispatch","eyebrow":"Intermediate · 45 min","keywords":"An explainable ETA-based dispatch shortlist rather than a straight-line guess. REST routes-navigation search-places candidate telemetry is stale matrix returns partial/unreachable pairs incident changes while ranking is in flight"},{"id":"tutorial:traffic-aware-commute","kind":"Tutorial","title":"Build a traffic-aware commute assistant","description":"Compare departure choices, refresh bounded route alternatives, and explain when an ETA becomes stale.","href":"/tutorials/traffic-aware-commute","eyebrow":"Intermediate · 50 min","keywords":"A route comparison experience that communicates freshness and uncertainty. Web REST routes-navigation maps traffic data becomes stale route changes during user selection provider returns a slower partial response"},{"id":"tutorial:geojson-operations-layer","kind":"Tutorial","title":"Render a governed GeoJSON operations layer","description":"Validate geometry, assign stable feature IDs, style deterministically, and synchronize map and table selection.","href":"/tutorials/geojson-operations-layer","eyebrow":"Intermediate · 55 min","keywords":"An accessible map layer whose visual state is reproducible from source data. Web maps gis-analytics unsupported geometry or CRS duplicate/missing feature identity large collection exceeds render budget"},{"id":"tutorial:linux-map-client","kind":"Tutorial","title":"Operate a Mappls client on embedded Linux","description":"Separate runtime and map-data compatibility, stage updates, survive power loss, and expose health signals.","href":"/tutorials/linux-map-client","eyebrow":"Advanced · 2 hr","keywords":"An embedded map runtime with atomic data activation and rollback evidence. Linux Automotive offline-automotive maps GPU/runtime incompatibility disk pressure during staging power loss between switch and acknowledgement"},{"id":"tutorial:intouch-trip-lifecycle","kind":"Tutorial","title":"Reconcile a complete InTouch trip lifecycle","description":"Create provider identity, consume event-time telemetry, own exceptions, and close only after provider acknowledgement.","href":"/tutorials/intouch-trip-lifecycle","eyebrow":"Advanced · 2 hr","keywords":"A restart-safe connected trip with replay, late evidence, and closure reconciliation. REST Web intouch-telematics routes-navigation provider accepts command but response is lost telemetry gap or route deviation closure requested with open exception"},{"id":"tutorial:workmate-proof-review","kind":"Tutorial","title":"Build proof review and rework for field jobs","description":"Capture purpose-bound evidence, route weak submissions to review, request rework, and preserve decision history.","href":"/tutorials/workmate-proof-review","eyebrow":"Advanced · 90 min","keywords":"An auditable proof workflow that cannot silently overwrite rejected evidence. REST Android workmate capture-feedback offline duplicate submission media upload succeeds but command times out review policy changes during rework"},{"id":"tutorial:cordova-release-hardening","kind":"Tutorial","title":"Qualify a Cordova location release","description":"Pin bridge and native dependencies, prove lifecycle disposal, automate both release builds, and operate a browser fallback.","href":"/tutorials/cordova-release-hardening","eyebrow":"Advanced · 80 min","keywords":"A versioned hybrid release with reproducible native builds, safe teardown, and rollback. Cordova maps search-places routes-navigation plugin and native SDK version drift WebView survives route teardown one store release rejects the configured entitlement"},{"id":"tutorial:deep-link-attribution-resilience","kind":"Tutorial","title":"Operate deep links across every hand-off","description":"Govern destination identity, universal-link association, privacy-safe attribution, fallback, expiry, and campaign retirement.","href":"/tutorials/deep-link-attribution-resilience","eyebrow":"Advanced · 70 min","keywords":"A measurable zero-SDK journey that never confuses a click with arrival. Deep links app-widgets-deep-links routes-navigation search-places association file is stale or unavailable messaging client strips parameters app opens but does not acknowledge the intended destination"},{"id":"tutorial:flutter-production-lifecycle","kind":"Tutorial","title":"Production-harden a Flutter location feature","description":"Lock Dart/native compatibility, control rebuilds and streams, test process recovery, and qualify Android and iOS independently.","href":"/tutorials/flutter-production-lifecycle","eyebrow":"Advanced · 90 min","keywords":"A cross-platform feature with stable identity, bounded bridge traffic, and deterministic disposal. Flutter maps search-places routes-navigation capture-feedback plugin/native architecture mismatch late stream event after disposal one platform restores an obsolete controller generation"},{"id":"tutorial:ios-sdk-production-readiness","kind":"Tutorial","title":"Qualify an iOS Mappls release","description":"Resolve package authority, bind credentials and entitlements, own controller generations, test privacy and background behavior, and prove rollback.","href":"/tutorials/ios-sdk-production-readiness","eyebrow":"Advanced · 2 hr","keywords":"A clean-device iOS qualification record spanning SDK, widget, tracking, and distribution boundaries. iOS maps search-places routes-navigation intouch-telematics workmate capture-feedback app-widgets-deep-links offline-automotive ai-location package exists but owning product contract is unclear delegate callback arrives after replacement background permission or entitlement changes during an active journey"},{"id":"tutorial:ios-direction-geofence-handoffs","kind":"Tutorial","title":"Build restart-safe iOS direction and geofence handoffs","description":"Own native editor generations, validate route and geometry candidates, provide an exact navigation-link fallback, separate target acknowledgement and application review, and recover safely after restart.","href":"/tutorials/ios-direction-geofence-handoffs","eyebrow":"Advanced · 95 min","keywords":"Two tested, durable iOS handoff journeys with explicit provider and application evidence boundaries. iOS app-widgets-deep-links routes-navigation intouch-telematics native UI is unavailable and the app link is not installed a callback arrives from an old presentation or route revision the route index or intent differs from the active draft circle or polygon violates geometry policy navigation target times out after request no authoritative entitled geofence publication contract is selected"},{"id":"tutorial:react-native-native-parity","kind":"Tutorial","title":"Qualify React Native native parity","description":"Freeze wrapper/native versions, normalize cross-platform results, constrain bridge traffic, recover process death, and release both native targets.","href":"/tutorials/react-native-native-parity","eyebrow":"Advanced · 100 min","keywords":"One JavaScript contract backed by independently qualified Android and iOS behavior. React Native maps search-places routes-navigation intouch-telematics workmate capture-feedback wrapper compiles against only one native SDK line JavaScript reload leaves a native session active platform permission semantics produce different unhandled states"},{"id":"tutorial:widget-host-production","kind":"Tutorial","title":"Operate widgets as untrusted lifecycle surfaces","description":"Validate origin and schema, separate candidate from commit, recover blocked embeds, preserve accessibility, and retire safely.","href":"/tutorials/widget-host-production","eyebrow":"Advanced · 85 min","keywords":"A restart-safe host journey with exact-origin validation and a complete non-widget fallback. Widgets app-widgets-deep-links search-places routes-navigation intouch-telematics capture-feedback CSP or browser blocks the widget message contract changes without version negotiation late callback targets an edited or submitted host record"},{"id":"tutorial:xamarin-maintenance-migration","kind":"Tutorial","title":"Harden and migrate a Xamarin location feature","description":"Inventory native dependencies, isolate shared state, qualify each renderer, add rollback, and prepare a controlled successor migration.","href":"/tutorials/xamarin-maintenance-migration","eyebrow":"Advanced · 2 hr","keywords":"A supportable existing integration with explicit compatibility, teardown, and migration evidence. Xamarin maps search-places routes-navigation binding references an unavailable native symbol renderer lifecycle differs across OS versions successor adapter changes place identity or cancellation semantics"},{"id":"recipe:last-mile-delivery-request-response","kind":"Recipe","title":"Contract slice: A delivery promise customers can trust","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/last-mile-delivery-request-response","eyebrow":"Logistics · stateless · 35–50 min","keywords":"Fewer failed deliveries and a live, explainable ETA from checkout to doorstep. Checkout customer Dispatch planner First-attempt delivery rate Cost per stop ETA error Distance per order Search & Places Routes & Navigation InTouch Telematics Capture & Feedback Normalize the destination and retain its Mappls Pin Order system of record Ambiguous apartment entrance Optimize stops against capacity and time windows Location normalization Driver telemetry goes silent Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:last-mile-delivery-composed-experience","kind":"Recipe","title":"Application flow: A delivery promise customers can trust","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/last-mile-delivery-composed-experience","eyebrow":"Logistics · hybrid · 90–120 min","keywords":"Fewer failed deliveries and a live, explainable ETA from checkout to doorstep. Checkout customer Dispatch planner Driver Customer-support agent First-attempt delivery rate Cost per stop ETA error Distance per order Search & Places Routes & Navigation InTouch Telematics Capture & Feedback Normalize the destination and retain its Mappls Pin Order system of record Ambiguous apartment entrance Optimize stops against capacity and time windows Location normalization Driver telemetry goes silent Navigate with live rerouting Planning and guidance Provider accepts a route/trip command after timeout Stream driver and order state Trip evidence Ambiguous apartment entrance Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:last-mile-delivery-durable-operation","kind":"Recipe","title":"Operating journey: A delivery promise customers can trust","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/last-mile-delivery-durable-operation","eyebrow":"Logistics · stateful · 2–3 hr","keywords":"Fewer failed deliveries and a live, explainable ETA from checkout to doorstep. Checkout customer Dispatch planner Driver Customer-support agent Transport partner First-attempt delivery rate Cost per stop ETA error Distance per order Search & Places Routes & Navigation InTouch Telematics Capture & Feedback Normalize the destination and retain its Mappls Pin Order system of record Ambiguous apartment entrance Optimize stops against capacity and time windows Location normalization Driver telemetry goes silent Navigate with live rerouting Planning and guidance Provider accepts a route/trip command after timeout Stream driver and order state Trip evidence Ambiguous apartment entrance Capture geotagged proof and reconcile exceptions Customer and operations views Driver telemetry goes silent Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:ride-hailing-request-response","kind":"Recipe","title":"Contract slice: A pickup flow that survives the real world","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/ride-hailing-request-response","eyebrow":"Mobility · stateless · 35–50 min","keywords":"Shorter pickup times with fewer calls, cancellations, and unsafe rendezvous points. Rider Driver Pickup ETA Cancellation rate Driver idle distance Pickup support contacts Maps Search & Places Routes & Navigation InTouch Telematics Bias search to the rider viewport Trip marketplace Search resolves the building centre Confirm a precise pickup pin and landmark Pickup intent Driver location is stale Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby A2A Solution Studio"},{"id":"recipe:ride-hailing-composed-experience","kind":"Recipe","title":"Application flow: A pickup flow that survives the real world","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/ride-hailing-composed-experience","eyebrow":"Mobility · hybrid · 90–120 min","keywords":"Shorter pickup times with fewer calls, cancellations, and unsafe rendezvous points. Rider Driver Marketplace dispatcher Safety operator Pickup ETA Cancellation rate Driver idle distance Pickup support contacts Maps Search & Places Routes & Navigation InTouch Telematics Bias search to the rider viewport Trip marketplace Search resolves the building centre Confirm a precise pickup pin and landmark Pickup intent Driver location is stale Match with network-aware ETA ETA matching Rider and driver disagree on arrival Track approach and reroute Approach journey Search resolves the building centre Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby A2A Solution Studio"},{"id":"recipe:ride-hailing-durable-operation","kind":"Recipe","title":"Operating journey: A pickup flow that survives the real world","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/ride-hailing-durable-operation","eyebrow":"Mobility · stateful · 2–3 hr","keywords":"Shorter pickup times with fewer calls, cancellations, and unsafe rendezvous points. Rider Driver Marketplace dispatcher Safety operator Customer support Pickup ETA Cancellation rate Driver idle distance Pickup support contacts Maps Search & Places Routes & Navigation InTouch Telematics Bias search to the rider viewport Trip marketplace Search resolves the building centre Confirm a precise pickup pin and landmark Pickup intent Driver location is stale Match with network-aware ETA ETA matching Rider and driver disagree on arrival Track approach and reroute Approach journey Search resolves the building centre Detect arrival and close the trip Shared rendezvous experience Driver location is stale Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby A2A Solution Studio"},{"id":"recipe:field-service-request-response","kind":"Recipe","title":"Contract slice: Dispatch the right technician, with the right proof","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/field-service-request-response","eyebrow":"Utilities · stateless · 35–50 min","keywords":"Higher first-time-fix rates and auditable work from dispatch through customer sign-off. Service requester Dispatcher First-time-fix rate Jobs per shift SLA compliance Repeat visit rate Workmate Routes & Navigation Capture & Feedback GIS & Analytics Geocode and classify the service location Work-order system Technician accepts while another assignment races Assign by skills, shift, inventory, and ETA Spatial service context Offline commands replay after reassignment Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:field-service-composed-experience","kind":"Recipe","title":"Application flow: Dispatch the right technician, with the right proof","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/field-service-composed-experience","eyebrow":"Utilities · hybrid · 90–120 min","keywords":"Higher first-time-fix rates and auditable work from dispatch through customer sign-off. Service requester Dispatcher Technician Proof reviewer First-time-fix rate Jobs per shift SLA compliance Repeat visit rate Workmate Routes & Navigation Capture & Feedback GIS & Analytics Geocode and classify the service location Work-order system Technician accepts while another assignment races Assign by skills, shift, inventory, and ETA Spatial service context Offline commands replay after reassignment Guide the technician Workmate lifecycle Proof is incomplete Collect checklist, image, and signature proof Technician experience Technician accepts while another assignment races Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:field-service-durable-operation","kind":"Recipe","title":"Operating journey: Dispatch the right technician, with the right proof","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/field-service-durable-operation","eyebrow":"Utilities · stateful · 2–3 hr","keywords":"Higher first-time-fix rates and auditable work from dispatch through customer sign-off. Service requester Dispatcher Technician Proof reviewer Operations manager First-time-fix rate Jobs per shift SLA compliance Repeat visit rate Workmate Routes & Navigation Capture & Feedback GIS & Analytics Geocode and classify the service location Work-order system Technician accepts while another assignment races Assign by skills, shift, inventory, and ETA Spatial service context Offline commands replay after reassignment Guide the technician Workmate lifecycle Proof is incomplete Collect checklist, image, and signature proof Technician experience Technician accepts while another assignment races Analyze repeat faults spatially Operations and analytics Offline commands replay after reassignment Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:energy-grid-resilience-request-response","kind":"Recipe","title":"Contract slice: Restore the grid from alarm to verified service","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/energy-grid-resilience-request-response","eyebrow":"Energy · stateless · 35–50 min","keywords":"Faster, safer restoration with an explainable view of affected assets, customers, crews, and residual risk. Grid control operator Outage coordinator Customers restored per hour SAIDI contribution Crew travel time Repeat outage rate GIS & Analytics InTouch Telematics Workmate Routes & Navigation Capture & Feedback Version the network and hazard context Network and hazard authority Many alarms collapse onto the wrong feeder Correlate alarms into bounded outage incidents Outage correlation A road route crosses a newly flooded segment Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:energy-grid-resilience-composed-experience","kind":"Recipe","title":"Application flow: Restore the grid from alarm to verified service","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/energy-grid-resilience-composed-experience","eyebrow":"Energy · hybrid · 90–120 min","keywords":"Faster, safer restoration with an explainable view of affected assets, customers, crews, and residual risk. Grid control operator Outage coordinator Switching authority Field crew Customers restored per hour SAIDI contribution Crew travel time Repeat outage rate GIS & Analytics InTouch Telematics Workmate Routes & Navigation Capture & Feedback Version the network and hazard context Network and hazard authority Many alarms collapse onto the wrong feeder Correlate alarms into bounded outage incidents Outage correlation A road route crosses a newly flooded segment Approve a switching and crew plan Switching and dispatch Crew completion arrives before telemetry recovery Guide crews and capture field evidence Field execution Many alarms collapse onto the wrong feeder Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:energy-grid-resilience-durable-operation","kind":"Recipe","title":"Operating journey: Restore the grid from alarm to verified service","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/energy-grid-resilience-durable-operation","eyebrow":"Energy · stateful · 2–3 hr","keywords":"Faster, safer restoration with an explainable view of affected assets, customers, crews, and residual risk. Grid control operator Outage coordinator Switching authority Field crew Customer-impact lead Customers restored per hour SAIDI contribution Crew travel time Repeat outage rate GIS & Analytics InTouch Telematics Workmate Routes & Navigation Capture & Feedback Version the network and hazard context Network and hazard authority Many alarms collapse onto the wrong feeder Correlate alarms into bounded outage incidents Outage correlation A road route crosses a newly flooded segment Approve a switching and crew plan Switching and dispatch Crew completion arrives before telemetry recovery Guide crews and capture field evidence Field execution Many alarms collapse onto the wrong feeder Reconcile telemetry, customer impact, and restoration Restoration reconciliation A road route crosses a newly flooded segment Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:retail-expansion-request-response","kind":"Recipe","title":"Contract slice: Choose the next store with evidence","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/retail-expansion-request-response","eyebrow":"Retail · stateless · 35–50 min","keywords":"Faster site screening and investment decisions grounded in a reusable spatial model. Expansion analyst GIS data steward Forecast accuracy Cannibalization risk Time to shortlist Revenue per catchment GIS & Analytics Search & Places Maps Publish candidate sites and performance data Enterprise data products Demographic feed changes mid-analysis Generate drive-time catchments mGIS version registry Candidate geometry has the wrong CRS Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:retail-expansion-composed-experience","kind":"Recipe","title":"Application flow: Choose the next store with evidence","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/retail-expansion-composed-experience","eyebrow":"Retail · hybrid · 90–120 min","keywords":"Faster site screening and investment decisions grounded in a reusable spatial model. Expansion analyst GIS data steward Real-estate manager Finance reviewer Forecast accuracy Cannibalization risk Time to shortlist Revenue per catchment GIS & Analytics Search & Places Maps Publish candidate sites and performance data Enterprise data products Demographic feed changes mid-analysis Generate drive-time catchments mGIS version registry Candidate geometry has the wrong CRS Join demand and competition signals Analysis engine Executive link is forwarded Score and compare candidates Analyst decision lab Demographic feed changes mid-analysis Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:retail-expansion-durable-operation","kind":"Recipe","title":"Operating journey: Choose the next store with evidence","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/retail-expansion-durable-operation","eyebrow":"Retail · stateful · 2–3 hr","keywords":"Faster site screening and investment decisions grounded in a reusable spatial model. Expansion analyst GIS data steward Real-estate manager Finance reviewer Executive approver Forecast accuracy Cannibalization risk Time to shortlist Revenue per catchment GIS & Analytics Search & Places Maps Publish candidate sites and performance data Enterprise data products Demographic feed changes mid-analysis Generate drive-time catchments mGIS version registry Candidate geometry has the wrong CRS Join demand and competition signals Analysis engine Executive link is forwarded Score and compare candidates Analyst decision lab Demographic feed changes mid-analysis Share an executive decision map Governed sharing Candidate geometry has the wrong CRS Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:banking-address-risk-request-response","kind":"Recipe","title":"Contract slice: Make address risk explainable","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/banking-address-risk-request-response","eyebrow":"Financial services · stateless · 35–50 min","keywords":"More straight-through approvals with a clear audit trail for ambiguous or high-risk addresses. Applicant Onboarding service Straight-through processing False-positive review rate Verification turnaround Fraud loss Search & Places Capture & Feedback GIS & Analytics Normalize the entered address Onboarding system Device fix is weak or unavailable Compare declared and captured locations Address normalization Address and device evidence disagree Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:banking-address-risk-composed-experience","kind":"Recipe","title":"Application flow: Make address risk explainable","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/banking-address-risk-composed-experience","eyebrow":"Financial services · hybrid · 90–120 min","keywords":"More straight-through approvals with a clear audit trail for ambiguous or high-risk addresses. Applicant Onboarding service Risk analyst Manual reviewer Straight-through processing False-positive review rate Verification turnaround Fraud loss Search & Places Capture & Feedback GIS & Analytics Normalize the entered address Onboarding system Device fix is weak or unavailable Compare declared and captured locations Address normalization Address and device evidence disagree Join serviceability and risk zones Evidence service Precise evidence reaches retention limit Score confidence with reasons Risk policy engine Device fix is weak or unavailable Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:banking-address-risk-durable-operation","kind":"Recipe","title":"Operating journey: Make address risk explainable","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/banking-address-risk-durable-operation","eyebrow":"Financial services · stateful · 2–3 hr","keywords":"More straight-through approvals with a clear audit trail for ambiguous or high-risk addresses. Applicant Onboarding service Risk analyst Manual reviewer Compliance auditor Straight-through processing False-positive review rate Verification turnaround Fraud loss Search & Places Capture & Feedback GIS & Analytics Normalize the entered address Onboarding system Device fix is weak or unavailable Compare declared and captured locations Address normalization Address and device evidence disagree Join serviceability and risk zones Evidence service Precise evidence reaches retention limit Score confidence with reasons Risk policy engine Device fix is weak or unavailable Escalate only unresolved cases Audit and privacy controls Address and device evidence disagree Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:insurance-claims-request-response","kind":"Recipe","title":"Contract slice: Evidence-led claims from incident to settlement","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/insurance-claims-request-response","eyebrow":"Insurance · stateless · 35–50 min","keywords":"Faster, more consistent claims decisions with tamper-aware spatial evidence. Policyholder Claims intake Settlement time Assessor travel Evidence completeness Leakage rate Capture & Feedback AI & Location Workmate GIS & Analytics Routes & Navigation Record consented incident location Claims system Media upload partially succeeds Capture guided photo evidence Consented capture and vision boundary Vision result is uncertain or sensitive Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:insurance-claims-composed-experience","kind":"Recipe","title":"Application flow: Evidence-led claims from incident to settlement","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/insurance-claims-composed-experience","eyebrow":"Insurance · hybrid · 90–120 min","keywords":"Faster, more consistent claims decisions with tamper-aware spatial evidence. Policyholder Claims intake Assessor Fraud analyst Settlement time Assessor travel Evidence completeness Leakage rate Capture & Feedback AI & Location Workmate GIS & Analytics Routes & Navigation Record consented incident location Claims system Media upload partially succeeds Capture guided photo evidence Consented capture and vision boundary Vision result is uncertain or sensitive Run model-locked vision triage with human review bands Spatial enrichment Location metadata conflicts with declaration Dispatch an assessor when needed Assessment operations Catastrophe data is revised Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:insurance-claims-durable-operation","kind":"Recipe","title":"Operating journey: Evidence-led claims from incident to settlement","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/insurance-claims-durable-operation","eyebrow":"Insurance · stateful · 2–3 hr","keywords":"Faster, more consistent claims decisions with tamper-aware spatial evidence. Policyholder Claims intake Assessor Fraud analyst Catastrophe manager Settlement time Assessor travel Evidence completeness Leakage rate Capture & Feedback AI & Location Workmate GIS & Analytics Routes & Navigation Record consented incident location Claims system Media upload partially succeeds Capture guided photo evidence Consented capture and vision boundary Vision result is uncertain or sensitive Run model-locked vision triage with human review bands Spatial enrichment Location metadata conflicts with declaration Dispatch an assessor when needed Assessment operations Catastrophe data is revised Overlay hazard and policy context Decision evidence Media upload partially succeeds Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:hospital-care-logistics-request-response","kind":"Recipe","title":"Contract slice: Coordinate time-critical care without losing custody","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/hospital-care-logistics-request-response","eyebrow":"Healthcare · stateless · 35–50 min","keywords":"Shorter transfer and specimen journeys with fewer missed hand-offs and a complete chain of operational custody. Transfer coordinator Ambulance dispatcher Door-to-door transfer time On-time specimen delivery Custody exceptions Privacy incidents Search & Places Routes & Navigation InTouch Telematics Capture & Feedback GIS & Analytics Resolve the correct facility, campus, and entrance Clinical and laboratory systems Search selects the public entrance instead of emergency receiving Select an eligible vehicle and bounded route Facility and entrance resolution Location or condition evidence becomes stale Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:hospital-care-logistics-composed-experience","kind":"Recipe","title":"Application flow: Coordinate time-critical care without losing custody","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/hospital-care-logistics-composed-experience","eyebrow":"Healthcare · hybrid · 90–120 min","keywords":"Shorter transfer and specimen journeys with fewer missed hand-offs and a complete chain of operational custody. Transfer coordinator Ambulance dispatcher Driver or courier Receiving clinician Door-to-door transfer time On-time specimen delivery Custody exceptions Privacy incidents Search & Places Routes & Navigation InTouch Telematics Capture & Feedback GIS & Analytics Resolve the correct facility, campus, and entrance Clinical and laboratory systems Search selects the public entrance instead of emergency receiving Select an eligible vehicle and bounded route Facility and entrance resolution Location or condition evidence becomes stale Track custody and freshness through every hand-off Eligibility and dispatch The receiver cannot match the custody identity Escalate delay or temperature exceptions Privacy-minimized journey Search selects the public entrance instead of emergency receiving Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:hospital-care-logistics-durable-operation","kind":"Recipe","title":"Operating journey: Coordinate time-critical care without losing custody","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/hospital-care-logistics-durable-operation","eyebrow":"Healthcare · stateful · 2–3 hr","keywords":"Shorter transfer and specimen journeys with fewer missed hand-offs and a complete chain of operational custody. Transfer coordinator Ambulance dispatcher Driver or courier Receiving clinician Privacy and quality reviewer Door-to-door transfer time On-time specimen delivery Custody exceptions Privacy incidents Search & Places Routes & Navigation InTouch Telematics Capture & Feedback GIS & Analytics Resolve the correct facility, campus, and entrance Clinical and laboratory systems Search selects the public entrance instead of emergency receiving Select an eligible vehicle and bounded route Facility and entrance resolution Location or condition evidence becomes stale Track custody and freshness through every hand-off Eligibility and dispatch The receiver cannot match the custody identity Escalate delay or temperature exceptions Privacy-minimized journey Search selects the public entrance instead of emergency receiving Reconcile arrival, acceptance, and retained evidence Acceptance and quality review Location or condition evidence becomes stale Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:emergency-response-request-response","kind":"Recipe","title":"Contract slice: Route coordinated response under pressure","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/emergency-response-request-response","eyebrow":"Public safety · stateless · 35–50 min","keywords":"Reduced time to scene and safer decisions across dispatch, responders, and command. Caller Emergency call taker Call-to-dispatch time Arrival time Unit utilization Coverage gaps Search & Places Routes & Navigation InTouch Telematics GIS & Analytics Resolve location from address, pin, or device CAD incident record Caller description produces multiple locations Find eligible nearby responders Location resolution Unit position is stale Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:emergency-response-composed-experience","kind":"Recipe","title":"Application flow: Route coordinated response under pressure","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/emergency-response-composed-experience","eyebrow":"Public safety · hybrid · 90–120 min","keywords":"Reduced time to scene and safer decisions across dispatch, responders, and command. Caller Emergency call taker Dispatcher Responder Call-to-dispatch time Arrival time Unit utilization Coverage gaps Search & Places Routes & Navigation InTouch Telematics GIS & Analytics Resolve location from address, pin, or device CAD incident record Caller description produces multiple locations Find eligible nearby responders Location resolution Unit position is stale Route with vehicle constraints Resource and route service Hazard changes after dispatch Track units and changing hazards Live coordination Caller description produces multiple locations Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:emergency-response-durable-operation","kind":"Recipe","title":"Operating journey: Route coordinated response under pressure","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/emergency-response-durable-operation","eyebrow":"Public safety · stateful · 2–3 hr","keywords":"Reduced time to scene and safer decisions across dispatch, responders, and command. Caller Emergency call taker Dispatcher Responder Incident commander Call-to-dispatch time Arrival time Unit utilization Coverage gaps Search & Places Routes & Navigation InTouch Telematics GIS & Analytics Resolve location from address, pin, or device CAD incident record Caller description produces multiple locations Find eligible nearby responders Location resolution Unit position is stale Route with vehicle constraints Resource and route service Hazard changes after dispatch Track units and changing hazards Live coordination Caller description produces multiple locations Replay the incident for review Command and review Unit position is stale Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Care Transfer Desk"},{"id":"recipe:smart-city-operations-request-response","kind":"Recipe","title":"Contract slice: A living operations map for the city","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/smart-city-operations-request-response","eyebrow":"Government · stateless · 35–50 min","keywords":"One governed view from daily operations to infrastructure investment planning. Citizen Control-room operator Resolution time Asset downtime Repeat incidents Ward-level service equity GIS & Analytics Workmate InTouch Telematics Maps Catalog authoritative layers Department systems of record Two departments claim the same incident Ingest live assets and citizen reports Spatial data catalogue Citizen report contains precise personal data Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:smart-city-operations-composed-experience","kind":"Recipe","title":"Application flow: A living operations map for the city","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/smart-city-operations-composed-experience","eyebrow":"Government · hybrid · 90–120 min","keywords":"One governed view from daily operations to infrastructure investment planning. Citizen Control-room operator Department dispatcher Field crew Resolution time Asset downtime Repeat incidents Ward-level service equity GIS & Analytics Workmate InTouch Telematics Maps Catalog authoritative layers Department systems of record Two departments claim the same incident Ingest live assets and citizen reports Spatial data catalogue Citizen report contains precise personal data Dispatch and monitor work Event correlation Public status lags internal resolution Publish role-specific dashboards Work orchestration Two departments claim the same incident Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:smart-city-operations-durable-operation","kind":"Recipe","title":"Operating journey: A living operations map for the city","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/smart-city-operations-durable-operation","eyebrow":"Government · stateful · 2–3 hr","keywords":"One governed view from daily operations to infrastructure investment planning. Citizen Control-room operator Department dispatcher Field crew City data steward Resolution time Asset downtime Repeat incidents Ward-level service equity GIS & Analytics Workmate InTouch Telematics Maps Catalog authoritative layers Department systems of record Two departments claim the same incident Ingest live assets and citizen reports Spatial data catalogue Citizen report contains precise personal data Dispatch and monitor work Event correlation Public status lags internal resolution Publish role-specific dashboards Work orchestration Two departments claim the same incident Analyze hotspots and service equity Role and public projections Citizen report contains precise personal data Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:connected-vehicle-request-response","kind":"Recipe","title":"Contract slice: Navigation built for intermittent connectivity","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/connected-vehicle-request-response","eyebrow":"Automotive · stateless · 35–50 min","keywords":"Reliable guidance across coverage gaps without giving up traffic, search freshness, or safety. Driver Vehicle head unit Route success offline Guidance crash-free rate Update adoption Search success Offline & Automotive Routes & Navigation Search & Places InTouch Telematics Activate the head unit Vehicle/OEM identity Power loss during update Install compatible signed regional data Dual-slot offline runtime Online traffic disappears mid-route Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby A2A Solution Studio"},{"id":"recipe:connected-vehicle-composed-experience","kind":"Recipe","title":"Application flow: Navigation built for intermittent connectivity","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/connected-vehicle-composed-experience","eyebrow":"Automotive · hybrid · 90–120 min","keywords":"Reliable guidance across coverage gaps without giving up traffic, search freshness, or safety. Driver Vehicle head unit OEM cloud Map-data operator Route success offline Guidance crash-free rate Update adoption Search success Offline & Automotive Routes & Navigation Search & Places InTouch Telematics Activate the head unit Vehicle/OEM identity Power loss during update Install compatible signed regional data Dual-slot offline runtime Online traffic disappears mid-route Plan and guide offline Local navigation New package boots but fails route smoke test Blend online traffic and search when available Online enhancement Power loss during update Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby A2A Solution Studio"},{"id":"recipe:connected-vehicle-durable-operation","kind":"Recipe","title":"Operating journey: Navigation built for intermittent connectivity","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/connected-vehicle-durable-operation","eyebrow":"Automotive · stateful · 2–3 hr","keywords":"Reliable guidance across coverage gaps without giving up traffic, search freshness, or safety. Driver Vehicle head unit OEM cloud Map-data operator Dealer/support engineer Route success offline Guidance crash-free rate Update adoption Search success Offline & Automotive Routes & Navigation Search & Places InTouch Telematics Activate the head unit Vehicle/OEM identity Power loss during update Install compatible signed regional data Dual-slot offline runtime Online traffic disappears mid-route Plan and guide offline Local navigation New package boots but fails route smoke test Blend online traffic and search when available Online enhancement Power loss during update Stage atomic map and runtime updates Fleet operations Online traffic disappears mid-route Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby A2A Solution Studio"},{"id":"recipe:aviation-ground-operations-request-response","kind":"Recipe","title":"Contract slice: Run a safe, punctual airport turnaround","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/aviation-ground-operations-request-response","eyebrow":"Aviation · stateless · 35–50 min","keywords":"More predictable departures with safer vehicle movement and attributable hand-offs across airport and airline teams. Turnaround coordinator Airport operations controller On-time departure Turnaround milestone variance Airside safety exceptions Ground-equipment utilization GIS & Analytics InTouch Telematics Workmate Maps Capture & Feedback Publish the approved airside network and restricted zones Airport operational authority Stand changes after teams accept tasks Create one versioned turnaround plan Versioned spatial operating picture A vehicle appears outside its approved corridor Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:aviation-ground-operations-composed-experience","kind":"Recipe","title":"Application flow: Run a safe, punctual airport turnaround","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/aviation-ground-operations-composed-experience","eyebrow":"Aviation · hybrid · 90–120 min","keywords":"More predictable departures with safer vehicle movement and attributable hand-offs across airport and airline teams. Turnaround coordinator Airport operations controller Ground-service team Airline station manager On-time departure Turnaround milestone variance Airside safety exceptions Ground-equipment utilization GIS & Analytics InTouch Telematics Workmate Maps Capture & Feedback Publish the approved airside network and restricted zones Airport operational authority Stand changes after teams accept tasks Create one versioned turnaround plan Versioned spatial operating picture A vehicle appears outside its approved corridor Track eligible vehicles and milestone hand-offs Turnaround aggregate One supplier reports complete while another dependency is open Capture inspection and exception evidence Ground-team execution Stand changes after teams accept tasks Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:aviation-ground-operations-durable-operation","kind":"Recipe","title":"Operating journey: Run a safe, punctual airport turnaround","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/aviation-ground-operations-durable-operation","eyebrow":"Aviation · stateful · 2–3 hr","keywords":"More predictable departures with safer vehicle movement and attributable hand-offs across airport and airline teams. Turnaround coordinator Airport operations controller Ground-service team Airline station manager Safety investigator On-time departure Turnaround milestone variance Airside safety exceptions Ground-equipment utilization GIS & Analytics InTouch Telematics Workmate Maps Capture & Feedback Publish the approved airside network and restricted zones Airport operational authority Stand changes after teams accept tasks Create one versioned turnaround plan Versioned spatial operating picture A vehicle appears outside its approved corridor Track eligible vehicles and milestone hand-offs Turnaround aggregate One supplier reports complete while another dependency is open Capture inspection and exception evidence Ground-team execution Stand changes after teams accept tasks Reconcile departure readiness across authorities Readiness reconciliation A vehicle appears outside its approved corridor Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:travel-discovery-request-response","kind":"Recipe","title":"Contract slice: Turn inspiration into an itinerary","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/travel-discovery-request-response","eyebrow":"Travel · stateless · 35–50 min","keywords":"More confident trip planning and higher conversion from discovery to booking. Traveler Travel-content editor Save-to-book rate Itinerary completion Search refinement Navigation hand-offs Search & Places Maps App Widgets & Deep Links Routes & Navigation Discover places by theme and proximity Travel content and inventory Two sources describe the same attraction Build a time-aware itinerary Place discovery Opening or availability data is stale Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Store Locator"},{"id":"recipe:travel-discovery-composed-experience","kind":"Recipe","title":"Application flow: Turn inspiration into an itinerary","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/travel-discovery-composed-experience","eyebrow":"Travel · hybrid · 90–120 min","keywords":"More confident trip planning and higher conversion from discovery to booking. Traveler Travel-content editor Booking partner Product merchandiser Save-to-book rate Itinerary completion Search refinement Navigation hand-offs Search & Places Maps App Widgets & Deep Links Routes & Navigation Discover places by theme and proximity Travel content and inventory Two sources describe the same attraction Build a time-aware itinerary Place discovery Opening or availability data is stale Visualize routes and neighborhoods Itinerary aggregate Navigation app is absent Embed 3D or RealView context Map and rich context Two sources describe the same attraction Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Store Locator"},{"id":"recipe:travel-discovery-durable-operation","kind":"Recipe","title":"Operating journey: Turn inspiration into an itinerary","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/travel-discovery-durable-operation","eyebrow":"Travel · stateful · 2–3 hr","keywords":"More confident trip planning and higher conversion from discovery to booking. Traveler Travel-content editor Booking partner Product merchandiser Customer support Save-to-book rate Itinerary completion Search refinement Navigation hand-offs Search & Places Maps App Widgets & Deep Links Routes & Navigation Discover places by theme and proximity Travel content and inventory Two sources describe the same attraction Build a time-aware itinerary Place discovery Opening or availability data is stale Visualize routes and neighborhoods Itinerary aggregate Navigation app is absent Embed 3D or RealView context Map and rich context Two sources describe the same attraction Hand off to navigation Partner hand-off Opening or availability data is stale Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Store Locator"},{"id":"recipe:agriculture-field-ops-request-response","kind":"Recipe","title":"Contract slice: Coordinate field operations across every plot","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/agriculture-field-ops-request-response","eyebrow":"Agriculture · stateless · 35–50 min","keywords":"Less travel and better traceability for inspection, inputs, harvest, and compliance. Farm manager Agronomist Area serviced per day Input variance Equipment utilization Issue recurrence GIS & Analytics Workmate InTouch Telematics Capture & Feedback Publish parcel boundaries Farm/parcel registry Observation falls near a parcel boundary Create seasonal field tasks Seasonal planning Offline task was reassigned Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:agriculture-field-ops-composed-experience","kind":"Recipe","title":"Application flow: Coordinate field operations across every plot","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/agriculture-field-ops-composed-experience","eyebrow":"Agriculture · hybrid · 90–120 min","keywords":"Less travel and better traceability for inspection, inputs, harvest, and compliance. Farm manager Agronomist Field worker Equipment operator Area serviced per day Input variance Equipment utilization Issue recurrence GIS & Analytics Workmate InTouch Telematics Capture & Feedback Publish parcel boundaries Farm/parcel registry Observation falls near a parcel boundary Create seasonal field tasks Seasonal planning Offline task was reassigned Optimize crews and equipment Offline field execution Equipment telemetry is shared across farms Capture geotagged observations Equipment telemetry Observation falls near a parcel boundary Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:agriculture-field-ops-durable-operation","kind":"Recipe","title":"Operating journey: Coordinate field operations across every plot","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/agriculture-field-ops-durable-operation","eyebrow":"Agriculture · stateful · 2–3 hr","keywords":"Less travel and better traceability for inspection, inputs, harvest, and compliance. Farm manager Agronomist Field worker Equipment operator Compliance auditor Area serviced per day Input variance Equipment utilization Issue recurrence GIS & Analytics Workmate InTouch Telematics Capture & Feedback Publish parcel boundaries Farm/parcel registry Observation falls near a parcel boundary Create seasonal field tasks Seasonal planning Offline task was reassigned Optimize crews and equipment Offline field execution Equipment telemetry is shared across farms Capture geotagged observations Equipment telemetry Observation falls near a parcel boundary Analyze yield and issue patterns Spatial agronomy analysis Offline task was reassigned Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:mining-haulage-safety-request-response","kind":"Recipe","title":"Contract slice: Move material safely across a changing mine","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/mining-haulage-safety-request-response","eyebrow":"Mining · stateless · 35–50 min","keywords":"Higher productive haulage with fewer route conflicts, stale-map movements, and unexplained cycle losses. Mine dispatcher Pit supervisor Tonnes per operating hour Cycle-time variance Geofence exceptions Unplanned equipment idle time GIS & Analytics InTouch Telematics Workmate Offline & Automotive Capture & Feedback Publish the approved pit, road, and exclusion-zone version Mine plan and safety authority A truck wakes with the previous pit map Assign compatible equipment and operators Versioned offline map release Telemetry silence looks like an idle vehicle Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:mining-haulage-safety-composed-experience","kind":"Recipe","title":"Application flow: Move material safely across a changing mine","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/mining-haulage-safety-composed-experience","eyebrow":"Mining · hybrid · 90–120 min","keywords":"Higher productive haulage with fewer route conflicts, stale-map movements, and unexplained cycle losses. Mine dispatcher Pit supervisor Haul-truck operator Geotechnical engineer Tonnes per operating hour Cycle-time variance Geofence exceptions Unplanned equipment idle time GIS & Analytics InTouch Telematics Workmate Offline & Automotive Capture & Feedback Publish the approved pit, road, and exclusion-zone version Mine plan and safety authority A truck wakes with the previous pit map Assign compatible equipment and operators Versioned offline map release Telemetry silence looks like an idle vehicle Guide and observe offline-capable haul cycles Dispatch aggregate Duplicate dump evidence inflates tonnes Stop and review safety or geofence exceptions Haul-cycle evidence A truck wakes with the previous pit map Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:mining-haulage-safety-durable-operation","kind":"Recipe","title":"Operating journey: Move material safely across a changing mine","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/mining-haulage-safety-durable-operation","eyebrow":"Mining · stateful · 2–3 hr","keywords":"Higher productive haulage with fewer route conflicts, stale-map movements, and unexplained cycle losses. Mine dispatcher Pit supervisor Haul-truck operator Geotechnical engineer Safety and production reviewer Tonnes per operating hour Cycle-time variance Geofence exceptions Unplanned equipment idle time GIS & Analytics InTouch Telematics Workmate Offline & Automotive Capture & Feedback Publish the approved pit, road, and exclusion-zone version Mine plan and safety authority A truck wakes with the previous pit map Assign compatible equipment and operators Versioned offline map release Telemetry silence looks like an idle vehicle Guide and observe offline-capable haul cycles Dispatch aggregate Duplicate dump evidence inflates tonnes Stop and review safety or geofence exceptions Haul-cycle evidence A truck wakes with the previous pit map Reconcile tonnes, cycles, maintenance, and shift closure Safety and production reconciliation Telemetry silence looks like an idle vehicle Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Airside Turnaround Desk"},{"id":"recipe:telecom-network-care-request-response","kind":"Recipe","title":"Contract slice: Operate the network from tower to doorstep","description":"Prove one bounded contract, identity handoff, failure response, and observable first success.","href":"/recipes/telecom-network-care-request-response","eyebrow":"Telecommunications · stateless · 35–50 min","keywords":"Faster restoration with better prioritization and fewer repeat dispatches. Network operations engineer Alarm correlator Mean time to repair Customers restored per action Truck rolls Repeat alarm rate GIS & Analytics Workmate Routes & Navigation Capture & Feedback Model towers, links, cabinets, and service areas Network inventory/topology Many alarms represent one fibre cut Correlate alarms with impacted customers Alarm and impact correlation Inventory geometry/topology is stale Bound inputs and outputs Abortable timeout Retry only safe reads Typed empty and denied states Safe request correlation Credential and URL-log redaction cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:telecom-network-care-composed-experience","kind":"Recipe","title":"Application flow: Operate the network from tower to doorstep","description":"Compose multiple capabilities while the application owns user intent, policy, and continuity.","href":"/recipes/telecom-network-care-composed-experience","eyebrow":"Telecommunications · hybrid · 90–120 min","keywords":"Faster restoration with better prioritization and fewer repeat dispatches. Network operations engineer Alarm correlator Field dispatcher Technician Mean time to repair Customers restored per action Truck rolls Repeat alarm rate GIS & Analytics Workmate Routes & Navigation Capture & Feedback Model towers, links, cabinets, and service areas Network inventory/topology Many alarms represent one fibre cut Correlate alarms with impacted customers Alarm and impact correlation Inventory geometry/topology is stale Create skill-aware repair tasks Repair orchestration Technician closes before alarms clear Navigate and capture repair proof Field evidence Many alarms represent one fibre cut Application-owned intent Stable cross-capability identity Partial-failure fallback Cancellation and teardown Freshness and provenance Quota and latency budget cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"recipe:telecom-network-care-durable-operation","kind":"Recipe","title":"Operating journey: Operate the network from tower to doorstep","description":"Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.","href":"/recipes/telecom-network-care-durable-operation","eyebrow":"Telecommunications · stateful · 2–3 hr","keywords":"Faster restoration with better prioritization and fewer repeat dispatches. Network operations engineer Alarm correlator Field dispatcher Technician Customer-impact manager Mean time to repair Customers restored per action Truck rolls Repeat alarm rate GIS & Analytics Workmate Routes & Navigation Capture & Feedback Model towers, links, cabinets, and service areas Network inventory/topology Many alarms represent one fibre cut Correlate alarms with impacted customers Alarm and impact correlation Inventory geometry/topology is stale Create skill-aware repair tasks Repair orchestration Technician closes before alarms clear Navigate and capture repair proof Field evidence Many alarms represent one fibre cut Analyze chronic failure clusters Restoration reconciliation Inventory geometry/topology is stale Idempotent commands Optimistic aggregate versions Event and receipt time Transactional outbox Unknown-outcome reconciliation Independent human decisions Restart recovery Immutable audit evidence cURL JavaScript Python Java C# Go PHP Ruby Grid Restoration Desk"},{"id":"solution:last-mile-delivery","kind":"Solution","title":"A delivery promise customers can trust","description":"Validate addresses, allocate stops, guide drivers, stream progress, and prove completion.","href":"/use-cases/last-mile-delivery","eyebrow":"Logistics","keywords":"Fewer failed deliveries and a live, explainable ETA from checkout to doorstep. search-places routes-navigation intouch-telematics capture-feedback Checkout customer Dispatch planner Driver Customer-support agent Transport partner Normalize the destination and retain its Mappls Pin Optimize stops against capacity and time windows Navigate with live rerouting Stream driver and order state Capture geotagged proof and reconcile exceptions First-attempt delivery rate Cost per stop ETA error Distance per order"},{"id":"solution:ride-hailing","kind":"Solution","title":"A pickup flow that survives the real world","description":"Find entrances, match riders and drivers, route continuously, and resolve pickup ambiguity.","href":"/use-cases/ride-hailing","eyebrow":"Mobility","keywords":"Shorter pickup times with fewer calls, cancellations, and unsafe rendezvous points. maps search-places routes-navigation intouch-telematics Rider Driver Marketplace dispatcher Safety operator Customer support Bias search to the rider viewport Confirm a precise pickup pin and landmark Match with network-aware ETA Track approach and reroute Detect arrival and close the trip Pickup ETA Cancellation rate Driver idle distance Pickup support contacts"},{"id":"solution:field-service","kind":"Solution","title":"Dispatch the right technician, with the right proof","description":"Turn outages or service requests into skill-aware, route-efficient field jobs.","href":"/use-cases/field-service","eyebrow":"Utilities","keywords":"Higher first-time-fix rates and auditable work from dispatch through customer sign-off. workmate routes-navigation capture-feedback gis-analytics Service requester Dispatcher Technician Proof reviewer Operations manager Geocode and classify the service location Assign by skills, shift, inventory, and ETA Guide the technician Collect checklist, image, and signature proof Analyze repeat faults spatially First-time-fix rate Jobs per shift SLA compliance Repeat visit rate"},{"id":"solution:energy-grid-resilience","kind":"Solution","title":"Restore the grid from alarm to verified service","description":"Correlate network alarms, weather exposure, switching plans, field crews, and restoration evidence.","href":"/use-cases/energy-grid-resilience","eyebrow":"Energy","keywords":"Faster, safer restoration with an explainable view of affected assets, customers, crews, and residual risk. gis-analytics intouch-telematics workmate routes-navigation capture-feedback Grid control operator Outage coordinator Switching authority Field crew Customer-impact lead Version the network and hazard context Correlate alarms into bounded outage incidents Approve a switching and crew plan Guide crews and capture field evidence Reconcile telemetry, customer impact, and restoration Customers restored per hour SAIDI contribution Crew travel time Repeat outage rate"},{"id":"solution:retail-expansion","kind":"Solution","title":"Choose the next store with evidence","description":"Combine catchments, demographics, competition, access, and existing performance.","href":"/use-cases/retail-expansion","eyebrow":"Retail","keywords":"Faster site screening and investment decisions grounded in a reusable spatial model. gis-analytics search-places maps Expansion analyst GIS data steward Real-estate manager Finance reviewer Executive approver Publish candidate sites and performance data Generate drive-time catchments Join demand and competition signals Score and compare candidates Share an executive decision map Forecast accuracy Cannibalization risk Time to shortlist Revenue per catchment"},{"id":"solution:banking-address-risk","kind":"Solution","title":"Make address risk explainable","description":"Standardize applications, verify presence, enrich geography, and route cases for review.","href":"/use-cases/banking-address-risk","eyebrow":"Financial services","keywords":"More straight-through approvals with a clear audit trail for ambiguous or high-risk addresses. search-places capture-feedback gis-analytics Applicant Onboarding service Risk analyst Manual reviewer Compliance auditor Normalize the entered address Compare declared and captured locations Join serviceability and risk zones Score confidence with reasons Escalate only unresolved cases Straight-through processing False-positive review rate Verification turnaround Fraud loss"},{"id":"solution:insurance-claims","kind":"Solution","title":"Evidence-led claims from incident to settlement","description":"Capture location and imagery, use governed vision triage, dispatch assessors, and understand catastrophe exposure.","href":"/use-cases/insurance-claims","eyebrow":"Insurance","keywords":"Faster, more consistent claims decisions with tamper-aware spatial evidence. capture-feedback ai-location workmate gis-analytics routes-navigation Policyholder Claims intake Assessor Fraud analyst Catastrophe manager Record consented incident location Capture guided photo evidence Run model-locked vision triage with human review bands Dispatch an assessor when needed Overlay hazard and policy context Preserve decision lineage and redaction Settlement time Assessor travel Evidence completeness Leakage rate"},{"id":"solution:hospital-care-logistics","kind":"Solution","title":"Coordinate time-critical care without losing custody","description":"Resolve facilities and entrances, dispatch suitable transport, track hand-offs, and preserve privacy-minimized care logistics evidence.","href":"/use-cases/hospital-care-logistics","eyebrow":"Healthcare","keywords":"Shorter transfer and specimen journeys with fewer missed hand-offs and a complete chain of operational custody. search-places routes-navigation intouch-telematics capture-feedback gis-analytics Transfer coordinator Ambulance dispatcher Driver or courier Receiving clinician Privacy and quality reviewer Resolve the correct facility, campus, and entrance Select an eligible vehicle and bounded route Track custody and freshness through every hand-off Escalate delay or temperature exceptions Reconcile arrival, acceptance, and retained evidence Door-to-door transfer time On-time specimen delivery Custody exceptions Privacy incidents"},{"id":"solution:emergency-response","kind":"Solution","title":"Route coordinated response under pressure","description":"Resolve caller location, find capable resources, route around incidents, and maintain a common picture.","href":"/use-cases/emergency-response","eyebrow":"Public safety","keywords":"Reduced time to scene and safer decisions across dispatch, responders, and command. search-places routes-navigation intouch-telematics gis-analytics Caller Emergency call taker Dispatcher Responder Incident commander Resolve location from address, pin, or device Find eligible nearby responders Route with vehicle constraints Track units and changing hazards Replay the incident for review Call-to-dispatch time Arrival time Unit utilization Coverage gaps"},{"id":"solution:smart-city-operations","kind":"Solution","title":"A living operations map for the city","description":"Unify assets, incidents, crews, citizen feedback, and long-term spatial analysis.","href":"/use-cases/smart-city-operations","eyebrow":"Government","keywords":"One governed view from daily operations to infrastructure investment planning. gis-analytics workmate intouch-telematics maps Citizen Control-room operator Department dispatcher Field crew City data steward Catalog authoritative layers Ingest live assets and citizen reports Dispatch and monitor work Publish role-specific dashboards Analyze hotspots and service equity Resolution time Asset downtime Repeat incidents Ward-level service equity"},{"id":"solution:connected-vehicle","kind":"Solution","title":"Navigation built for intermittent connectivity","description":"Ship an activated, updateable in-vehicle navigation lifecycle with online enhancement.","href":"/use-cases/connected-vehicle","eyebrow":"Automotive","keywords":"Reliable guidance across coverage gaps without giving up traffic, search freshness, or safety. offline-automotive routes-navigation search-places intouch-telematics Driver Vehicle head unit OEM cloud Map-data operator Dealer/support engineer Activate the head unit Install compatible signed regional data Plan and guide offline Blend online traffic and search when available Stage atomic map and runtime updates Route success offline Guidance crash-free rate Update adoption Search success"},{"id":"solution:aviation-ground-operations","kind":"Solution","title":"Run a safe, punctual airport turnaround","description":"Coordinate stands, service vehicles, restricted zones, inspections, and turnaround milestones on one governed operating picture.","href":"/use-cases/aviation-ground-operations","eyebrow":"Aviation","keywords":"More predictable departures with safer vehicle movement and attributable hand-offs across airport and airline teams. gis-analytics intouch-telematics workmate maps capture-feedback Turnaround coordinator Airport operations controller Ground-service team Airline station manager Safety investigator Publish the approved airside network and restricted zones Create one versioned turnaround plan Track eligible vehicles and milestone hand-offs Capture inspection and exception evidence Reconcile departure readiness across authorities On-time departure Turnaround milestone variance Airside safety exceptions Ground-equipment utilization"},{"id":"solution:travel-discovery","kind":"Solution","title":"Turn inspiration into an itinerary","description":"Help travelers discover, sequence, visualize, and open rich place experiences.","href":"/use-cases/travel-discovery","eyebrow":"Travel","keywords":"More confident trip planning and higher conversion from discovery to booking. search-places maps app-widgets-deep-links routes-navigation Traveler Travel-content editor Booking partner Product merchandiser Customer support Discover places by theme and proximity Build a time-aware itinerary Visualize routes and neighborhoods Embed 3D or RealView context Hand off to navigation Save-to-book rate Itinerary completion Search refinement Navigation hand-offs"},{"id":"solution:agriculture-field-ops","kind":"Solution","title":"Coordinate field operations across every plot","description":"Map parcels, schedule crews, track equipment, and compare observations over time.","href":"/use-cases/agriculture-field-ops","eyebrow":"Agriculture","keywords":"Less travel and better traceability for inspection, inputs, harvest, and compliance. gis-analytics workmate intouch-telematics capture-feedback Farm manager Agronomist Field worker Equipment operator Compliance auditor Publish parcel boundaries Create seasonal field tasks Optimize crews and equipment Capture geotagged observations Analyze yield and issue patterns Area serviced per day Input variance Equipment utilization Issue recurrence"},{"id":"solution:mining-haulage-safety","kind":"Solution","title":"Move material safely across a changing mine","description":"Version haul roads and exclusion zones, dispatch compatible equipment, track cycles, and reconcile safety and production evidence.","href":"/use-cases/mining-haulage-safety","eyebrow":"Mining","keywords":"Higher productive haulage with fewer route conflicts, stale-map movements, and unexplained cycle losses. gis-analytics intouch-telematics workmate offline-automotive capture-feedback Mine dispatcher Pit supervisor Haul-truck operator Geotechnical engineer Safety and production reviewer Publish the approved pit, road, and exclusion-zone version Assign compatible equipment and operators Guide and observe offline-capable haul cycles Stop and review safety or geofence exceptions Reconcile tonnes, cycles, maintenance, and shift closure Tonnes per operating hour Cycle-time variance Geofence exceptions Unplanned equipment idle time"},{"id":"solution:telecom-network-care","kind":"Solution","title":"Operate the network from tower to doorstep","description":"Link network assets, alarms, field teams, and customer impact spatially.","href":"/use-cases/telecom-network-care","eyebrow":"Telecommunications","keywords":"Faster restoration with better prioritization and fewer repeat dispatches. gis-analytics workmate routes-navigation capture-feedback Network operations engineer Alarm correlator Field dispatcher Technician Customer-impact manager Model towers, links, cabinets, and service areas Correlate alarms with impacted customers Create skill-aware repair tasks Navigate and capture repair proof Analyze chronic failure clusters Mean time to repair Customers restored per action Truck rolls Repeat alarm rate"},{"id":"journey:field-service-task","kind":"Journey","title":"Field-service task lifecycle","description":"Create, assign, accept, travel, prove, approve, and close a field job without losing actor, retry, or evidence history.","href":"/journeys/field-service-task","eyebrow":"stateful · task","keywords":"workmate Dispatcher Field worker Supervisor Integration service unassigned Unassigned assigned Assigned accepted Accepted en_route En route in_progress In progress proof_pending Proof pending completed Completed cancelled Cancelled create_task task.created assign task.assigned accept task.accepted start_travel task.en_route arrive task.started submit_proof task.proof_submitted approve_proof task.completed reject_proof task.proof_rejected One upstream external job maps to one durable task aggregate. Only the assigned worker can accept, travel, arrive, or submit proof unless an attributable override is recorded. Every command carries tenant, actor, idempotency key, expected version, and occurrence time. Completion is impossible until the declared proof policy passes. Task history is append-only; corrections use new events or compensating work."},{"id":"journey:connected-fleet-trip","kind":"Journey","title":"Connected fleet trip","description":"Provision an observable trip, follow live vehicle state, explain exceptions, close deliberately, and retain a replayable operational record.","href":"/journeys/connected-fleet-trip","eyebrow":"stateful · trip","keywords":"intouch-telematics Fleet planner Driver Operations controller Telematics service planned Planned ready Ready active Active exception Exception closing Closing closed Closed create_trip trip.created confirm_device_ready trip.ready start_trip trip.started raise_exception trip.exception_raised resolve_exception trip.exception_resolved request_close trip.close_requested close_trip trip.closed A device is assigned to at most one active trip in the same operational context. Raw telemetry is immutable and distinguished by event time and receipt time. Derived live state can be rebuilt from ordered observations and commands. Trip closure never discards unresolved exceptions or data gaps. Every provider identifier is mapped to the internal trip and tenant."},{"id":"journey:fleet-geofence-exception","kind":"Journey","title":"Fleet geofence exception","description":"Create a governed zone, evaluate vehicle activity, suppress noise, raise an actionable case, and retire the rule safely.","href":"/journeys/fleet-geofence-exception","eyebrow":"stateful · geofence case","keywords":"intouch-telematics Fleet administrator Telematics service Operations controller Compliance reviewer draft Draft active Active breached Breached acknowledged Acknowledged resolved Resolved retired Retired publish_geofence geofence.published record_breach geofence.breached acknowledge_case geofence_case.acknowledged resolve_case geofence_case.resolved retire_geofence geofence.retired Geometry and coordinate reference are validated before publication. Every activity names the geofence definition version that evaluated it. Noise suppression never deletes raw source observations. One provider activity creates at most one operational case per rule version. Retirement stops new evaluation while preserving case and audit history."},{"id":"journey:emergency-incident-response","kind":"Journey","title":"Coordinated incident response","description":"Resolve an incident location, select a capable available responder, route and observe the unit, adapt to hazards, establish arrival, resolve with evidence, and review every decision.","href":"/journeys/emergency-incident-response","eyebrow":"stateful · incident","keywords":"routes-navigation Call taker Dispatcher Responder Incident commander Telematics service reported Reported located Located dispatched Dispatched en_route En route on_scene On scene resolved Resolved reviewed Reviewed report_incident incident.reported resolve_location incident.located dispatch incident.dispatched accept_dispatch dispatch.accepted record_position unit.position_recorded confirm_arrival incident.arrived resolve incident.resolved review incident.reviewed One external report maps to one incident aggregate. Only available units with the required capability are eligible for ranking. A unit is assigned to at most one active incident in the same operational context. Only the assigned unit can accept dispatch and publish operational telemetry. Raw telemetry preserves event and receipt time; late evidence never regresses latest state. Arrival requires explicit distance, speed, and dwell evidence. Resolution cannot occur without external evidence references."},{"id":"journey:navigation-session","kind":"Journey","title":"Recoverable navigation session","description":"Move from route intent through preview, guidance, reroute, arrival, and cleanup while surviving process, sensor, and network interruption.","href":"/journeys/navigation-session","eyebrow":"hybrid · navigation session","keywords":"routes-navigation Driver Navigation application Mappls navigation SDK Operations backend draft Draft preview Preview navigating Navigating rerouting Rerouting arrived Arrived ended Ended calculate_route route.calculated start_guidance navigation.started request_reroute reroute.requested accept_reroute route.updated confirm_arrival navigation.arrived end_session navigation.ended Only one guidance session owns foreground navigation resources at a time. Every route result is applied only to the intent version that requested it. The last valid route remains available while a reroute is pending. Arrival requires an explicit distance, speed, dwell, and stop policy. End releases every observer, sensor, audio, and service resource exactly once in effect."},{"id":"journey:governed-spatial-analysis","kind":"Journey","title":"Governed spatial analysis","description":"Ingest versioned data, validate and publish it, execute reproducible analysis, review lineage, and share a governed decision layer.","href":"/journeys/governed-spatial-analysis","eyebrow":"hybrid · analysis run","keywords":"gis-analytics Data engineer Spatial analyst Workspace administrator Decision consumer draft Draft validating Validating published Published processing Processing ready Ready shared Shared failed Failed create_dataset_version dataset.version_created validate dataset.validation_started publish dataset.published run_analysis analysis.started complete_analysis analysis.completed create_share share.created Published input and output versions are immutable. Every output records exact input versions, parameters, runtime, and actor. Workspace authorization applies separately to source, job, output, visualization, and share. A retry is linked to its previous attempt and never overwrites it. Revoking a share does not destroy dataset or analysis lineage."},{"id":"journey:durable-weekend-itinerary","kind":"Journey","title":"Durable multi-stop itinerary","description":"Discover provider-backed places, preserve their Mappls Pins in a versioned itinerary, preview the exact ordered route, invalidate stale plans on edits, and retain visit or skip progress through completion.","href":"/journeys/durable-weekend-itinerary","eyebrow":"hybrid · trip itinerary","keywords":"routes-navigation Traveller Collaborator Mappls discovery service Mappls routing service draft Draft planned Planned active Active paused Paused completed Completed cancelled Cancelled create_trip trip.created add_or_reorder_stop trip.sequence_changed preview_route trip.route_previewed start_trip trip.started pause_trip trip.paused resume_trip trip.resumed visit_or_skip_next trip.stop_completed complete_trip trip.completed cancel_trip trip.cancelled Every saved stop originated from provider-backed discovery and retains its Mappls Pin and provenance. A Mappls Pin occurs at most once in an itinerary. A route revision is valid only for the exact ordered stop list and constraints that produced it. Only the next pending stop may receive a visit or skip outcome. Completion is impossible while any stop remains pending. Commands are idempotent and compare the expected trip version."},{"id":"journey:consented-address-verification","kind":"Journey","title":"Consented address verification","description":"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.","href":"/journeys/consented-address-verification","eyebrow":"stateful · address verification","keywords":"search-places Application user Evidence capture application Policy service Human reviewer Privacy service entered Entered normalized Normalized capture_authorized Capture authorized evidence_captured Evidence captured compared Compared review_required Review required verified Verified rejected Rejected cancelled Cancelled enter_verification address_verification.entered normalize_address address_verification.normalized authorize_capture address_verification.capture_authorized revoke_consent address_verification.consent_revoked capture_evidence address_verification.evidence_captured compare address_verification.compared verify address_verification.verified reject address_verification.rejected defer address_verification.review_required review_verify address_verification.verified review_reject address_verification.rejected One external business reference maps to one verification aggregate. Precise evidence is accepted only under active consent for the exact declared purpose and time window. Provider normalization and application policy are identified separately. An automated actor cannot override its own policy recommendation. Every terminal outcome retains evidence hash, policy version, actor, and attributable reason. Precise evidence can be redacted without erasing the audit trail or claiming that retained hashes can reconstruct it."},{"id":"journey:governed-spatial-agent-run","kind":"Journey","title":"Governed spatial agent run","description":"Turn a natural-language spatial objective into an inspectable plan, obtain an exact least-privilege approval, execute allow-listed Mappls tools, and cite provider evidence without exposing credentials to the model.","href":"/journeys/governed-spatial-agent-run","eyebrow":"stateful · agent run","keywords":"ai-location Application user Agent planner Human approver Execution service Mappls MCP server asked Asked planned Planned approved Approved executing Executing completed Completed rejected Rejected failed Failed ask agent.question_received create_plan agent.plan_created approve_plan agent.plan_approved reject_plan agent.plan_rejected start_execution agent.execution_started complete_execution agent.execution_completed The model never receives Mappls or customer credentials. Only schema-valid allow-listed tools and bounded arguments can enter a plan. Approval names the canonical immutable plan hash and every required scope. An expired, superseded, partially scoped, or self-approved plan cannot execute. Every factual provider claim is traceable to retained Mappls provenance. Tool failures and persisted evidence never expose secrets."},{"id":"journey:offline-automotive-release","kind":"Journey","title":"Offline automotive release","description":"Manufacture, activate, install, operate, update, recover, and retire a navigation runtime and map-data release as one compatible system.","href":"/journeys/offline-automotive-release","eyebrow":"stateful · device release","keywords":"offline-automotive Manufacturing system Fleet release manager Vehicle runtime Support engineer manufactured Manufactured activated Activated installed Installed operational Operational updating Updating recovering Recovering retired Retired register_device device.registered activate license.activated stage_base_release release.installed qualify release.qualified start_update release.update_started rollback release.rollback_started retire device.retired Runtime, map data, configuration, and voice assets are qualified as one compatible manifest. Only a verified inactive slot may replace the active slot. Power loss at any update point leaves one bootable known-good slot. Activation identity and secrets are distinct from vehicle business identity. Retirement revokes protected access without erasing support and release history."},{"id":"journey:widget-selection-session","kind":"Journey","title":"Application-owned widget selection","description":"Launch a Mappls widget, recover through a useful fallback, validate a narrow candidate, commit it deliberately, invalidate stale selection, and submit one durable business record.","href":"/journeys/widget-selection-session","eyebrow":"hybrid · widget selection session","keywords":"app-widgets-deep-links Application user Host application Platform adapter Mappls widget draft Draft widget_open Widget open fallback_active Fallback active candidate_received Candidate received selected Selected submitted Submitted cancelled Cancelled create_session host.session_created open_widget widget.opened activate_fallback widget.fallback_activated receive_candidate location.candidate_received accept_selection location.selected edit_host_text host.text_edited submit host.submitted cancel host.cancelled A provider callback or browser message creates only a candidate, never a submitted business record. Every browser message matches the exact reviewed origin and a versioned allow-listed schema. Only a six-character alphanumeric Mappls Pin and bounded printable label enter durable selection state. A host-text edit invalidates every candidate and committed selection from the previous draft version. One launch generation produces at most one terminal adapter outcome; late callbacks are ignored. Credentials, provider controllers, native views, bridge objects, and opaque response payloads are never persisted."},{"id":"journey:ios-direction-planning-handoff","kind":"Journey","title":"iOS direction planning and navigation handoff","description":"Own route intent and revisions in the host app, present MapplsDirectionUI for editing and calculation, validate the selected route callback, and hand off to navigation without confusing a UI request with a started or completed trip.","href":"/journeys/ios-direction-planning-handoff","eyebrow":"hybrid · route planning session","keywords":"routes-navigation Traveler Host application MapplsDirectionUI Navigation adapter draft Draft editing Editing calculating Calculating candidates_ready Candidates ready selected Selected handoff_pending Handoff pending handed_off Handed off cancelled Cancelled create_plan route_plan.created open_direction_ui route_plan.editor_opened request_routes route_plan.calculation_requested receive_routes route_plan.candidates_received select_route route_plan.route_selected request_navigation route_plan.navigation_requested confirm_handoff route_plan.navigation_handed_off cancel_plan route_plan.cancelled Stops, options, route candidates, and selection share one explicit revision. A selected index is validated before dereferencing its Route candidate. The provider controller and opaque Route objects never become durable application records. The start-navigation callback expresses intent, not proof that navigation started or completed. One presentation generation produces at most one terminal handoff or cancellation. Credentials and unrestricted location histories never enter route-planning audit events."},{"id":"journey:ios-geofence-draft","kind":"Journey","title":"iOS geofence draft and publication boundary","description":"Present the Mappls geofence editor, normalize circle or polygon output into a versioned application draft, validate geometry and policy, and stop at a review-ready artifact until a separately documented provider publication contract is selected.","href":"/journeys/ios-geofence-draft","eyebrow":"hybrid · geofence draft","keywords":"intouch-telematics Operations author Host application MapplsGeofenceUI Geofence reviewer Rule-publication adapter draft Draft editing Editing candidate Candidate review_pending Review pending approved_draft Approved draft cancelled Cancelled create_geofence_draft geofence_draft.created open_editor geofence_draft.editor_opened receive_geometry geofence_draft.geometry_received submit_for_review geofence_draft.review_requested approve_draft geofence_draft.approved cancel_edit geofence_draft.cancelled Editor output is an application candidate, not evidence of a published provider rule. Only canonical validated circle or polygon geometry enters review. Each geometry revision is immutable and linked to the editor generation that produced it. Purpose, subject scope, schedule intent, and policy version travel with geometry review. Publishing requires a separately documented, entitled rule contract and creates a separate provider identity mapping. Provider views, delegates, map layers, credentials, and opaque callback objects are never persisted."},{"id":"journey:ios-feedback-report-review","kind":"Journey","title":"iOS feedback report and review","description":"Open one feedback UI generation, normalize a bounded report candidate, commit an application submission, reconcile provider acknowledgement separately, review evidence, and close only with an attributable resolution.","href":"/journeys/ios-feedback-report-review","eyebrow":"hybrid · feedback report","keywords":"capture-feedback Contributor Host application Mappls Feedback Kit Provider adapter Operations reviewer draft Draft capturing Capturing candidate Candidate submitted Submitted provider_pending Provider pending review_pending Review pending resolved Resolved rejected Rejected cancelled Cancelled create_report feedback_report.created open_feedback_ui feedback_report.ui_opened receive_candidate feedback_report.candidate_received commit_submission feedback_report.submitted request_provider_submission feedback_report.provider_requested queue_review feedback_report.review_queued resolve_report feedback_report.resolved reject_report feedback_report.rejected cancel_report feedback_report.cancelled A UI callback creates only a candidate; it cannot prove application submission, provider receipt, publication, or resolution. One presentation generation produces at most one accepted terminal result and all late callbacks are ignored. Every submission revision is immutable and content-hashed; rework creates a new linked attempt. Provider acknowledgement and reviewer disposition are separate attributable records. Credentials, view controllers, delegates, attachment bodies, and opaque provider payloads never enter durable state. Idempotency, optimistic concurrency, audit, outbox, privacy purpose, retention, and redaction apply to every committed transition."},{"id":"journey:location-capture-evidence","kind":"Journey","title":"Consent-bound location capture evidence","description":"Initialize and configure an entitled Location Capture SDK, acquire a bounded single or subscribed fix, preserve accuracy and timing as evidence, review weak results, and stop every native resource deterministically.","href":"/journeys/location-capture-evidence","eyebrow":"hybrid · location capture attempt","keywords":"capture-feedback Application user Host application Platform adapter Evidence reviewer Mappls Location Capture SDK draft Draft permission_pending Permission pending ready Ready acquiring Acquiring candidate Candidate review_pending Review pending accepted Accepted cancelled Cancelled create_attempt location_capture.attempt_created request_permission location_capture.permission_requested prepare_sdk location_capture.sdk_ready start_acquisition location_capture.acquisition_started receive_location location_capture.candidate_received queue_review location_capture.review_queued accept_evidence location_capture.evidence_accepted approve_weak_evidence location_capture.weak_evidence_approved cancel_attempt location_capture.attempt_cancelled A permission grant is not consent for every purpose; purpose, policy, and retention are recorded separately. One acquisition generation owns one callback family, timeout, stop, and unsubscribe lifecycle. Accuracy, event time, receipt time, and policy result remain attached to the normalized coordinates. A callback creates a candidate, never an accepted business decision. Weak or stale evidence cannot pass an automatic acceptance threshold by omitting quality fields. Credentials, native manager instances, full opaque payloads, and callback closures never enter durable storage."},{"id":"journey:place-contribution-publication","kind":"Journey","title":"Governed place contribution and publication","description":"Embed the credential-free Add a Place surface, record what the user reports, reconcile independently, and call a place published only when durable provider-backed evidence exists.","href":"/journeys/place-contribution-publication","eyebrow":"stateful · place contribution","keywords":"capture-feedback Contributor Host application Operations reviewer Mappls hosted widget and search draft Draft widget_open Widget open submission_reported Submission reported publication_pending Publication pending published Published rejected Rejected withdrawn Withdrawn create_contribution place_contribution.created open_widget place_contribution.widget_opened report_submission place_contribution.submission_reported queue_reconciliation place_contribution.reconciliation_queued confirm_publication place_contribution.published reject place_contribution.rejected retry place_contribution.retried withdraw place_contribution.withdrawn A hosted success screen or contributor report never proves publication. No callback, browser message, receipt, moderation status, or withdrawal capability is invented when the public source does not document it. Only provider-backed evidence containing a valid Mappls Pin can close the aggregate as published. Every widget attempt is immutable and linked to the aggregate version that opened it. Commands are idempotent, compare expected version, and commit audit plus outbox atomically. Contribution text, actor identity, and precise location follow declared purpose, access, and retention boundaries."},{"id":"journey:realview-remote-inspection","kind":"Journey","title":"Entitled RealView remote inspection","description":"Qualify paid RealView entitlement, open one browser-visible-token viewer attempt, handle the documented no-imagery signal safely, and turn human observations into a reviewed business record without inventing panorama metadata.","href":"/journeys/realview-remote-inspection","eyebrow":"stateful · remote visual inspection","keywords":"app-widgets-deep-links Inspector Inspection reviewer Platform administrator Host application Mappls RealView widget draft Draft entitlement_pending Entitlement pending ready Ready viewing Viewing coverage_unavailable Coverage unavailable observation_recorded Observation recorded review_pending Review pending accepted Accepted rework_required Rework required cancelled Cancelled create_inspection realview_inspection.created request_entitlement realview_inspection.entitlement_requested confirm_entitlement realview_inspection.entitlement_confirmed open_viewer realview_inspection.viewer_opened record_no_coverage realview_inspection.coverage_unavailable record_observation realview_inspection.observation_recorded submit_review realview_inspection.review_requested accept realview_inspection.accepted request_rework realview_inspection.rework_requested record_entitlement_expired realview_inspection.entitlement_expired cancel realview_inspection.cancelled No server secret, browser token value, or complete token-bearing iframe URL is persisted, logged, analyzed, exported, or sent to a model. The exact selected origin and narrow documented schema are checked before any browser message reaches domain state. Status 204 proves only no imagery for one attempt and configuration; HTTP 200 and frame load prove only a delivered shell. Human observation is distinct from provider imagery, panorama metadata, measurement, currentness, and inspection acceptance. Imagery is not copied, screenshotted, exported, or retained without an explicit licensed product contract and purpose-specific policy. Every command is idempotent, compares expected version, and commits snapshot, audit, receipt, and outbox atomically. Reviewer acceptance is attributable and cannot be performed by the same automated actor that created the observation."},{"id":"journey:vision-inference-review","kind":"Journey","title":"Governed SkyDNN inference review","description":"Lock an entitled model to an immutable asset identity, call the documented synchronous prediction boundary, validate geometry and confidence, require independent review, and redact derived detections on schedule.","href":"/journeys/vision-inference-review","eyebrow":"stateful · vision evidence case","keywords":"ai-location Asset steward Vision worker Policy service Independent reviewer Privacy worker Mappls SkyDNN API registered Registered model_locked Model locked inference_requested Inference requested inferred Inferred review_pending Review pending accepted Accepted rejected Rejected redacted Redacted register_case vision.case_registered lock_model vision.model_locked request_inference vision.inference_requested record_inference vision.inference_recorded submit_review vision.review_requested accept vision.accepted reject vision.rejected redact vision.redacted No image bytes, media URL, bearer token, credential, face, number plate, or provider-internal file path enters the reference case store. The provider POST /predict call is synchronous; application queue, review, retry, decision, and retention states are never attributed to SkyDNN. Every attempt binds an immutable asset hash to one discovered model fingerprint and policy version. Confidence and geometry are evidence, not a business outcome or live safety command. Reviewer identity is independent from the fixture inference actor and every override or rejection has a reason. Idempotency, optimistic versions, audit, receipts, and outbox commit atomically."},{"id":"journey-workshop:field-service-task","kind":"Journey workshop","title":"Build Field-service task lifecycle","description":"An eight-lab, source-bounded workshop for the complete task lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/field-service-task/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"workmate task Field Service Console Model the lifecycle before the UI Turn the task blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Field Service Console capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 8 reviewed transitions are implemented with actor and source-state checks. All 8 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Field Service Console capstone passes 6 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:connected-fleet-trip","kind":"Journey workshop","title":"Build Connected fleet trip","description":"An eight-lab, source-bounded workshop for the complete trip lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/connected-fleet-trip/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"intouch-telematics trip Delivery Control Tower Model the lifecycle before the UI Turn the trip blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Delivery Control Tower capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 7 reviewed transitions are implemented with actor and source-state checks. All 7 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Delivery Control Tower capstone passes 7 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:fleet-geofence-exception","kind":"Journey workshop","title":"Build Fleet geofence exception","description":"An eight-lab, source-bounded workshop for the complete geofence case lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/fleet-geofence-exception/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"intouch-telematics geofence case Fleet Geofence Monitor Model the lifecycle before the UI Turn the geofence case blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Fleet Geofence Monitor capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 5 reviewed transitions are implemented with actor and source-state checks. All 5 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Fleet Geofence Monitor capstone passes 7 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:emergency-incident-response","kind":"Journey workshop","title":"Build Coordinated incident response","description":"An eight-lab, source-bounded workshop for the complete incident lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/emergency-incident-response/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"routes-navigation incident Incident Dispatch Model the lifecycle before the UI Turn the incident blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Incident Dispatch capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 8 reviewed transitions are implemented with actor and source-state checks. All 8 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Incident Dispatch capstone passes 8 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:navigation-session","kind":"Journey workshop","title":"Build Recoverable navigation session","description":"An eight-lab, source-bounded workshop for the complete navigation session lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/navigation-session/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"routes-navigation navigation session Weekend Trip Planner Model the lifecycle before the UI Turn the navigation session blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Weekend Trip Planner capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 6 reviewed transitions are implemented with actor and source-state checks. All 6 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Weekend Trip Planner capstone passes 8 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:governed-spatial-analysis","kind":"Journey workshop","title":"Build Governed spatial analysis","description":"An eight-lab, source-bounded workshop for the complete analysis run lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/governed-spatial-analysis/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"gis-analytics analysis run Retail Site Lab Model the lifecycle before the UI Turn the analysis run blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Retail Site Lab capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 6 reviewed transitions are implemented with actor and source-state checks. All 6 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Retail Site Lab capstone passes 8 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:durable-weekend-itinerary","kind":"Journey workshop","title":"Build Durable multi-stop itinerary","description":"An eight-lab, source-bounded workshop for the complete trip itinerary lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/durable-weekend-itinerary/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"routes-navigation trip itinerary Weekend Trip Planner Model the lifecycle before the UI Turn the trip itinerary blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Weekend Trip Planner capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 9 reviewed transitions are implemented with actor and source-state checks. All 9 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Weekend Trip Planner capstone passes 8 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:consented-address-verification","kind":"Journey workshop","title":"Build Consented address verification","description":"An eight-lab, source-bounded workshop for the complete address verification lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/consented-address-verification/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"search-places address verification Address Verifier Model the lifecycle before the UI Turn the address verification blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Address Verifier capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 11 reviewed transitions are implemented with actor and source-state checks. All 9 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Address Verifier capstone passes 8 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:governed-spatial-agent-run","kind":"Journey workshop","title":"Build Governed spatial agent run","description":"An eight-lab, source-bounded workshop for the complete agent run lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/governed-spatial-agent-run/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"ai-location agent run Spatial Operations Agent Model the lifecycle before the UI Turn the agent run blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Spatial Operations Agent capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 6 reviewed transitions are implemented with actor and source-state checks. All 6 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Spatial Operations Agent capstone passes 15 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:offline-automotive-release","kind":"Journey workshop","title":"Build Offline automotive release","description":"An eight-lab, source-bounded workshop for the complete device release lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/offline-automotive-release/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"offline-automotive device release Offline Release Control Model the lifecycle before the UI Turn the device release blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Offline Release Control capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 7 reviewed transitions are implemented with actor and source-state checks. All 7 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Offline Release Control capstone passes 10 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:widget-selection-session","kind":"Journey workshop","title":"Build Application-owned widget selection","description":"An eight-lab, source-bounded workshop for the complete widget selection session lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/widget-selection-session/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"app-widgets-deep-links widget selection session Widget Journey Host Model the lifecycle before the UI Turn the widget selection session blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Widget Journey Host capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 8 reviewed transitions are implemented with actor and source-state checks. All 8 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Widget Journey Host capstone passes 8 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:ios-direction-planning-handoff","kind":"Journey workshop","title":"Build iOS direction planning and navigation handoff","description":"An eight-lab, source-bounded workshop for the complete route planning session lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/ios-direction-planning-handoff/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"routes-navigation route planning session Deep-link & Native UI Journey Host Model the lifecycle before the UI Turn the route planning session blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Deep-link & Native UI Journey Host capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 8 reviewed transitions are implemented with actor and source-state checks. All 8 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Deep-link & Native UI Journey Host capstone passes 11 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:ios-geofence-draft","kind":"Journey workshop","title":"Build iOS geofence draft and publication boundary","description":"An eight-lab, source-bounded workshop for the complete geofence draft lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/ios-geofence-draft/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"intouch-telematics geofence draft Deep-link & Native UI Journey Host Model the lifecycle before the UI Turn the geofence draft blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Deep-link & Native UI Journey Host capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 6 reviewed transitions are implemented with actor and source-state checks. All 6 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Deep-link & Native UI Journey Host capstone passes 11 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:ios-feedback-report-review","kind":"Journey workshop","title":"Build iOS feedback report and review","description":"An eight-lab, source-bounded workshop for the complete feedback report lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/ios-feedback-report-review/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"capture-feedback feedback report Place Contribution Desk Model the lifecycle before the UI Turn the feedback report blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Place Contribution Desk capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 9 reviewed transitions are implemented with actor and source-state checks. All 9 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Place Contribution Desk capstone passes 8 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:location-capture-evidence","kind":"Journey workshop","title":"Build Consent-bound location capture evidence","description":"An eight-lab, source-bounded workshop for the complete location capture attempt lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/location-capture-evidence/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"capture-feedback location capture attempt Address Verifier Model the lifecycle before the UI Turn the location capture attempt blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Address Verifier capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 9 reviewed transitions are implemented with actor and source-state checks. All 9 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Address Verifier capstone passes 8 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:place-contribution-publication","kind":"Journey workshop","title":"Build Governed place contribution and publication","description":"An eight-lab, source-bounded workshop for the complete place contribution lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/place-contribution-publication/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"capture-feedback place contribution Place Contribution Desk Model the lifecycle before the UI Turn the place contribution blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Place Contribution Desk capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 8 reviewed transitions are implemented with actor and source-state checks. All 8 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Place Contribution Desk capstone passes 8 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:realview-remote-inspection","kind":"Journey workshop","title":"Build Entitled RealView remote inspection","description":"An eight-lab, source-bounded workshop for the complete remote visual inspection lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/realview-remote-inspection/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"app-widgets-deep-links remote visual inspection RealView Inspection Desk Model the lifecycle before the UI Turn the remote visual inspection blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the RealView Inspection Desk capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 11 reviewed transitions are implemented with actor and source-state checks. All 11 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The RealView Inspection Desk capstone passes 10 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"journey-workshop:vision-inference-review","kind":"Journey workshop","title":"Build Governed SkyDNN inference review","description":"An eight-lab, source-bounded workshop for the complete vision evidence case lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.","href":"/journeys/vision-inference-review/workshop","eyebrow":"8 labs · 2 hr 10 min","keywords":"ai-location vision evidence case Vision Evidence Desk Model the lifecycle before the UI Turn the vision evidence case blueprint into an explicit aggregate boundary owned by the application. Implement every command and event pair Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together. Persist restart-safe records Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery. Make concurrency and replay deterministic Apply optimistic expected versions and aggregate-scoped idempotency before executing effects. Control effects and unknown outcomes Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results. Run all hostile fixture scenarios Exercise the success path plus replay, concurrency, state, and response-loss failures without an account. Trace the Vision Evidence Desk capstone Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test. Qualify the real integration boundary Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants. All 8 reviewed transitions are implemented with actor and source-state checks. All 8 application event identities are immutable and versioned. Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested. Aggregate, event, audit, command result, and outbox intent commit atomically. The Vision Evidence Desk capstone passes 10 declared tests after archive checksum verification. Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced."},{"id":"event:field-service-task-task-created","kind":"Event","title":"task.created","description":"Application-owned task fact emitted after create_task reaches unassigned.","href":"/events/field-service-task-task-created","eyebrow":"stateful · task · v1","keywords":"Task Created field-service-task Field-service task lifecycle workmate create_task Integration service  unassigned outbox idempotency replay deduplication event schema"},{"id":"event:field-service-task-task-assigned","kind":"Event","title":"task.assigned","description":"Application-owned task fact emitted after assign reaches assigned.","href":"/events/field-service-task-task-assigned","eyebrow":"stateful · task · v1","keywords":"Task Assigned field-service-task Field-service task lifecycle workmate assign Dispatcher unassigned assigned assigned outbox idempotency replay deduplication event schema"},{"id":"event:field-service-task-task-accepted","kind":"Event","title":"task.accepted","description":"Application-owned task fact emitted after accept reaches accepted.","href":"/events/field-service-task-task-accepted","eyebrow":"stateful · task · v1","keywords":"Task Accepted field-service-task Field-service task lifecycle workmate accept Field worker assigned accepted outbox idempotency replay deduplication event schema"},{"id":"event:field-service-task-task-en-route","kind":"Event","title":"task.en_route","description":"Application-owned task fact emitted after start_travel reaches en_route.","href":"/events/field-service-task-task-en-route","eyebrow":"stateful · task · v1","keywords":"Task En Route field-service-task Field-service task lifecycle workmate start_travel Field worker accepted en_route outbox idempotency replay deduplication event schema"},{"id":"event:field-service-task-task-started","kind":"Event","title":"task.started","description":"Application-owned task fact emitted after arrive reaches in_progress.","href":"/events/field-service-task-task-started","eyebrow":"stateful · task · v1","keywords":"Task Started field-service-task Field-service task lifecycle workmate arrive Field worker en_route in_progress outbox idempotency replay deduplication event schema"},{"id":"event:field-service-task-task-proof-submitted","kind":"Event","title":"task.proof_submitted","description":"Application-owned task fact emitted after submit_proof reaches proof_pending.","href":"/events/field-service-task-task-proof-submitted","eyebrow":"stateful · task · v1","keywords":"Task Proof Submitted field-service-task Field-service task lifecycle workmate submit_proof Field worker in_progress proof_pending outbox idempotency replay deduplication event schema"},{"id":"event:field-service-task-task-completed","kind":"Event","title":"task.completed","description":"Application-owned task fact emitted after approve_proof reaches completed.","href":"/events/field-service-task-task-completed","eyebrow":"stateful · task · v1","keywords":"Task Completed field-service-task Field-service task lifecycle workmate approve_proof Supervisor proof_pending completed outbox idempotency replay deduplication event schema"},{"id":"event:field-service-task-task-proof-rejected","kind":"Event","title":"task.proof_rejected","description":"Application-owned task fact emitted after reject_proof reaches in_progress.","href":"/events/field-service-task-task-proof-rejected","eyebrow":"stateful · task · v1","keywords":"Task Proof Rejected field-service-task Field-service task lifecycle workmate reject_proof Supervisor proof_pending in_progress outbox idempotency replay deduplication event schema"},{"id":"event:connected-fleet-trip-trip-created","kind":"Event","title":"trip.created","description":"Application-owned trip fact emitted after create_trip reaches planned.","href":"/events/connected-fleet-trip-trip-created","eyebrow":"stateful · trip · v1","keywords":"Trip Created connected-fleet-trip Connected fleet trip intouch-telematics create_trip Fleet planner  planned outbox idempotency replay deduplication event schema"},{"id":"event:connected-fleet-trip-trip-ready","kind":"Event","title":"trip.ready","description":"Application-owned trip fact emitted after confirm_device_ready reaches ready.","href":"/events/connected-fleet-trip-trip-ready","eyebrow":"stateful · trip · v1","keywords":"Trip Ready connected-fleet-trip Connected fleet trip intouch-telematics confirm_device_ready Telematics service planned ready outbox idempotency replay deduplication event schema"},{"id":"event:connected-fleet-trip-trip-started","kind":"Event","title":"trip.started","description":"Application-owned trip fact emitted after start_trip reaches active.","href":"/events/connected-fleet-trip-trip-started","eyebrow":"stateful · trip · v1","keywords":"Trip Started connected-fleet-trip Connected fleet trip intouch-telematics start_trip Driver ready active outbox idempotency replay deduplication event schema"},{"id":"event:connected-fleet-trip-trip-exception-raised","kind":"Event","title":"trip.exception_raised","description":"Application-owned trip fact emitted after raise_exception reaches exception.","href":"/events/connected-fleet-trip-trip-exception-raised","eyebrow":"stateful · trip · v1","keywords":"Trip Exception Raised connected-fleet-trip Connected fleet trip intouch-telematics raise_exception Telematics service active exception exception outbox idempotency replay deduplication event schema"},{"id":"event:connected-fleet-trip-trip-exception-resolved","kind":"Event","title":"trip.exception_resolved","description":"Application-owned trip fact emitted after resolve_exception reaches active.","href":"/events/connected-fleet-trip-trip-exception-resolved","eyebrow":"stateful · trip · v1","keywords":"Trip Exception Resolved connected-fleet-trip Connected fleet trip intouch-telematics resolve_exception Operations controller exception active outbox idempotency replay deduplication event schema"},{"id":"event:connected-fleet-trip-trip-close-requested","kind":"Event","title":"trip.close_requested","description":"Application-owned trip fact emitted after request_close reaches closing.","href":"/events/connected-fleet-trip-trip-close-requested","eyebrow":"stateful · trip · v1","keywords":"Trip Close Requested connected-fleet-trip Connected fleet trip intouch-telematics request_close Driver active exception closing outbox idempotency replay deduplication event schema"},{"id":"event:connected-fleet-trip-trip-closed","kind":"Event","title":"trip.closed","description":"Application-owned trip fact emitted after close_trip reaches closed.","href":"/events/connected-fleet-trip-trip-closed","eyebrow":"stateful · trip · v1","keywords":"Trip Closed connected-fleet-trip Connected fleet trip intouch-telematics close_trip Telematics service closing closed outbox idempotency replay deduplication event schema"},{"id":"event:fleet-geofence-exception-geofence-published","kind":"Event","title":"geofence.published","description":"Application-owned geofence case fact emitted after publish_geofence reaches active.","href":"/events/fleet-geofence-exception-geofence-published","eyebrow":"stateful · geofence case · v1","keywords":"Geofence Published fleet-geofence-exception Fleet geofence exception intouch-telematics publish_geofence Fleet administrator draft active outbox idempotency replay deduplication event schema"},{"id":"event:fleet-geofence-exception-geofence-breached","kind":"Event","title":"geofence.breached","description":"Application-owned geofence case fact emitted after record_breach reaches breached.","href":"/events/fleet-geofence-exception-geofence-breached","eyebrow":"stateful · geofence case · v1","keywords":"Geofence Breached fleet-geofence-exception Fleet geofence exception intouch-telematics record_breach Telematics service active breached breached outbox idempotency replay deduplication event schema"},{"id":"event:fleet-geofence-exception-geofence-case-acknowledged","kind":"Event","title":"geofence_case.acknowledged","description":"Application-owned geofence case fact emitted after acknowledge_case reaches acknowledged.","href":"/events/fleet-geofence-exception-geofence-case-acknowledged","eyebrow":"stateful · geofence case · v1","keywords":"Geofence Case Acknowledged fleet-geofence-exception Fleet geofence exception intouch-telematics acknowledge_case Operations controller breached acknowledged outbox idempotency replay deduplication event schema"},{"id":"event:fleet-geofence-exception-geofence-case-resolved","kind":"Event","title":"geofence_case.resolved","description":"Application-owned geofence case fact emitted after resolve_case reaches resolved.","href":"/events/fleet-geofence-exception-geofence-case-resolved","eyebrow":"stateful · geofence case · v1","keywords":"Geofence Case Resolved fleet-geofence-exception Fleet geofence exception intouch-telematics resolve_case Operations controller acknowledged resolved outbox idempotency replay deduplication event schema"},{"id":"event:fleet-geofence-exception-geofence-retired","kind":"Event","title":"geofence.retired","description":"Application-owned geofence case fact emitted after retire_geofence reaches retired.","href":"/events/fleet-geofence-exception-geofence-retired","eyebrow":"stateful · geofence case · v1","keywords":"Geofence Retired fleet-geofence-exception Fleet geofence exception intouch-telematics retire_geofence Fleet administrator draft active retired outbox idempotency replay deduplication event schema"},{"id":"event:emergency-incident-response-incident-reported","kind":"Event","title":"incident.reported","description":"Application-owned incident fact emitted after report_incident reaches reported.","href":"/events/emergency-incident-response-incident-reported","eyebrow":"stateful · incident · v1","keywords":"Incident Reported emergency-incident-response Coordinated incident response routes-navigation report_incident Call taker  reported outbox idempotency replay deduplication event schema"},{"id":"event:emergency-incident-response-incident-located","kind":"Event","title":"incident.located","description":"Application-owned incident fact emitted after resolve_location reaches located.","href":"/events/emergency-incident-response-incident-located","eyebrow":"stateful · incident · v1","keywords":"Incident Located emergency-incident-response Coordinated incident response routes-navigation resolve_location Dispatcher reported located outbox idempotency replay deduplication event schema"},{"id":"event:emergency-incident-response-incident-dispatched","kind":"Event","title":"incident.dispatched","description":"Application-owned incident fact emitted after dispatch reaches dispatched.","href":"/events/emergency-incident-response-incident-dispatched","eyebrow":"stateful · incident · v1","keywords":"Incident Dispatched emergency-incident-response Coordinated incident response routes-navigation dispatch Dispatcher located dispatched outbox idempotency replay deduplication event schema"},{"id":"event:emergency-incident-response-dispatch-accepted","kind":"Event","title":"dispatch.accepted","description":"Application-owned incident fact emitted after accept_dispatch reaches en_route.","href":"/events/emergency-incident-response-dispatch-accepted","eyebrow":"stateful · incident · v1","keywords":"Dispatch Accepted emergency-incident-response Coordinated incident response routes-navigation accept_dispatch Responder dispatched en_route outbox idempotency replay deduplication event schema"},{"id":"event:emergency-incident-response-unit-position-recorded","kind":"Event","title":"unit.position_recorded","description":"Application-owned incident fact emitted after record_position reaches en_route.","href":"/events/emergency-incident-response-unit-position-recorded","eyebrow":"stateful · incident · v1","keywords":"Unit Position Recorded emergency-incident-response Coordinated incident response routes-navigation record_position Telematics service en_route en_route outbox idempotency replay deduplication event schema"},{"id":"event:emergency-incident-response-incident-arrived","kind":"Event","title":"incident.arrived","description":"Application-owned incident fact emitted after confirm_arrival reaches on_scene.","href":"/events/emergency-incident-response-incident-arrived","eyebrow":"stateful · incident · v1","keywords":"Incident Arrived emergency-incident-response Coordinated incident response routes-navigation confirm_arrival Responder en_route on_scene outbox idempotency replay deduplication event schema"},{"id":"event:emergency-incident-response-incident-resolved","kind":"Event","title":"incident.resolved","description":"Application-owned incident fact emitted after resolve reaches resolved.","href":"/events/emergency-incident-response-incident-resolved","eyebrow":"stateful · incident · v1","keywords":"Incident Resolved emergency-incident-response Coordinated incident response routes-navigation resolve Responder on_scene resolved outbox idempotency replay deduplication event schema"},{"id":"event:emergency-incident-response-incident-reviewed","kind":"Event","title":"incident.reviewed","description":"Application-owned incident fact emitted after review reaches reviewed.","href":"/events/emergency-incident-response-incident-reviewed","eyebrow":"stateful · incident · v1","keywords":"Incident Reviewed emergency-incident-response Coordinated incident response routes-navigation review Incident commander resolved reviewed outbox idempotency replay deduplication event schema"},{"id":"event:navigation-session-route-calculated","kind":"Event","title":"route.calculated","description":"Application-owned navigation session fact emitted after calculate_route reaches preview.","href":"/events/navigation-session-route-calculated","eyebrow":"hybrid · navigation session · v1","keywords":"Route Calculated navigation-session Recoverable navigation session routes-navigation calculate_route Navigation application draft preview preview outbox idempotency replay deduplication event schema"},{"id":"event:navigation-session-navigation-started","kind":"Event","title":"navigation.started","description":"Application-owned navigation session fact emitted after start_guidance reaches navigating.","href":"/events/navigation-session-navigation-started","eyebrow":"hybrid · navigation session · v1","keywords":"Navigation Started navigation-session Recoverable navigation session routes-navigation start_guidance Driver preview navigating outbox idempotency replay deduplication event schema"},{"id":"event:navigation-session-reroute-requested","kind":"Event","title":"reroute.requested","description":"Application-owned navigation session fact emitted after request_reroute reaches rerouting.","href":"/events/navigation-session-reroute-requested","eyebrow":"hybrid · navigation session · v1","keywords":"Reroute Requested navigation-session Recoverable navigation session routes-navigation request_reroute Navigation application navigating rerouting rerouting outbox idempotency replay deduplication event schema"},{"id":"event:navigation-session-route-updated","kind":"Event","title":"route.updated","description":"Application-owned navigation session fact emitted after accept_reroute reaches navigating.","href":"/events/navigation-session-route-updated","eyebrow":"hybrid · navigation session · v1","keywords":"Route Updated navigation-session Recoverable navigation session routes-navigation accept_reroute Mappls navigation SDK rerouting navigating outbox idempotency replay deduplication event schema"},{"id":"event:navigation-session-navigation-arrived","kind":"Event","title":"navigation.arrived","description":"Application-owned navigation session fact emitted after confirm_arrival reaches arrived.","href":"/events/navigation-session-navigation-arrived","eyebrow":"hybrid · navigation session · v1","keywords":"Navigation Arrived navigation-session Recoverable navigation session routes-navigation confirm_arrival Navigation application navigating arrived outbox idempotency replay deduplication event schema"},{"id":"event:navigation-session-navigation-ended","kind":"Event","title":"navigation.ended","description":"Application-owned navigation session fact emitted after end_session reaches ended.","href":"/events/navigation-session-navigation-ended","eyebrow":"hybrid · navigation session · v1","keywords":"Navigation Ended navigation-session Recoverable navigation session routes-navigation end_session Driver preview navigating rerouting arrived ended outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-analysis-dataset-version-created","kind":"Event","title":"dataset.version_created","description":"Application-owned analysis run fact emitted after create_dataset_version reaches draft.","href":"/events/governed-spatial-analysis-dataset-version-created","eyebrow":"hybrid · analysis run · v1","keywords":"Dataset Version Created governed-spatial-analysis Governed spatial analysis gis-analytics create_dataset_version Data engineer  draft outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-analysis-dataset-validation-started","kind":"Event","title":"dataset.validation_started","description":"Application-owned analysis run fact emitted after validate reaches validating.","href":"/events/governed-spatial-analysis-dataset-validation-started","eyebrow":"hybrid · analysis run · v1","keywords":"Dataset Validation Started governed-spatial-analysis Governed spatial analysis gis-analytics validate Spatial analyst draft validating outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-analysis-dataset-published","kind":"Event","title":"dataset.published","description":"Application-owned analysis run fact emitted after publish reaches published.","href":"/events/governed-spatial-analysis-dataset-published","eyebrow":"hybrid · analysis run · v1","keywords":"Dataset Published governed-spatial-analysis Governed spatial analysis gis-analytics publish Workspace administrator validating published outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-analysis-analysis-started","kind":"Event","title":"analysis.started","description":"Application-owned analysis run fact emitted after run_analysis reaches processing.","href":"/events/governed-spatial-analysis-analysis-started","eyebrow":"hybrid · analysis run · v1","keywords":"Analysis Started governed-spatial-analysis Governed spatial analysis gis-analytics run_analysis Spatial analyst published ready processing outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-analysis-analysis-completed","kind":"Event","title":"analysis.completed","description":"Application-owned analysis run fact emitted after complete_analysis reaches ready.","href":"/events/governed-spatial-analysis-analysis-completed","eyebrow":"hybrid · analysis run · v1","keywords":"Analysis Completed governed-spatial-analysis Governed spatial analysis gis-analytics complete_analysis Spatial processing service processing ready outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-analysis-share-created","kind":"Event","title":"share.created","description":"Application-owned analysis run fact emitted after create_share reaches shared.","href":"/events/governed-spatial-analysis-share-created","eyebrow":"hybrid · analysis run · v1","keywords":"Share Created governed-spatial-analysis Governed spatial analysis gis-analytics create_share Workspace administrator ready shared outbox idempotency replay deduplication event schema"},{"id":"event:durable-weekend-itinerary-trip-created","kind":"Event","title":"trip.created","description":"Application-owned trip itinerary fact emitted after create_trip reaches draft.","href":"/events/durable-weekend-itinerary-trip-created","eyebrow":"hybrid · trip itinerary · v1","keywords":"Trip Created durable-weekend-itinerary Durable multi-stop itinerary routes-navigation create_trip Traveller  draft outbox idempotency replay deduplication event schema"},{"id":"event:durable-weekend-itinerary-trip-sequence-changed","kind":"Event","title":"trip.sequence_changed","description":"Application-owned trip itinerary fact emitted after add_or_reorder_stop reaches draft.","href":"/events/durable-weekend-itinerary-trip-sequence-changed","eyebrow":"hybrid · trip itinerary · v1","keywords":"Trip Sequence Changed durable-weekend-itinerary Durable multi-stop itinerary routes-navigation add_or_reorder_stop Traveller draft planned draft outbox idempotency replay deduplication event schema"},{"id":"event:durable-weekend-itinerary-trip-route-previewed","kind":"Event","title":"trip.route_previewed","description":"Application-owned trip itinerary fact emitted after preview_route reaches planned.","href":"/events/durable-weekend-itinerary-trip-route-previewed","eyebrow":"hybrid · trip itinerary · v1","keywords":"Trip Route Previewed durable-weekend-itinerary Durable multi-stop itinerary routes-navigation preview_route Mappls routing service draft planned outbox idempotency replay deduplication event schema"},{"id":"event:durable-weekend-itinerary-trip-started","kind":"Event","title":"trip.started","description":"Application-owned trip itinerary fact emitted after start_trip reaches active.","href":"/events/durable-weekend-itinerary-trip-started","eyebrow":"hybrid · trip itinerary · v1","keywords":"Trip Started durable-weekend-itinerary Durable multi-stop itinerary routes-navigation start_trip Traveller planned active outbox idempotency replay deduplication event schema"},{"id":"event:durable-weekend-itinerary-trip-paused","kind":"Event","title":"trip.paused","description":"Application-owned trip itinerary fact emitted after pause_trip reaches paused.","href":"/events/durable-weekend-itinerary-trip-paused","eyebrow":"hybrid · trip itinerary · v1","keywords":"Trip Paused durable-weekend-itinerary Durable multi-stop itinerary routes-navigation pause_trip Traveller active paused outbox idempotency replay deduplication event schema"},{"id":"event:durable-weekend-itinerary-trip-resumed","kind":"Event","title":"trip.resumed","description":"Application-owned trip itinerary fact emitted after resume_trip reaches active.","href":"/events/durable-weekend-itinerary-trip-resumed","eyebrow":"hybrid · trip itinerary · v1","keywords":"Trip Resumed durable-weekend-itinerary Durable multi-stop itinerary routes-navigation resume_trip Traveller paused active outbox idempotency replay deduplication event schema"},{"id":"event:durable-weekend-itinerary-trip-stop-completed","kind":"Event","title":"trip.stop_completed","description":"Application-owned trip itinerary fact emitted after visit_or_skip_next reaches active.","href":"/events/durable-weekend-itinerary-trip-stop-completed","eyebrow":"hybrid · trip itinerary · v1","keywords":"Trip Stop Completed durable-weekend-itinerary Durable multi-stop itinerary routes-navigation visit_or_skip_next Traveller active active outbox idempotency replay deduplication event schema"},{"id":"event:durable-weekend-itinerary-trip-completed","kind":"Event","title":"trip.completed","description":"Application-owned trip itinerary fact emitted after complete_trip reaches completed.","href":"/events/durable-weekend-itinerary-trip-completed","eyebrow":"hybrid · trip itinerary · v1","keywords":"Trip Completed durable-weekend-itinerary Durable multi-stop itinerary routes-navigation complete_trip Traveller active completed outbox idempotency replay deduplication event schema"},{"id":"event:durable-weekend-itinerary-trip-cancelled","kind":"Event","title":"trip.cancelled","description":"Application-owned trip itinerary fact emitted after cancel_trip reaches cancelled.","href":"/events/durable-weekend-itinerary-trip-cancelled","eyebrow":"hybrid · trip itinerary · v1","keywords":"Trip Cancelled durable-weekend-itinerary Durable multi-stop itinerary routes-navigation cancel_trip Traveller draft planned active paused cancelled outbox idempotency replay deduplication event schema"},{"id":"event:consented-address-verification-address-verification-entered","kind":"Event","title":"address_verification.entered","description":"Application-owned address verification fact emitted after enter_verification reaches entered.","href":"/events/consented-address-verification-address-verification-entered","eyebrow":"stateful · address verification · v1","keywords":"Address Verification Entered consented-address-verification Consented address verification search-places enter_verification Application user  entered outbox idempotency replay deduplication event schema"},{"id":"event:consented-address-verification-address-verification-normalized","kind":"Event","title":"address_verification.normalized","description":"Application-owned address verification fact emitted after normalize_address reaches normalized.","href":"/events/consented-address-verification-address-verification-normalized","eyebrow":"stateful · address verification · v1","keywords":"Address Verification Normalized consented-address-verification Consented address verification search-places normalize_address Policy service entered normalized outbox idempotency replay deduplication event schema"},{"id":"event:consented-address-verification-address-verification-capture-authorized","kind":"Event","title":"address_verification.capture_authorized","description":"Application-owned address verification fact emitted after authorize_capture reaches capture_authorized.","href":"/events/consented-address-verification-address-verification-capture-authorized","eyebrow":"stateful · address verification · v1","keywords":"Address Verification Capture Authorized consented-address-verification Consented address verification search-places authorize_capture Application user normalized capture_authorized outbox idempotency replay deduplication event schema"},{"id":"event:consented-address-verification-address-verification-consent-revoked","kind":"Event","title":"address_verification.consent_revoked","description":"Application-owned address verification fact emitted after revoke_consent reaches cancelled.","href":"/events/consented-address-verification-address-verification-consent-revoked","eyebrow":"stateful · address verification · v1","keywords":"Address Verification Consent Revoked consented-address-verification Consented address verification search-places revoke_consent Application user capture_authorized cancelled outbox idempotency replay deduplication event schema"},{"id":"event:consented-address-verification-address-verification-evidence-captured","kind":"Event","title":"address_verification.evidence_captured","description":"Application-owned address verification fact emitted after capture_evidence reaches evidence_captured.","href":"/events/consented-address-verification-address-verification-evidence-captured","eyebrow":"stateful · address verification · v1","keywords":"Address Verification Evidence Captured consented-address-verification Consented address verification search-places capture_evidence Evidence capture application capture_authorized evidence_captured outbox idempotency replay deduplication event schema"},{"id":"event:consented-address-verification-address-verification-compared","kind":"Event","title":"address_verification.compared","description":"Application-owned address verification fact emitted after compare reaches compared.","href":"/events/consented-address-verification-address-verification-compared","eyebrow":"stateful · address verification · v1","keywords":"Address Verification Compared consented-address-verification Consented address verification search-places compare Policy service evidence_captured compared outbox idempotency replay deduplication event schema"},{"id":"event:consented-address-verification-address-verification-verified","kind":"Event","title":"address_verification.verified","description":"Application-owned address verification fact emitted after verify or review_verify reaches verified.","href":"/events/consented-address-verification-address-verification-verified","eyebrow":"stateful · address verification · v1","keywords":"Address Verification Verified consented-address-verification Consented address verification search-places verify Policy service compared verified review_verify Human reviewer review_required verified outbox idempotency replay deduplication event schema"},{"id":"event:consented-address-verification-address-verification-rejected","kind":"Event","title":"address_verification.rejected","description":"Application-owned address verification fact emitted after reject or review_reject reaches rejected.","href":"/events/consented-address-verification-address-verification-rejected","eyebrow":"stateful · address verification · v1","keywords":"Address Verification Rejected consented-address-verification Consented address verification search-places reject Policy service compared rejected review_reject Human reviewer review_required rejected outbox idempotency replay deduplication event schema"},{"id":"event:consented-address-verification-address-verification-review-required","kind":"Event","title":"address_verification.review_required","description":"Application-owned address verification fact emitted after defer reaches review_required.","href":"/events/consented-address-verification-address-verification-review-required","eyebrow":"stateful · address verification · v1","keywords":"Address Verification Review Required consented-address-verification Consented address verification search-places defer Policy service compared review_required outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-agent-run-agent-question-received","kind":"Event","title":"agent.question_received","description":"Application-owned agent run fact emitted after ask reaches asked.","href":"/events/governed-spatial-agent-run-agent-question-received","eyebrow":"stateful · agent run · v1","keywords":"Agent Question Received governed-spatial-agent-run Governed spatial agent run ai-location ask Application user  asked outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-agent-run-agent-plan-created","kind":"Event","title":"agent.plan_created","description":"Application-owned agent run fact emitted after create_plan reaches planned.","href":"/events/governed-spatial-agent-run-agent-plan-created","eyebrow":"stateful · agent run · v1","keywords":"Agent Plan Created governed-spatial-agent-run Governed spatial agent run ai-location create_plan Agent planner asked planned outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-agent-run-agent-plan-approved","kind":"Event","title":"agent.plan_approved","description":"Application-owned agent run fact emitted after approve_plan reaches approved.","href":"/events/governed-spatial-agent-run-agent-plan-approved","eyebrow":"stateful · agent run · v1","keywords":"Agent Plan Approved governed-spatial-agent-run Governed spatial agent run ai-location approve_plan Human approver planned approved outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-agent-run-agent-plan-rejected","kind":"Event","title":"agent.plan_rejected","description":"Application-owned agent run fact emitted after reject_plan reaches rejected.","href":"/events/governed-spatial-agent-run-agent-plan-rejected","eyebrow":"stateful · agent run · v1","keywords":"Agent Plan Rejected governed-spatial-agent-run Governed spatial agent run ai-location reject_plan Human approver planned rejected outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-agent-run-agent-execution-started","kind":"Event","title":"agent.execution_started","description":"Application-owned agent run fact emitted after start_execution reaches executing.","href":"/events/governed-spatial-agent-run-agent-execution-started","eyebrow":"stateful · agent run · v1","keywords":"Agent Execution Started governed-spatial-agent-run Governed spatial agent run ai-location start_execution Execution service approved executing outbox idempotency replay deduplication event schema"},{"id":"event:governed-spatial-agent-run-agent-execution-completed","kind":"Event","title":"agent.execution_completed","description":"Application-owned agent run fact emitted after complete_execution reaches completed.","href":"/events/governed-spatial-agent-run-agent-execution-completed","eyebrow":"stateful · agent run · v1","keywords":"Agent Execution Completed governed-spatial-agent-run Governed spatial agent run ai-location complete_execution Execution service executing completed outbox idempotency replay deduplication event schema"},{"id":"event:offline-automotive-release-device-registered","kind":"Event","title":"device.registered","description":"Application-owned device release fact emitted after register_device reaches manufactured.","href":"/events/offline-automotive-release-device-registered","eyebrow":"stateful · device release · v1","keywords":"Device Registered offline-automotive-release Offline automotive release offline-automotive register_device Manufacturing system  manufactured outbox idempotency replay deduplication event schema"},{"id":"event:offline-automotive-release-license-activated","kind":"Event","title":"license.activated","description":"Application-owned device release fact emitted after activate reaches activated.","href":"/events/offline-automotive-release-license-activated","eyebrow":"stateful · device release · v1","keywords":"License Activated offline-automotive-release Offline automotive release offline-automotive activate Fleet release manager manufactured activated outbox idempotency replay deduplication event schema"},{"id":"event:offline-automotive-release-release-installed","kind":"Event","title":"release.installed","description":"Application-owned device release fact emitted after stage_base_release reaches installed.","href":"/events/offline-automotive-release-release-installed","eyebrow":"stateful · device release · v1","keywords":"Release Installed offline-automotive-release Offline automotive release offline-automotive stage_base_release Vehicle runtime activated installed outbox idempotency replay deduplication event schema"},{"id":"event:offline-automotive-release-release-qualified","kind":"Event","title":"release.qualified","description":"Application-owned device release fact emitted after qualify reaches operational.","href":"/events/offline-automotive-release-release-qualified","eyebrow":"stateful · device release · v1","keywords":"Release Qualified offline-automotive-release Offline automotive release offline-automotive qualify Vehicle runtime installed recovering operational outbox idempotency replay deduplication event schema"},{"id":"event:offline-automotive-release-release-update-started","kind":"Event","title":"release.update_started","description":"Application-owned device release fact emitted after start_update reaches updating.","href":"/events/offline-automotive-release-release-update-started","eyebrow":"stateful · device release · v1","keywords":"Release Update Started offline-automotive-release Offline automotive release offline-automotive start_update Fleet release manager operational updating outbox idempotency replay deduplication event schema"},{"id":"event:offline-automotive-release-release-rollback-started","kind":"Event","title":"release.rollback_started","description":"Application-owned device release fact emitted after rollback reaches recovering.","href":"/events/offline-automotive-release-release-rollback-started","eyebrow":"stateful · device release · v1","keywords":"Release Rollback Started offline-automotive-release Offline automotive release offline-automotive rollback Vehicle runtime updating operational recovering outbox idempotency replay deduplication event schema"},{"id":"event:offline-automotive-release-device-retired","kind":"Event","title":"device.retired","description":"Application-owned device release fact emitted after retire reaches retired.","href":"/events/offline-automotive-release-device-retired","eyebrow":"stateful · device release · v1","keywords":"Device Retired offline-automotive-release Offline automotive release offline-automotive retire Fleet release manager manufactured activated installed operational recovering retired outbox idempotency replay deduplication event schema"},{"id":"event:widget-selection-session-host-session-created","kind":"Event","title":"host.session_created","description":"Application-owned widget selection session fact emitted after create_session reaches draft.","href":"/events/widget-selection-session-host-session-created","eyebrow":"hybrid · widget selection session · v1","keywords":"Host Session Created widget-selection-session Application-owned widget selection app-widgets-deep-links create_session Host application  draft outbox idempotency replay deduplication event schema"},{"id":"event:widget-selection-session-widget-opened","kind":"Event","title":"widget.opened","description":"Application-owned widget selection session fact emitted after open_widget reaches widget_open.","href":"/events/widget-selection-session-widget-opened","eyebrow":"hybrid · widget selection session · v1","keywords":"Widget Opened widget-selection-session Application-owned widget selection app-widgets-deep-links open_widget Application user draft fallback_active widget_open outbox idempotency replay deduplication event schema"},{"id":"event:widget-selection-session-widget-fallback-activated","kind":"Event","title":"widget.fallback_activated","description":"Application-owned widget selection session fact emitted after activate_fallback reaches fallback_active.","href":"/events/widget-selection-session-widget-fallback-activated","eyebrow":"hybrid · widget selection session · v1","keywords":"Widget Fallback Activated widget-selection-session Application-owned widget selection app-widgets-deep-links activate_fallback Platform adapter widget_open fallback_active outbox idempotency replay deduplication event schema"},{"id":"event:widget-selection-session-location-candidate-received","kind":"Event","title":"location.candidate_received","description":"Application-owned widget selection session fact emitted after receive_candidate reaches candidate_received.","href":"/events/widget-selection-session-location-candidate-received","eyebrow":"hybrid · widget selection session · v1","keywords":"Location Candidate Received widget-selection-session Application-owned widget selection app-widgets-deep-links receive_candidate Platform adapter widget_open fallback_active candidate_received outbox idempotency replay deduplication event schema"},{"id":"event:widget-selection-session-location-selected","kind":"Event","title":"location.selected","description":"Application-owned widget selection session fact emitted after accept_selection reaches selected.","href":"/events/widget-selection-session-location-selected","eyebrow":"hybrid · widget selection session · v1","keywords":"Location Selected widget-selection-session Application-owned widget selection app-widgets-deep-links accept_selection Application user candidate_received selected outbox idempotency replay deduplication event schema"},{"id":"event:widget-selection-session-host-text-edited","kind":"Event","title":"host.text_edited","description":"Application-owned widget selection session fact emitted after edit_host_text reaches draft.","href":"/events/widget-selection-session-host-text-edited","eyebrow":"hybrid · widget selection session · v1","keywords":"Host Text Edited widget-selection-session Application-owned widget selection app-widgets-deep-links edit_host_text Application user draft widget_open fallback_active candidate_received selected draft outbox idempotency replay deduplication event schema"},{"id":"event:widget-selection-session-host-submitted","kind":"Event","title":"host.submitted","description":"Application-owned widget selection session fact emitted after submit reaches submitted.","href":"/events/widget-selection-session-host-submitted","eyebrow":"hybrid · widget selection session · v1","keywords":"Host Submitted widget-selection-session Application-owned widget selection app-widgets-deep-links submit Application user selected submitted outbox idempotency replay deduplication event schema"},{"id":"event:widget-selection-session-host-cancelled","kind":"Event","title":"host.cancelled","description":"Application-owned widget selection session fact emitted after cancel reaches cancelled.","href":"/events/widget-selection-session-host-cancelled","eyebrow":"hybrid · widget selection session · v1","keywords":"Host Cancelled widget-selection-session Application-owned widget selection app-widgets-deep-links cancel Application user draft widget_open fallback_active candidate_received selected cancelled outbox idempotency replay deduplication event schema"},{"id":"event:ios-direction-planning-handoff-route-plan-created","kind":"Event","title":"route_plan.created","description":"Application-owned route planning session fact emitted after create_plan reaches draft.","href":"/events/ios-direction-planning-handoff-route-plan-created","eyebrow":"hybrid · route planning session · v1","keywords":"Route Plan Created ios-direction-planning-handoff iOS direction planning and navigation handoff routes-navigation create_plan Host application  draft outbox idempotency replay deduplication event schema"},{"id":"event:ios-direction-planning-handoff-route-plan-editor-opened","kind":"Event","title":"route_plan.editor_opened","description":"Application-owned route planning session fact emitted after open_direction_ui reaches editing.","href":"/events/ios-direction-planning-handoff-route-plan-editor-opened","eyebrow":"hybrid · route planning session · v1","keywords":"Route Plan Editor Opened ios-direction-planning-handoff iOS direction planning and navigation handoff routes-navigation open_direction_ui Traveler draft selected editing outbox idempotency replay deduplication event schema"},{"id":"event:ios-direction-planning-handoff-route-plan-calculation-requested","kind":"Event","title":"route_plan.calculation_requested","description":"Application-owned route planning session fact emitted after request_routes reaches calculating.","href":"/events/ios-direction-planning-handoff-route-plan-calculation-requested","eyebrow":"hybrid · route planning session · v1","keywords":"Route Plan Calculation Requested ios-direction-planning-handoff iOS direction planning and navigation handoff routes-navigation request_routes Traveler editing calculating outbox idempotency replay deduplication event schema"},{"id":"event:ios-direction-planning-handoff-route-plan-candidates-received","kind":"Event","title":"route_plan.candidates_received","description":"Application-owned route planning session fact emitted after receive_routes reaches candidates_ready.","href":"/events/ios-direction-planning-handoff-route-plan-candidates-received","eyebrow":"hybrid · route planning session · v1","keywords":"Route Plan Candidates Received ios-direction-planning-handoff iOS direction planning and navigation handoff routes-navigation receive_routes MapplsDirectionUI calculating candidates_ready outbox idempotency replay deduplication event schema"},{"id":"event:ios-direction-planning-handoff-route-plan-route-selected","kind":"Event","title":"route_plan.route_selected","description":"Application-owned route planning session fact emitted after select_route reaches selected.","href":"/events/ios-direction-planning-handoff-route-plan-route-selected","eyebrow":"hybrid · route planning session · v1","keywords":"Route Plan Route Selected ios-direction-planning-handoff iOS direction planning and navigation handoff routes-navigation select_route Traveler candidates_ready selected outbox idempotency replay deduplication event schema"},{"id":"event:ios-direction-planning-handoff-route-plan-navigation-requested","kind":"Event","title":"route_plan.navigation_requested","description":"Application-owned route planning session fact emitted after request_navigation reaches handoff_pending.","href":"/events/ios-direction-planning-handoff-route-plan-navigation-requested","eyebrow":"hybrid · route planning session · v1","keywords":"Route Plan Navigation Requested ios-direction-planning-handoff iOS direction planning and navigation handoff routes-navigation request_navigation Traveler selected candidates_ready handoff_pending outbox idempotency replay deduplication event schema"},{"id":"event:ios-direction-planning-handoff-route-plan-navigation-handed-off","kind":"Event","title":"route_plan.navigation_handed_off","description":"Application-owned route planning session fact emitted after confirm_handoff reaches handed_off.","href":"/events/ios-direction-planning-handoff-route-plan-navigation-handed-off","eyebrow":"hybrid · route planning session · v1","keywords":"Route Plan Navigation Handed Off ios-direction-planning-handoff iOS direction planning and navigation handoff routes-navigation confirm_handoff Navigation adapter handoff_pending handed_off outbox idempotency replay deduplication event schema"},{"id":"event:ios-direction-planning-handoff-route-plan-cancelled","kind":"Event","title":"route_plan.cancelled","description":"Application-owned route planning session fact emitted after cancel_plan reaches cancelled.","href":"/events/ios-direction-planning-handoff-route-plan-cancelled","eyebrow":"hybrid · route planning session · v1","keywords":"Route Plan Cancelled ios-direction-planning-handoff iOS direction planning and navigation handoff routes-navigation cancel_plan Traveler draft editing calculating candidates_ready selected handoff_pending cancelled outbox idempotency replay deduplication event schema"},{"id":"event:ios-geofence-draft-geofence-draft-created","kind":"Event","title":"geofence_draft.created","description":"Application-owned geofence draft fact emitted after create_geofence_draft reaches draft.","href":"/events/ios-geofence-draft-geofence-draft-created","eyebrow":"hybrid · geofence draft · v1","keywords":"Geofence Draft Created ios-geofence-draft iOS geofence draft and publication boundary intouch-telematics create_geofence_draft Host application  draft outbox idempotency replay deduplication event schema"},{"id":"event:ios-geofence-draft-geofence-draft-editor-opened","kind":"Event","title":"geofence_draft.editor_opened","description":"Application-owned geofence draft fact emitted after open_editor reaches editing.","href":"/events/ios-geofence-draft-geofence-draft-editor-opened","eyebrow":"hybrid · geofence draft · v1","keywords":"Geofence Draft Editor Opened ios-geofence-draft iOS geofence draft and publication boundary intouch-telematics open_editor Operations author draft review_pending editing outbox idempotency replay deduplication event schema"},{"id":"event:ios-geofence-draft-geofence-draft-geometry-received","kind":"Event","title":"geofence_draft.geometry_received","description":"Application-owned geofence draft fact emitted after receive_geometry reaches candidate.","href":"/events/ios-geofence-draft-geofence-draft-geometry-received","eyebrow":"hybrid · geofence draft · v1","keywords":"Geofence Draft Geometry Received ios-geofence-draft iOS geofence draft and publication boundary intouch-telematics receive_geometry MapplsGeofenceUI editing candidate outbox idempotency replay deduplication event schema"},{"id":"event:ios-geofence-draft-geofence-draft-review-requested","kind":"Event","title":"geofence_draft.review_requested","description":"Application-owned geofence draft fact emitted after submit_for_review reaches review_pending.","href":"/events/ios-geofence-draft-geofence-draft-review-requested","eyebrow":"hybrid · geofence draft · v1","keywords":"Geofence Draft Review Requested ios-geofence-draft iOS geofence draft and publication boundary intouch-telematics submit_for_review Operations author candidate review_pending outbox idempotency replay deduplication event schema"},{"id":"event:ios-geofence-draft-geofence-draft-approved","kind":"Event","title":"geofence_draft.approved","description":"Application-owned geofence draft fact emitted after approve_draft reaches approved_draft.","href":"/events/ios-geofence-draft-geofence-draft-approved","eyebrow":"hybrid · geofence draft · v1","keywords":"Geofence Draft Approved ios-geofence-draft iOS geofence draft and publication boundary intouch-telematics approve_draft Geofence reviewer review_pending approved_draft outbox idempotency replay deduplication event schema"},{"id":"event:ios-geofence-draft-geofence-draft-cancelled","kind":"Event","title":"geofence_draft.cancelled","description":"Application-owned geofence draft fact emitted after cancel_edit reaches cancelled.","href":"/events/ios-geofence-draft-geofence-draft-cancelled","eyebrow":"hybrid · geofence draft · v1","keywords":"Geofence Draft Cancelled ios-geofence-draft iOS geofence draft and publication boundary intouch-telematics cancel_edit Operations author draft editing candidate review_pending cancelled outbox idempotency replay deduplication event schema"},{"id":"event:ios-feedback-report-review-feedback-report-created","kind":"Event","title":"feedback_report.created","description":"Application-owned feedback report fact emitted after create_report reaches draft.","href":"/events/ios-feedback-report-review-feedback-report-created","eyebrow":"hybrid · feedback report · v1","keywords":"Feedback Report Created ios-feedback-report-review iOS feedback report and review capture-feedback create_report Host application  draft outbox idempotency replay deduplication event schema"},{"id":"event:ios-feedback-report-review-feedback-report-ui-opened","kind":"Event","title":"feedback_report.ui_opened","description":"Application-owned feedback report fact emitted after open_feedback_ui reaches capturing.","href":"/events/ios-feedback-report-review-feedback-report-ui-opened","eyebrow":"hybrid · feedback report · v1","keywords":"Feedback Report Ui Opened ios-feedback-report-review iOS feedback report and review capture-feedback open_feedback_ui Contributor draft capturing outbox idempotency replay deduplication event schema"},{"id":"event:ios-feedback-report-review-feedback-report-candidate-received","kind":"Event","title":"feedback_report.candidate_received","description":"Application-owned feedback report fact emitted after receive_candidate reaches candidate.","href":"/events/ios-feedback-report-review-feedback-report-candidate-received","eyebrow":"hybrid · feedback report · v1","keywords":"Feedback Report Candidate Received ios-feedback-report-review iOS feedback report and review capture-feedback receive_candidate Mappls Feedback Kit capturing candidate outbox idempotency replay deduplication event schema"},{"id":"event:ios-feedback-report-review-feedback-report-submitted","kind":"Event","title":"feedback_report.submitted","description":"Application-owned feedback report fact emitted after commit_submission reaches submitted.","href":"/events/ios-feedback-report-review-feedback-report-submitted","eyebrow":"hybrid · feedback report · v1","keywords":"Feedback Report Submitted ios-feedback-report-review iOS feedback report and review capture-feedback commit_submission Contributor candidate submitted outbox idempotency replay deduplication event schema"},{"id":"event:ios-feedback-report-review-feedback-report-provider-requested","kind":"Event","title":"feedback_report.provider_requested","description":"Application-owned feedback report fact emitted after request_provider_submission reaches provider_pending.","href":"/events/ios-feedback-report-review-feedback-report-provider-requested","eyebrow":"hybrid · feedback report · v1","keywords":"Feedback Report Provider Requested ios-feedback-report-review iOS feedback report and review capture-feedback request_provider_submission Provider adapter submitted provider_pending outbox idempotency replay deduplication event schema"},{"id":"event:ios-feedback-report-review-feedback-report-review-queued","kind":"Event","title":"feedback_report.review_queued","description":"Application-owned feedback report fact emitted after queue_review reaches review_pending.","href":"/events/ios-feedback-report-review-feedback-report-review-queued","eyebrow":"hybrid · feedback report · v1","keywords":"Feedback Report Review Queued ios-feedback-report-review iOS feedback report and review capture-feedback queue_review Host application submitted provider_pending review_pending outbox idempotency replay deduplication event schema"},{"id":"event:ios-feedback-report-review-feedback-report-resolved","kind":"Event","title":"feedback_report.resolved","description":"Application-owned feedback report fact emitted after resolve_report reaches resolved.","href":"/events/ios-feedback-report-review-feedback-report-resolved","eyebrow":"hybrid · feedback report · v1","keywords":"Feedback Report Resolved ios-feedback-report-review iOS feedback report and review capture-feedback resolve_report Operations reviewer review_pending resolved outbox idempotency replay deduplication event schema"},{"id":"event:ios-feedback-report-review-feedback-report-rejected","kind":"Event","title":"feedback_report.rejected","description":"Application-owned feedback report fact emitted after reject_report reaches rejected.","href":"/events/ios-feedback-report-review-feedback-report-rejected","eyebrow":"hybrid · feedback report · v1","keywords":"Feedback Report Rejected ios-feedback-report-review iOS feedback report and review capture-feedback reject_report Operations reviewer review_pending rejected outbox idempotency replay deduplication event schema"},{"id":"event:ios-feedback-report-review-feedback-report-cancelled","kind":"Event","title":"feedback_report.cancelled","description":"Application-owned feedback report fact emitted after cancel_report reaches cancelled.","href":"/events/ios-feedback-report-review-feedback-report-cancelled","eyebrow":"hybrid · feedback report · v1","keywords":"Feedback Report Cancelled ios-feedback-report-review iOS feedback report and review capture-feedback cancel_report Contributor draft capturing candidate cancelled outbox idempotency replay deduplication event schema"},{"id":"event:location-capture-evidence-location-capture-attempt-created","kind":"Event","title":"location_capture.attempt_created","description":"Application-owned location capture attempt fact emitted after create_attempt reaches draft.","href":"/events/location-capture-evidence-location-capture-attempt-created","eyebrow":"hybrid · location capture attempt · v1","keywords":"Location Capture Attempt Created location-capture-evidence Consent-bound location capture evidence capture-feedback create_attempt Host application  draft outbox idempotency replay deduplication event schema"},{"id":"event:location-capture-evidence-location-capture-permission-requested","kind":"Event","title":"location_capture.permission_requested","description":"Application-owned location capture attempt fact emitted after request_permission reaches permission_pending.","href":"/events/location-capture-evidence-location-capture-permission-requested","eyebrow":"hybrid · location capture attempt · v1","keywords":"Location Capture Permission Requested location-capture-evidence Consent-bound location capture evidence capture-feedback request_permission Application user draft permission_pending outbox idempotency replay deduplication event schema"},{"id":"event:location-capture-evidence-location-capture-sdk-ready","kind":"Event","title":"location_capture.sdk_ready","description":"Application-owned location capture attempt fact emitted after prepare_sdk reaches ready.","href":"/events/location-capture-evidence-location-capture-sdk-ready","eyebrow":"hybrid · location capture attempt · v1","keywords":"Location Capture Sdk Ready location-capture-evidence Consent-bound location capture evidence capture-feedback prepare_sdk Platform adapter permission_pending ready outbox idempotency replay deduplication event schema"},{"id":"event:location-capture-evidence-location-capture-acquisition-started","kind":"Event","title":"location_capture.acquisition_started","description":"Application-owned location capture attempt fact emitted after start_acquisition reaches acquiring.","href":"/events/location-capture-evidence-location-capture-acquisition-started","eyebrow":"hybrid · location capture attempt · v1","keywords":"Location Capture Acquisition Started location-capture-evidence Consent-bound location capture evidence capture-feedback start_acquisition Application user ready review_pending acquiring outbox idempotency replay deduplication event schema"},{"id":"event:location-capture-evidence-location-capture-candidate-received","kind":"Event","title":"location_capture.candidate_received","description":"Application-owned location capture attempt fact emitted after receive_location reaches candidate.","href":"/events/location-capture-evidence-location-capture-candidate-received","eyebrow":"hybrid · location capture attempt · v1","keywords":"Location Capture Candidate Received location-capture-evidence Consent-bound location capture evidence capture-feedback receive_location Platform adapter acquiring candidate outbox idempotency replay deduplication event schema"},{"id":"event:location-capture-evidence-location-capture-review-queued","kind":"Event","title":"location_capture.review_queued","description":"Application-owned location capture attempt fact emitted after queue_review reaches review_pending.","href":"/events/location-capture-evidence-location-capture-review-queued","eyebrow":"hybrid · location capture attempt · v1","keywords":"Location Capture Review Queued location-capture-evidence Consent-bound location capture evidence capture-feedback queue_review Host application candidate review_pending outbox idempotency replay deduplication event schema"},{"id":"event:location-capture-evidence-location-capture-evidence-accepted","kind":"Event","title":"location_capture.evidence_accepted","description":"Application-owned location capture attempt fact emitted after accept_evidence reaches accepted.","href":"/events/location-capture-evidence-location-capture-evidence-accepted","eyebrow":"hybrid · location capture attempt · v1","keywords":"Location Capture Evidence Accepted location-capture-evidence Consent-bound location capture evidence capture-feedback accept_evidence Application user candidate accepted outbox idempotency replay deduplication event schema"},{"id":"event:location-capture-evidence-location-capture-weak-evidence-approved","kind":"Event","title":"location_capture.weak_evidence_approved","description":"Application-owned location capture attempt fact emitted after approve_weak_evidence reaches accepted.","href":"/events/location-capture-evidence-location-capture-weak-evidence-approved","eyebrow":"hybrid · location capture attempt · v1","keywords":"Location Capture Weak Evidence Approved location-capture-evidence Consent-bound location capture evidence capture-feedback approve_weak_evidence Evidence reviewer review_pending accepted outbox idempotency replay deduplication event schema"},{"id":"event:location-capture-evidence-location-capture-attempt-cancelled","kind":"Event","title":"location_capture.attempt_cancelled","description":"Application-owned location capture attempt fact emitted after cancel_attempt reaches cancelled.","href":"/events/location-capture-evidence-location-capture-attempt-cancelled","eyebrow":"hybrid · location capture attempt · v1","keywords":"Location Capture Attempt Cancelled location-capture-evidence Consent-bound location capture evidence capture-feedback cancel_attempt Application user draft permission_pending ready acquiring candidate review_pending cancelled outbox idempotency replay deduplication event schema"},{"id":"event:place-contribution-publication-place-contribution-created","kind":"Event","title":"place_contribution.created","description":"Application-owned place contribution fact emitted after create_contribution reaches draft.","href":"/events/place-contribution-publication-place-contribution-created","eyebrow":"stateful · place contribution · v1","keywords":"Place Contribution Created place-contribution-publication Governed place contribution and publication capture-feedback create_contribution Host application  draft outbox idempotency replay deduplication event schema"},{"id":"event:place-contribution-publication-place-contribution-widget-opened","kind":"Event","title":"place_contribution.widget_opened","description":"Application-owned place contribution fact emitted after open_widget reaches widget_open.","href":"/events/place-contribution-publication-place-contribution-widget-opened","eyebrow":"stateful · place contribution · v1","keywords":"Place Contribution Widget Opened place-contribution-publication Governed place contribution and publication capture-feedback open_widget Contributor draft widget_open outbox idempotency replay deduplication event schema"},{"id":"event:place-contribution-publication-place-contribution-submission-reported","kind":"Event","title":"place_contribution.submission_reported","description":"Application-owned place contribution fact emitted after report_submission reaches submission_reported.","href":"/events/place-contribution-publication-place-contribution-submission-reported","eyebrow":"stateful · place contribution · v1","keywords":"Place Contribution Submission Reported place-contribution-publication Governed place contribution and publication capture-feedback report_submission Contributor widget_open submission_reported outbox idempotency replay deduplication event schema"},{"id":"event:place-contribution-publication-place-contribution-reconciliation-queued","kind":"Event","title":"place_contribution.reconciliation_queued","description":"Application-owned place contribution fact emitted after queue_reconciliation reaches publication_pending.","href":"/events/place-contribution-publication-place-contribution-reconciliation-queued","eyebrow":"stateful · place contribution · v1","keywords":"Place Contribution Reconciliation Queued place-contribution-publication Governed place contribution and publication capture-feedback queue_reconciliation Host application submission_reported publication_pending outbox idempotency replay deduplication event schema"},{"id":"event:place-contribution-publication-place-contribution-published","kind":"Event","title":"place_contribution.published","description":"Application-owned place contribution fact emitted after confirm_publication reaches published.","href":"/events/place-contribution-publication-place-contribution-published","eyebrow":"stateful · place contribution · v1","keywords":"Place Contribution Published place-contribution-publication Governed place contribution and publication capture-feedback confirm_publication Operations reviewer submission_reported publication_pending published outbox idempotency replay deduplication event schema"},{"id":"event:place-contribution-publication-place-contribution-rejected","kind":"Event","title":"place_contribution.rejected","description":"Application-owned place contribution fact emitted after reject reaches rejected.","href":"/events/place-contribution-publication-place-contribution-rejected","eyebrow":"stateful · place contribution · v1","keywords":"Place Contribution Rejected place-contribution-publication Governed place contribution and publication capture-feedback reject Operations reviewer submission_reported publication_pending rejected outbox idempotency replay deduplication event schema"},{"id":"event:place-contribution-publication-place-contribution-retried","kind":"Event","title":"place_contribution.retried","description":"Application-owned place contribution fact emitted after retry reaches widget_open.","href":"/events/place-contribution-publication-place-contribution-retried","eyebrow":"stateful · place contribution · v1","keywords":"Place Contribution Retried place-contribution-publication Governed place contribution and publication capture-feedback retry Contributor rejected widget_open outbox idempotency replay deduplication event schema"},{"id":"event:place-contribution-publication-place-contribution-withdrawn","kind":"Event","title":"place_contribution.withdrawn","description":"Application-owned place contribution fact emitted after withdraw reaches withdrawn.","href":"/events/place-contribution-publication-place-contribution-withdrawn","eyebrow":"stateful · place contribution · v1","keywords":"Place Contribution Withdrawn place-contribution-publication Governed place contribution and publication capture-feedback withdraw Contributor draft widget_open submission_reported publication_pending withdrawn outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-created","kind":"Event","title":"realview_inspection.created","description":"Application-owned remote visual inspection fact emitted after create_inspection reaches draft.","href":"/events/realview-remote-inspection-realview-inspection-created","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Created realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links create_inspection Host application  draft outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-entitlement-requested","kind":"Event","title":"realview_inspection.entitlement_requested","description":"Application-owned remote visual inspection fact emitted after request_entitlement reaches entitlement_pending.","href":"/events/realview-remote-inspection-realview-inspection-entitlement-requested","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Entitlement Requested realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links request_entitlement Inspector draft entitlement_pending outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-entitlement-confirmed","kind":"Event","title":"realview_inspection.entitlement_confirmed","description":"Application-owned remote visual inspection fact emitted after confirm_entitlement reaches ready.","href":"/events/realview-remote-inspection-realview-inspection-entitlement-confirmed","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Entitlement Confirmed realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links confirm_entitlement Platform administrator entitlement_pending ready outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-viewer-opened","kind":"Event","title":"realview_inspection.viewer_opened","description":"Application-owned remote visual inspection fact emitted after open_viewer reaches viewing.","href":"/events/realview-remote-inspection-realview-inspection-viewer-opened","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Viewer Opened realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links open_viewer Inspector ready coverage_unavailable rework_required viewing outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-coverage-unavailable","kind":"Event","title":"realview_inspection.coverage_unavailable","description":"Application-owned remote visual inspection fact emitted after record_no_coverage reaches coverage_unavailable.","href":"/events/realview-remote-inspection-realview-inspection-coverage-unavailable","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Coverage Unavailable realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links record_no_coverage Host application viewing coverage_unavailable outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-observation-recorded","kind":"Event","title":"realview_inspection.observation_recorded","description":"Application-owned remote visual inspection fact emitted after record_observation reaches observation_recorded.","href":"/events/realview-remote-inspection-realview-inspection-observation-recorded","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Observation Recorded realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links record_observation Inspector viewing observation_recorded outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-review-requested","kind":"Event","title":"realview_inspection.review_requested","description":"Application-owned remote visual inspection fact emitted after submit_review reaches review_pending.","href":"/events/realview-remote-inspection-realview-inspection-review-requested","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Review Requested realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links submit_review Inspector observation_recorded review_pending outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-accepted","kind":"Event","title":"realview_inspection.accepted","description":"Application-owned remote visual inspection fact emitted after accept reaches accepted.","href":"/events/realview-remote-inspection-realview-inspection-accepted","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Accepted realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links accept Inspection reviewer review_pending accepted outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-rework-requested","kind":"Event","title":"realview_inspection.rework_requested","description":"Application-owned remote visual inspection fact emitted after request_rework reaches rework_required.","href":"/events/realview-remote-inspection-realview-inspection-rework-requested","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Rework Requested realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links request_rework Inspection reviewer review_pending rework_required outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-entitlement-expired","kind":"Event","title":"realview_inspection.entitlement_expired","description":"Application-owned remote visual inspection fact emitted after record_entitlement_expired reaches entitlement_pending.","href":"/events/realview-remote-inspection-realview-inspection-entitlement-expired","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Entitlement Expired realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links record_entitlement_expired Host application ready viewing entitlement_pending outbox idempotency replay deduplication event schema"},{"id":"event:realview-remote-inspection-realview-inspection-cancelled","kind":"Event","title":"realview_inspection.cancelled","description":"Application-owned remote visual inspection fact emitted after cancel reaches cancelled.","href":"/events/realview-remote-inspection-realview-inspection-cancelled","eyebrow":"stateful · remote visual inspection · v1","keywords":"Realview Inspection Cancelled realview-remote-inspection Entitled RealView remote inspection app-widgets-deep-links cancel Inspector draft entitlement_pending ready viewing coverage_unavailable observation_recorded review_pending rework_required cancelled outbox idempotency replay deduplication event schema"},{"id":"event:vision-inference-review-vision-case-registered","kind":"Event","title":"vision.case_registered","description":"Application-owned vision evidence case fact emitted after register_case reaches registered.","href":"/events/vision-inference-review-vision-case-registered","eyebrow":"stateful · vision evidence case · v1","keywords":"Vision Case Registered vision-inference-review Governed SkyDNN inference review ai-location register_case Asset steward  registered outbox idempotency replay deduplication event schema"},{"id":"event:vision-inference-review-vision-model-locked","kind":"Event","title":"vision.model_locked","description":"Application-owned vision evidence case fact emitted after lock_model reaches model_locked.","href":"/events/vision-inference-review-vision-model-locked","eyebrow":"stateful · vision evidence case · v1","keywords":"Vision Model Locked vision-inference-review Governed SkyDNN inference review ai-location lock_model Vision worker registered model_locked outbox idempotency replay deduplication event schema"},{"id":"event:vision-inference-review-vision-inference-requested","kind":"Event","title":"vision.inference_requested","description":"Application-owned vision evidence case fact emitted after request_inference reaches inference_requested.","href":"/events/vision-inference-review-vision-inference-requested","eyebrow":"stateful · vision evidence case · v1","keywords":"Vision Inference Requested vision-inference-review Governed SkyDNN inference review ai-location request_inference Vision worker model_locked inference_requested outbox idempotency replay deduplication event schema"},{"id":"event:vision-inference-review-vision-inference-recorded","kind":"Event","title":"vision.inference_recorded","description":"Application-owned vision evidence case fact emitted after record_inference reaches inferred.","href":"/events/vision-inference-review-vision-inference-recorded","eyebrow":"stateful · vision evidence case · v1","keywords":"Vision Inference Recorded vision-inference-review Governed SkyDNN inference review ai-location record_inference Vision worker inference_requested inferred outbox idempotency replay deduplication event schema"},{"id":"event:vision-inference-review-vision-review-requested","kind":"Event","title":"vision.review_requested","description":"Application-owned vision evidence case fact emitted after submit_review reaches review_pending.","href":"/events/vision-inference-review-vision-review-requested","eyebrow":"stateful · vision evidence case · v1","keywords":"Vision Review Requested vision-inference-review Governed SkyDNN inference review ai-location submit_review Policy service inferred review_pending outbox idempotency replay deduplication event schema"},{"id":"event:vision-inference-review-vision-accepted","kind":"Event","title":"vision.accepted","description":"Application-owned vision evidence case fact emitted after accept reaches accepted.","href":"/events/vision-inference-review-vision-accepted","eyebrow":"stateful · vision evidence case · v1","keywords":"Vision Accepted vision-inference-review Governed SkyDNN inference review ai-location accept Independent reviewer review_pending accepted outbox idempotency replay deduplication event schema"},{"id":"event:vision-inference-review-vision-rejected","kind":"Event","title":"vision.rejected","description":"Application-owned vision evidence case fact emitted after reject reaches rejected.","href":"/events/vision-inference-review-vision-rejected","eyebrow":"stateful · vision evidence case · v1","keywords":"Vision Rejected vision-inference-review Governed SkyDNN inference review ai-location reject Independent reviewer review_pending rejected outbox idempotency replay deduplication event schema"},{"id":"event:vision-inference-review-vision-redacted","kind":"Event","title":"vision.redacted","description":"Application-owned vision evidence case fact emitted after redact reaches redacted.","href":"/events/vision-inference-review-vision-redacted","eyebrow":"stateful · vision evidence case · v1","keywords":"Vision Redacted vision-inference-review Governed SkyDNN inference review ai-location redact Privacy worker inferred review_pending accepted rejected redacted outbox idempotency replay deduplication event schema"},{"id":"sample-app:store-locator","kind":"Sample app","title":"Store Locator","description":"Discover eligible branches, compare distance and ETA, preserve Mappls Pin identity, and hand off safely to navigation.","href":"/samples/store-locator","eyebrow":"Starter · 6 tests","keywords":"Node.js Responsive map-and-list UI Nearby adapter Matrix adapter maps search-places routes-navigation app-widgets-deep-links Locate → discover → filter → rank → select → navigate Responsive synchronized map and list Credential-safe server boundary Nearby and matrix contract provenance Stable Mappls Pin continuity Service intersection filters Opening and accessibility eligibility Distance, ETA, and name ranking Honest radius and empty states Validated navigation deep links Canonical bounded cache Defensive cache isolation"},{"id":"sample-app:delivery-control-tower","kind":"Sample app","title":"Delivery Control Tower","description":"Track live orders, explain ETA risk, replay a trip, and handle delivery exceptions.","href":"/samples/delivery-control-tower","eyebrow":"Advanced · 7 tests","keywords":"Node.js Browser UI InTouch adapter intouch-telematics routes-navigation maps Plan → ready → track → recover → close → replay Responsive fleet control tower Durable trip aggregates Immutable telemetry ledger Event-time and receipt-time ordering Late-event derived revisions Owned exception recovery Idempotent commands and observations Optimistic concurrency Transactional outbox InTouch adapter boundary Provider close reconciliation Restart recovery"},{"id":"sample-app:grid-restoration-desk","kind":"Sample app","title":"Grid Restoration Desk","description":"Correlate an outage, govern independent switching approval, dispatch an assigned crew, preserve rework, and reconcile restoration from telemetry and customer-impact evidence.","href":"/samples/grid-restoration-desk","eyebrow":"Advanced · 14 tests","keywords":"Node.js Responsive operations desk Atomic evidence repository Mappls fixture adapter gis-analytics intouch-telematics workmate routes-navigation capture-feedback Report → correlate → approve switching → dispatch → prove → reconcile Responsive restoration operations desk Complete eight-event outage journey Role-scoped operational commands Independent switching-plan approval Assigned-crew enforcement Independent restoration reconciliation Telemetry and customer-impact recovery gate Rejected-attempt retention and rework Map and route evidence separated from electrical authority Private evidence and credential rejection Idempotent commands Optimistic concurrency Append-only audit events Transactional outbox Atomic restart recovery Credential-free zero-network fixture mode"},{"id":"sample-app:care-transfer-desk","kind":"Sample app","title":"Care Transfer Desk","description":"Confirm the correct receiving entrance, assign eligible transport, preserve courier custody, review condition exceptions, and reconcile receiver acceptance without retaining patient or clinical data.","href":"/samples/care-transfer-desk","eyebrow":"Advanced · 17 tests","keywords":"Node.js Responsive custody desk Atomic evidence repository Mappls care fixture adapter search-places routes-navigation intouch-telematics capture-feedback gis-analytics Request → confirm facility → assign → custody → review exceptions → accept Responsive privacy-minimized custody desk Complete ten-event exception-aware journey Exact role-scoped commands Confirmed clinical-entrance revision Bounded transport eligibility and stability window Assigned-courier custody enforcement Independent condition-exception review Arrival separated from completion Custody-bound receiver acceptance Independent quality reconciliation Rejected receipt retention and rework Patient and clinical evidence rejection Idempotent commands Optimistic concurrency Append-only audit events Transactional outbox Atomic restart recovery Credential-free zero-network fixture mode"},{"id":"sample-app:airside-turnaround-desk","kind":"Sample app","title":"Airside Turnaround Desk","description":"Coordinate a revision-safe aircraft turnaround, pause for airside exceptions, preserve four service milestones, and require independent airline, airport, and safety readiness decisions.","href":"/samples/airside-turnaround-desk","eyebrow":"Advanced · 22 tests","keywords":"Node.js Responsive airside control desk Atomic evidence repository Mappls aviation fixture adapter gis-analytics intouch-telematics workmate maps capture-feedback Draft → lock stand → plan → dispatch → evidence → review → ready Responsive aviation control desk Complete sixteen-event exception-aware journey Exact role-scoped operational commands Immutable stand and zone revisions Stale plan and assignment invalidation Eligible vehicle and assigned-lead enforcement Four independently evidenced service milestones Independent airside exception investigation Abort without invented readiness Airline, airport, and safety authority separation Map, route, task, and telemetry evidence separated from authority Passenger, location, clearance, and credential rejection Idempotent commands Optimistic concurrency Append-only audit events Transactional outbox Atomic restart recovery Credential-free zero-network fixture mode"},{"id":"sample-app:field-service","kind":"Sample app","title":"Field Service Console","description":"Create, assign, execute, and audit a technician visit with proof.","href":"/samples/field-service","eyebrow":"Production pattern · 6 tests","keywords":"Node.js Browser UI Workmate adapter workmate routes-navigation capture-feedback Create → assign → accept → travel → prove → close Browser operations console Durable task snapshots Append-only audit history Idempotent commands Optimistic concurrency Proof approval and rework Transactional outbox Mappls adapter boundary Restart recovery"},{"id":"sample-app:fleet-geofence","kind":"Sample app","title":"Fleet Geofence Monitor","description":"Design zones and run an actionable live enter/exit event queue.","href":"/samples/fleet-geofence","eyebrow":"Production pattern · 7 tests","keywords":"Node.js Browser UI InTouch adapter intouch-telematics maps Draft → publish → breach → acknowledge → resolve Responsive exception queue Validated geofence geometry Versioned provider rule identity Immutable source activity ledger Jitter suppression without evidence loss Asset-scope enforcement Named case ownership and SLA Evidence-backed resolution Safe rule retirement Idempotent activity ingestion Optimistic concurrency Transactional outbox Restart recovery"},{"id":"sample-app:retail-site-lab","kind":"Sample app","title":"Retail Site Lab","description":"Compare candidate sites through immutable dataset versions, reproducible scoring, lineage, and governed sharing.","href":"/samples/retail-site-lab","eyebrow":"Advanced · 8 tests","keywords":"Node.js Browser UI mGIS adapter Insight lineage gis-analytics search-places Version → validate → publish → process → share → revoke Responsive decision lab Immutable dataset versions Content-hash deduplication CRS and feature diagnostics Reproducible weighted scoring Parameter and input lineage Failed-attempt retry links Audience, expiry, export, and embed policy Share revocation without evidence loss Idempotent commands Optimistic concurrency Transactional outbox Restart recovery"},{"id":"sample-app:trip-planner","kind":"Sample app","title":"Weekend Trip Planner","description":"Preserve Mappls place identity through a durable ordered itinerary, route revisions, progress, and completion.","href":"/samples/trip-planner","eyebrow":"Starter · 8 tests","keywords":"Node.js Responsive itinerary UI Search adapter Routes adapter maps search-places routes-navigation app-widgets-deep-links Discover → save → sequence → preview → go → complete Responsive itinerary planner Provider-backed discovery provenance Mappls Pin identity continuity Bounded duplicate-free stops Exact sequence validation Profile-aware multi-leg routes Immutable route revisions Automatic stale-route invalidation Ordered visit and explicit skip progress Pause, resume, and deliberate cancellation Completion invariants Idempotent commands Optimistic concurrency Transactional outbox Restart recovery"},{"id":"sample-app:incident-dispatch","kind":"Sample app","title":"Incident Dispatch","description":"Resolve an incident, choose a capable available responder, route, track evidence, enforce arrival, and review.","href":"/samples/incident-dispatch","eyebrow":"Advanced · 8 tests","keywords":"Node.js Browser control room Search adapter Routes adapter InTouch adapter search-places routes-navigation intouch-telematics gis-analytics Report → locate → dispatch → route → coordinate → resolve → review Responsive incident command UI Stable CAD identity Confidence-bearing location resolution Capability and availability filtering Matrix ETA responder ranking Active-unit double-dispatch prevention Assigned-unit acceptance Vehicle-aware route identity Event-time telemetry ordering Late evidence without state regression Hazard updates Objective arrival policy Resolution evidence Attributable review metrics Idempotent commands Optimistic concurrency Transactional outbox Restart recovery"},{"id":"sample-app:address-verifier","kind":"Sample app","title":"Address Verifier","description":"Normalize an address, govern consented device evidence, apply versioned policy, and retain an attributable decision.","href":"/samples/address-verifier","eyebrow":"Production pattern · 8 tests","keywords":"Node.js Browser trust studio Search adapter Evidence ledger search-places capture-feedback Enter → normalize → consent → capture → compare → decide → redact Responsive trust studio Stable external business identity Mappls Pin normalization and provenance Purpose-bound expiring consent Consent revocation Immutable device-evidence ledger Event and receipt time Accuracy-bearing capture Evidence content hashes Versioned distance policy Mandatory weak-evidence review Automated override prevention Precise-data redaction with audit retention Idempotent commands Optimistic concurrency Transactional outbox Restart recovery"},{"id":"sample-app:map-story","kind":"Sample app","title":"Map Story","description":"Compile validated GeoJSON into an accessible, deterministic, source-disclosed narrative map.","href":"/samples/map-story","eyebrow":"Starter · 5 tests","keywords":"Node.js Accessible scrollytelling UI GeoJSON compiler maps gis-analytics Validate → compile → encode → narrate → share Responsive scrollytelling experience Bounded GeoJSON compiler Geometry and coordinate validation Unique feature and sequence identity Numeric range enforcement Markup-safe narrative content Derived geographic bounds and metrics Deterministic documented visual encoding Keyboard-accessible map points Scroll, focus, and URL synchronization Required source, date, and license disclosure Honest fixture labelling"},{"id":"sample-app:spatial-agent","kind":"Sample app","title":"Spatial Operations Agent","description":"Research, plan, approve, execute, and cite grounded Mappls MCP operations through fixture, local stdio, or authenticated remote transports.","href":"/samples/spatial-agent","eyebrow":"Advanced · 15 tests","keywords":"Node.js Browser agent lab Mappls MCP SDK client ai-location search-places routes-navigation intouch-telematics Ask → plan → review → approve → execute → cite Responsive governed-agent UI Six-pattern agent authority planner Twelve conditional governance controls Eight-dimension evaluation contract Credential-free solution research All sixteen industries and thirteen platform targets Deterministic fixture boundary Real local stdio MCP client Authenticated Streamable HTTP MCP client Offline and live-read profile isolation HTTPS and exact endpoint validation Bounded arguments, calls, buffers, and outputs Advertised-tool enforcement Gateway credential non-echo Deterministic allow-listed plans Immutable SHA-256 plan identity Human approval as a state transition Explicit least-privilege scopes Expiring approvals Sensitive live-location risk class Dependency-bound tool execution Provider provenance on every live result Explicit catalog provenance for offline tools Grounded per-step citations Secret-safe failure persistence Idempotent commands Optimistic concurrency Transactional outbox Graceful MCP shutdown Restart recovery"},{"id":"sample-app:a2a-solution-studio","kind":"Sample app","title":"A2A Solution Studio","description":"Discover the Mappls A2A v1 service, delegate exact offline or purpose-bound live-read work, reconcile ambiguous outcomes, and review immutable artifacts without elevating their authority.","href":"/samples/a2a-solution-studio","eyebrow":"Advanced · 21 tests","keywords":"Node.js Responsive coordination UI Official A2A SDK client Durable evidence ledger ai-location search-places routes-navigation intouch-telematics Draft → discover profile → delegate → reconcile → review → accept or reject Responsive A2A coordination studio Official A2A v1 SDK client JSONRPC and HTTP+JSON negotiation OAuth-protected A2A client Transport token non-persistence Agent Card OAuth contract validation Offline and live-read profile discovery All ten live-read command contracts Exact live-read OAuth scope Purpose and data-class evidence One-read authority validation Provider payload excluded from audit Credential-free zero-network fixture Agent Card SHA-256 fingerprint Advertised-skill and protocol validation Client-owned message and context identity Server-assigned task identity Unknown-outcome context reconciliation Structured-only command allowlist Canonical command and artifact digests Offline authority non-escalation Live authority non-escalation Human accept and reject review Explicit no provider writes Explicit no production approval Idempotent commands Changed-intent replay rejection Optimistic concurrency Append-only audit events Transactional outbox Atomic restart recovery Bounded input and Agent Card HTTPS outside loopback"},{"id":"sample-app:mcp-identity-lab","kind":"Sample app","title":"MCP Identity Interoperability Lab","description":"Provision, discover, validate, and revoke a remote MCP client through a signed, replay-safe control-plane adapter and a non-issuing OAuth interoperability sandbox.","href":"/samples/mcp-identity-lab","eyebrow":"Advanced · 13 tests","keywords":"Node.js Signed pre-registration adapter OAuth discovery validator Durable audit UI ai-location Approve → deliver → register → discover → validate → revoke Responsive identity boundary explorer Worker-compatible HMAC-SHA256 envelope Five-minute signature freshness window Strict 32 KiB request bound Secret-shaped field rejection Public and confidential callback policy Deterministic non-secret client identity Signed retry contract compatibility Exact replay and event conflict handling Durable signed-event receipts RFC 9728 protected-resource metadata RFC 8414 authorization-server metadata Exact OAuth resource indicator PKCE S256 request validation Exact redirect and least-scope checks No authorization-code or token issuance Idempotent conformance runs Typed revocation outcomes Append-only audit evidence Atomic file persistence Restart recovery"},{"id":"sample-app:vision-evidence-desk","kind":"Sample app","title":"Vision Evidence Desk","description":"Lock a SkyDNN model to an immutable asset identity, record a synchronous fixture inference, validate geometry and confidence, review independently, and redact derived detections on schedule.","href":"/samples/vision-evidence-desk","eyebrow":"Advanced · 10 tests","keywords":"Node.js Responsive review UI SkyDNN synchronous adapter Evidence and retention ledger ai-location gis-analytics capture-feedback Register → lock model → infer → validate → review → decide → redact Responsive vision-review desk Public OpenAPI and marketing boundary separation Synchronous provider contract separated from application workflow No image body, media URL, credential, face, plate, or internal path input Opaque asset references and SHA-256 identity Purpose, lawful-basis, capture-time, and retention gates Entitled model-discovery fixture Immutable model fingerprint lock Idempotent inference attempts Normalized rectangle, polygon, and polyline validation Confidence and sensitive-class review policy Independent reviewer separation of duties Attributable acceptance and rejection Derived-output redaction with minimum audit retention Secret-safe provider failures Idempotent commands Optimistic concurrency Append-only audit events Transactional outbox Atomic restart recovery Credential-free fixture mode"},{"id":"sample-app:widget-journey-host","kind":"Sample app","title":"Widget Journey Host","description":"Own a complete place-selection journey around a Mappls widget: launch, recover through fallback, normalize a candidate, commit deliberately, invalidate stale selection, and submit exactly once in effect.","href":"/samples/widget-journey-host","eyebrow":"Production pattern · 8 tests","keywords":"Node.js Responsive host form UI Widget message adapter Durable evidence store app-widgets-deep-links search-places Draft → open → candidate → commit → submit Responsive widget-host journey Exact-origin postMessage validation Versioned candidate schema Mappls Pin normalization Opaque provider result rejection Application-owned durable selection Useful manual fallback Stale-selection invalidation after host edits Deliberate cancellation Idempotent commands Optimistic concurrency Append-only audit events Transactional outbox Restart recovery Credential-free fixture mode"},{"id":"sample-app:deep-link-journey-host","kind":"Sample app","title":"Deep-link & Native UI Journey Host","description":"Run complete direction-planning and geofence-draft lifecycles around Mappls iOS UI adapters, with an exact documented navigation-link fallback and no invented callback or provider publication claim.","href":"/samples/deep-link-journey-host","eyebrow":"Production pattern · 11 tests","keywords":"Node.js Responsive two-lane journey UI iOS native fixture adapters Durable evidence store app-widgets-deep-links routes-navigation intouch-telematics Draft → edit → validate → select or review → acknowledge Responsive direction and geofence journey lab Exact documented Mappls navigation HTTPS fallback Validated Mappls app URI Explicit no-return-callback evidence boundary Versioned host-owned iOS adapter envelopes Stale editor generation rejection Immutable route and geometry draft revisions Route-index and intent-match validation Navigation request separated from target acceptance Circle radius and coordinate bounds Canonical non-crossing polygon validation SHA-256 geometry identity Independent geofence reviewer separation of duties Approved application draft separated from provider publication No invented geofence deep link or rule identity Idempotent commands Cross-aggregate replay rejection Optimistic concurrency Append-only audit events Transactional outbox Atomic restart recovery Credential-free fixture mode"},{"id":"sample-app:place-contribution-desk","kind":"Sample app","title":"Place Contribution Desk","description":"Embed the public Add a Place form, preserve contributor-reported submission as testimony, reconcile independently, and close only with attributable publication evidence.","href":"/samples/place-contribution-desk","eyebrow":"Production pattern · 8 tests","keywords":"Node.js Responsive operations UI Add a Place iframe Reconciliation evidence ledger app-widgets-deep-links capture-feedback search-places Draft → open → report → reconcile → publish, reject, or withdraw Responsive contribution operations desk Corrected public iframe query shape No undocumented submission endpoint No invented callback or receipt Contributor testimony separated from provider evidence Seven explicit lifecycle states Immutable widget attempts Mappls Pin evidence validation Allow-listed evidence sources Explicit application-side withdrawal boundary Rejection and immutable retry Idempotent commands Optimistic concurrency Append-only audit events Transactional outbox Atomic restart recovery Credential-free fixture mode"},{"id":"sample-app:realview-inspection-desk","kind":"Sample app","title":"RealView Inspection Desk","description":"Qualify paid RealView access, open bounded viewer attempts, validate the documented no-imagery signal, record human observations, and require separate review without persisting tokens or imagery.","href":"/samples/realview-inspection-desk","eyebrow":"Advanced · 10 tests","keywords":"Node.js Responsive inspection UI RealView Auth2 adapter Human evidence and review ledger app-widgets-deep-links maps capture-feedback Draft → entitle → view → observe → review → accept or rework Responsive remote-inspection desk Paid-entitlement state separated from application state No credential or token-bearing URL input Non-secret entitlement references Ephemeral token-handle model Exact Auth2 origin equality One-field status-204 schema validation Lookalike-origin rejection HTTP shell and coverage evidence separation Immutable viewer attempts Human observations without provider metadata No imagery or screenshot persistence Inspector-reviewer separation of duties Entitlement expiry recovery Immutable rework Idempotent commands Optimistic concurrency Append-only audit events Transactional outbox Atomic restart recovery Credential-free fixture mode"},{"id":"sample-app:offline-release-control","kind":"Sample app","title":"Offline Release Control","description":"Operate an entitled offline or automotive runtime as one compatible, dual-slot release across manufacture, activation, installation, qualification, update, interruption, rollback, and retirement.","href":"/samples/offline-release-control","eyebrow":"Advanced · 10 tests","keywords":"Node.js Responsive fleet release UI A/B slot controller Manifest and qualification ledger offline-automotive maps routes-navigation Manufacture → activate → install → qualify → update → recover → retire Responsive fleet release console Public and local evidence-generation separation No runtime, map package, binary, license, activation key, credential, or URL input Non-secret entitlement evidence Runtime/data/configuration/voice manifest unit Exact CPU/ABI/OS/graphics compatibility SHA-256 manifest and component identities Independent signature and observed-digest attestations Dual-slot active and known-good invariants Download, verify, stage, switch, and qualify checkpoints Seven-lane deterministic qualification suite Power-loss recovery before atomic switch Power-loss rollback after switch Post-qualification regression rollback Activation expiry and offline-grace gate Retirement without history deletion Idempotent commands Optimistic concurrency Append-only audit events Transactional outbox Atomic restart recovery Credential-free fixture mode"}]}