Include the following details (edit as applicable):
- Platform category: Unity
- Device Model & OS version: Quest 3
Hello, so I have an existing Site setup on Scaniverse and never had a Lightship account. Ive been following the Unity documentation to setup a project with NSDK. When I click the Get API Key button in Unity, im taken to the legacy lightship migrate to Niantic Spatial page. Since Ive never originally had a Lightship account, I have no account to migrate. When I hit ‘back’ on the site, it takes me to the login page, which takes me to my homepage, but the prompt to direct me to my API key has been lost. Even after being logged in, the site does not redirect. Is there another place to access this Key on the site? Thank you.
Thanks for reaching out — and you’re not missing anything here, this is a confusing edge case in the current setup.
At the moment, API keys are only available for projects that were created under the legacy Lightship system. Since you didn’t previously have a Lightship account, there isn’t a way to generate a new API key through the current portal.
The “Get API Key” flow you’re seeing in Unity is tied to that legacy system, which is why it’s redirecting you to the migration page without a path forward. For new projects, the recommended path is to use the latest NSDK (4.0), which no longer uses API keys and instead relies on the new authentication system. If you specifically need to use an older SDK version (for example, due to platform support like Quest), there unfortunately isn’t a supported way to create a new API key at this time.
I’ll pass this feedback along to the team as this gap in onboarding is something we’re actively aware of.
Kind regards,
Maverick L.
Thank you for the response. So I was originally on the latest NSDK, and successfully was able to test out a vps on 4.0 on iOS, but when I went to follow the quest 3 documentation listed here : Setting Up the Niantic SDK | Niantic Spatial Platform , I could only see instructions for 3.17. Is there currently a path to use the 4.0 NSDK with Quest 3?
Hi Nick,
We are currently evaluating adding Meta Quest 3 support back to the NSDK. In the meantime, you will have to use 3.17 or older.
Kind regards,
Maverick L.