Create or select a Developer app to work with your Team’s real API data. New apps receive the default 14-day trial. You can explore the public Five Demo immediately without an account, an app, or starting a trial.
Sign in and choose the owning Team
Open Apps and sign in with Realsee Passport. Choose the Team that will own the integration. A Team can represent a person, a company, or another organization.
Each Team can have up to three Developer apps, shared across its members. Expired or disabled apps still count toward this limit. Only a Team owner can create an app; members can ask an owner or switch to a Team where they have owner access.
Create a trial app
Choose Create trial app. Enter an app name and check the prefilled contact name and email; the description of what you are building is optional. The Team shown in the form is the owner. Change the active Team before submitting if the app belongs elsewhere.
The portal saves an App request and starts creation. Keep its request reference if creation is still in progress. Closing the panel does not cancel the saved request; Apps and application records let you reopen it.
Get your credentials
When creation succeeds, the App request becomes Completed immediately and is bound to the app’s AK. CRM delivery, commercial follow-up, trial configuration, and the first API call are separate from request completion. If creation needs attention, follow the saved request’s status instead of creating a replacement application.
Open the app detail to copy the AK and use the guarded SK reveal action when you need server-side credentials. The app uses the shared /open interface scope; you do not apply for separate product capabilities. Actual resource availability and app status still govern whether a request can succeed.
The existing business process configures the trial. A new app may show Trial dates pending while its information is being updated. Use the app’s reported availability and trial information; do not calculate an expiry from the App request submission time. A later expiry does not undo Completed or change the saved AK.
Start integration
Choose Start integration in the app detail. Follow the server-side token exchange and read-only request instructions, then check the actual response. An empty resource result can mean the Team has no suitable work; it does not require a new app. Never paste SK or access tokens into browser code, support text, URLs, or logs.
For scene rendering, open Playground and choose a page-local Viewing Team. Playground resolves an enabled app’s AK before loading that Team’s VR list. This selection does not switch the Team that owns your Dashboard data.
Render the public Five Demo
The public sample also gives you an independent first SDK result:
npm install @realsee/five @realsee/open-works three@0.117.1Render a public work independently of app creation:
import { Five, parseWork } from '@realsee/five'
import workJSON from '@realsee/open-works/virtual/816lPVZQkQDF5XOpPo/work.json'
const container = document.querySelector<HTMLElement>('#app')
const five = new Five({ imageOptions: { size: 1024 } })
if (container) {
five.appendTo(container)
await five.load(parseWork(workJSON))
five.refresh()
}This first SDK render does not require an OpenAPI token and does not prove that a real Team API request succeeded. Server-side OpenAPI calls and SDK rendering are separate steps.
Continue with the same app
Join the Realsee Discord community to ask questions or discuss continued use of your existing app. Trial extensions require confirmation from the team. Never share SK or tokens in community messages.
Next steps
- Five SDK — render and control spatial scenes.
- OpenAPI — call the shared interfaces from your server.
- Argus — evaluate AI reconstruction workflows.
- Team and App Management — understand Team scope, the three-app limit, and permanent request completion.