Developer apps belong to a Realsee Passport Team. A Team can be an individual, a company, or another organization. Apps is the console’s starting point.
Team scope and roles
The active Team determines the app list, application records, and credential context. Switch it from the console’s Team selector or Account page. Only an owner can create an app; members can view the Team data available to them and contact an owner when creation is needed. Credential actions continue to enforce their existing authorization checks.
Playground’s optional Viewing Team is different: it only selects whose VRs to browse on that page and does not change the active Dashboard Team.
Up to three apps per Team
The limit is shared across the Team’s users. Expired or disabled apps still occupy a place. Once all three places are used, continue with an existing app. Historical Teams above the limit retain their apps and cannot create another through the portal. The portal does not add an app-deletion flow to recycle trial places.
Create and recover
An owner chooses Create trial app, supplies an app name, checks the contact name and email, and optionally describes the intended use. The displayed Team is the authoritative owner; there is no second editable Team name or product-capability picker.
Submission saves an App request and starts creation. If the result is pending, reopen the saved reference from Apps or application records. A retry of the same request uses the original identity and resolves to the same AK. A recovered success remains available even when the Team is now full. Avoid submitting another request to work around an unresolved creation.
Completed means the app and AK were saved
As soon as the Developer app is created successfully, its App request becomes Completed and the AK binding is saved with the completion time. Neither manual review, CRM synchronization, sales follow-up, trial configuration, nor the first API call is required for completion.
The request stays Completed when the app later expires, is disabled, or its live details cannot be loaded. Application records preserve the original AK and completion fact separately from current app availability.
Credentials and interface scope
The app detail shows AK, XID, availability, trial information, and guarded SK controls. Keep the SK on your server and out of browser bundles, URLs, logs, and support descriptions. Follow Authentication for the credential boundary.
Developer apps use the shared /open interface scope. Product capabilities are not separately selected or activated in this portal. A resource-access error, disabled app, trial condition, or rate limit remains a distinct issue; creating a second app is not the default remedy.
Trial and continued access
A new app receives the default 14-day trial, configured by the existing business process. Trial information may initially be pending. The portal displays available upstream information and does not infer an end date from the request timestamp.
For integration questions, app creation issues, production use, or continued access, join the Realsee Discord community. Start there for help with your existing app. Trial extensions require confirmation from the team. Use the email link in the site footer for private account issues. Never share SK or tokens in community messages.