Embed the form. Never invent the publication.

The public Add a Place demo is usable without a credential, but its documentation has a broken first-query separator and publishes no callback or moderation contract. This guide corrects the embed while keeping every later state evidence-bound.

200correct query

The base demo and conventional ? parameter shape returned successfully on 2026-08-17.

401literal docs path

The documented first & separator did not resolve as a working widget path.

0callbacks assumed

No message, receipt, moderation, withdrawal, or publication schema is manufactured.

7lifecycle states

The host separates reported submission from independently verified publication.

Configure only documented display options

No token or callback input exists because neither is part of the established public contract.

source ready

Mappls Add a Place widget

Application-owned place contribution case

Corrected iframe sourcehttps://embed.mappls.com/addAplace?fullscreen=true&position=top-left&zoom=16&pitch=0
Embed and host boundary
<div class="mappls-widget" aria-busy="false">
  <iframe src="https://embed.mappls.com/addAplace?fullscreen=true&amp;position=top-left&amp;zoom=16&amp;pitch=0" title="Mappls Add a Place widget" loading="lazy" style="width: 100%; min-height: 420px; border: 0;" allowfullscreen></iframe>
  <p><a href="https://embed.mappls.com/addAplace?fullscreen=true&amp;position=top-left&amp;zoom=16&amp;pitch=0">Open the Mappls view directly</a></p>
</div>
Read as JSON

One character separates the documented example from the working URL.

The official examples use '&' before the first option. On 2026-08-17 the base demo and conventional '?' query returned HTTP 200, while the literal documented ampersand path returned HTTP 401. Reconfirm this public behavior before release.

Open official documentation

A success screen is not a published place.

No public source establishes a postMessage payload, submission receipt, moderation status, Mappls Pin return, withdrawal operation, or publication SLA. Frame load and visible success copy are not durable provider evidence.

01
Host application

draft

One contribution case owns business context, purpose, actor, consent, and bounded non-sensitive notes.

02
Browser lifecycle

widget open

One iframe generation is visible with loading, blocked, offline, cancel, and direct-link fallback states.

03
User plus host

submission reported

The user reports completing the hosted flow. This is interaction evidence only—not a Mappls receipt or published place.

04
Host operations

publication pending

A review task waits for an independently observable Mappls result under an explicit SLA and retry policy.

05
Host reconciliation

published

A provider-backed search or approved Mappls receipt establishes the published Mappls Pin, observed fields, source, and time.

06
Host operations

rejected

A documented provider outcome or attributable review records reason, evidence, appeal/retry policy, and attempt identity.

07
Contributor or privacy operator

withdrawn

The application stops its case and retention workflow without claiming it withdrew an undocumented provider-side submission.

Own the case, attempt, evidence, and audit—not the provider frame.

Contribution case: external business identity, purpose, actor, state, version, and current attempt

Attempt: iframe generation, source version, opened/reported times, and non-sensitive user confirmation

Publication evidence: Mappls Pin, provider-backed observation, observed fields, source fingerprint, event/receipt time, and reviewer

Audit/outbox: idempotency key, optimistic version, actor, event, downstream status, and retention action

Useful in seven industries. Governed differently in each.

Each scenario defines the evidence needed before your application can call the contribution resolved.

Retail

A newly opened store is missing from discovery before launch week.

Case identity, authorized contributor, storefront evidence, category, review owner, and verified Mappls Pin.

Healthcare

A new clinic must become discoverable without publishing unreviewed medical contact details.

Purpose, consent, approved public fields, location evidence, moderation outcome, and privacy retention.

Real estate

A newly handed-over development needs one canonical entrance rather than duplicate listings.

Development identity, entrance coordinate, duplicate search, authoritative name, and reconciliation result.

Tourism

A community documents a landmark while protecting sensitive or restricted locations.

Source attribution, safety review, category, public-interest basis, and bounded published detail.

Emergency services

A new fire station must be discoverable while operational-only fields remain private.

Agency authority, public address, service category, publication observation, and prohibited-field review.

Events

A temporary venue needs arrival guidance with an expiry and removal plan.

Event dates, temporary-location policy, arrival entrance, accessibility context, and post-event review.

Education

A new campus gate should resolve consistently across admissions, transport, and safety apps.

Institution authority, entrance identity, address normalization, duplicate resolution, and shared Mappls Pin.

Operate reported submission through verified publication.

The Place Contribution Desk preserves attempts, versions, user reports, reconciliation evidence, rejection, withdrawal, audit, outbox, and restart recovery without calling an undocumented provider endpoint.

Run and download the app Study the state machineInspect repository evidence