Developers
Build with Maphere
Choose an integration, understand what runs where, and connect your website to a hosted map.
Choose your integration
Maphere hosts the map and viewer. Your application can embed the complete viewer, replace its controls with your own interface, or work with approved place information from your backend. Your team continues to author and publish in the studio.
| You want to… | Use | Backend needed? |
|---|---|---|
| Show a public map with Maphere controls | The iframe snippet from Share | No |
| Control floors, selection or camera from your page | Browser SDK + hosted viewer | No, for public maps |
| Restrict viewing to your authorized visitors | Browser SDK + short-lived viewing sessions | Yes |
| Read or update permitted place information | Server SDK or REST API v1 | Yes |
What runs where
Scroll the diagram horizontally to see all participants, or read the steps below.
Read the flow step by step
- Your website + SDK → Maphere viewer: The SDK creates a titled iframe inside your map container.
- Maphere viewer → Maphere platform: The hosted viewer requests the selected floor and images. Protected requests require a valid viewing token.
- Maphere platform → Maphere viewer: The platform checks access and returns the content needed to render the map.
- Maphere viewer → Your website + SDK: The SDK receives map, floor and place IDs plus the current viewer state.
- Your website + SDK → Maphere viewer: Your interface sends a command. The hosted viewer applies it and reports the resulting state.
The browser SDK controls the hosted viewer; it does not include the editor, a self-hosted renderer or an offline map bundle. You can keep the built-in search, floors, camera and detail card, or supply your own controls. Maphere branding and source-data attribution stay with the viewer.
Before you start
- Create and review a map in your workspace. Choose Protected before the first publication if the map is sensitive.
- Publish the map, enable website embeds in Share, and save your website’s exact origin, including its scheme and port. Use HTTPS in production.
- Copy the SDK map ID from Share. It is the published map UUID, not a private editor map ID or the venue name.
- For protected viewing or content APIs, ask a workspace owner/admin to create a scoped key and store the secret in your backend’s secret manager.
Access and map data
An allowed website controls where an iframe can appear; it does not make a public map confidential. Protected maps also require server-verified viewing sessions. API keys stay on your backend, while short-lived viewing tokens reach the authorized browser.
Map data is delivered as JSON. The hosted viewer receives rendering data rather than the private authoring document. An authorized browser can still inspect and retain data it receives. Revocation stops future access; it cannot recall downloaded geometry, images or exports.