Can I embed a 360 panorama on my own website for free?

Yes. The embed is an iframe pointing at the viewer with ?embed=true, so it works on any host that can render HTML, including WordPress, Webflow, Shopify, Squarespace, a README or a plain static page. No API key or account is required for viewing.

Which image URL can I pass to the pano parameter?

Any publicly reachable HTTPS image in 2:1 equirectangular projection that can be loaded cross-origin. Panoramas published through the share API expose an /api/shares/{id}/image link that is already CORS-friendly and stays valid while the share is active.

Do I need a server to use the API?

No. The endpoints are plain JSON over HTTPS and the read-only ones need no authentication, so a static site, a Cloudflare Worker, a serverless function or a local script can call them directly.

How does the API authenticate private calls?

Send the session token from POST /api/user/guest or POST /api/user/auth as an Authorization: Bearer header. Guest sessions can generate panoramas with trial credits but cannot publish permanent shares, which requires a signed-in, non-guest account.

Are there rate limits?

Share reads are limited per hour and per day, publishing is limited to a handful of new links per day with a 100 MB personal quota, and generation is limited by daily credits and concurrent requests.

Can I call this API from an AI agent or an MCP server?

Yes. Every endpoint is standard JSON over HTTPS with no SDK requirement: POST /api/generate creates a scene, GET /api/shares?public=1 lists examples, and /api/shares/{id}/image is a texture URL that can be handed to other tools.

Is the viewer open source or self-hostable?

The rendering core is the standard Three.js equirectangular approach: one inverted sphere, a 2:1 texture and pointer controls. This page documents the hosted embed and API, and the same layout can be reproduced in your own build.

What response format do the endpoints return?

UTF-8 JSON for metadata and binary image bytes for /image and /download. Errors use standard HTTP status codes: 400 for invalid input, 401 for missing tokens, 403 for disabled downloads, 415 for unsupported upload types, 429 for rate limits and 503 while an upload is still propagating.

Developer Docs — Embed a 360° Panorama or Call the API

Drop an interactive 360° viewer into any page with a single iframe, or drive the platform from your own code: generate equirectangular panoramas, publish them, and read them back as JSON or image bytes. No SDK, and no API key for reads.

Embed a 360° Panorama with One iframe

Load https://360panoramaviewer.com/?embed=true&pano=https://example.com/my-panorama.jpg#embed inside an iframe. The page switches to full-viewport viewer mode, so the frame shows the scene only.

embed=true — full-viewport viewer mode with a small branding badge.
pano — public HTTPS URL of the 2:1 equirectangular image.
autorotate=1 — slow automatic camera rotation until the visitor drags.
#embed — hash form of the embed switch for hosts that strip query strings.

REST API Endpoints

GET /api/health — service, database and payment gateway status.
GET /api/billing — public plan configuration and trial credits.
GET /api/models — available image models with API keys stripped.
POST /api/user/guest — create a trial session and bearer token.
POST /api/generate — generate a 2:1 equirectangular panorama from a prompt.
GET /api/shares?public=1 — listed panoramas only, newest first, no auth.
GET /api/shares/{id}/image — panorama bytes, usable as a texture or embed source.
POST /api/shares — publish a panorama with a bearer token (PNG or JPEG body).

Authentication and Limits

Read-only endpoints need no credentials and send Access-Control-Allow-Origin: *. Private calls use an Authorization: Bearer session token from the guest or auth endpoint. Share reads are rate limited per hour and per day, publishing is limited to a few new links per day with a 100 MB personal quota, and generation is limited by daily credits.

AI Agents and MCP Tools

Every endpoint is ordinary JSON over HTTPS, so an agent or a self-hosted MCP server can call /api/generate to create a scene and then pass /api/shares/{id}/image to other tools as a plain image URL.