Niantic · Authentication Profile

Niantic Authentication

Authentication

Niantic secures its APIs with apiKey and token across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyGeospatialAugmented RealityComputer VisionVisual PositioningSpatial ComputingSDKPhysical AIRobotics
Methods: apiKey, token Schemes: 2 OAuth flows: API key in: sdk-config

Security Schemes

NianticSpatialToken token
scheme: bearer-token
LightshipApiKey apiKey
· in: sdk-config ()

Source

Authentication Profile

niantic-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://www.nianticspatial.com/docs/nsdk/
docs: https://www.nianticspatial.com/docs/nsdk/
notes: >-
  No OpenAPI is published for the Niantic Spatial platform (SDK-first: Unity/Swift/
  Kotlin/ROS 2), so this profile is captured from the developer documentation rather
  than derived from a spec. Two documented models coexist across SDK generations.
summary:
  types: [apiKey, token]
  api_key_in: [sdk-config]
schemes:
  - name: NianticSpatialToken
    type: token
    scheme: bearer-token
    description: >-
      NSDK 4.0 introduced a token-based authentication model for the Niantic
      Spatial platform, replacing the legacy API-key-only approach. Simplifies
      auth for testing and iteration across Unity, Swift, and Kotlin.
    since: NSDK 4.0
    sources: [docs]
  - name: LightshipApiKey
    type: apiKey
    in: sdk-config
    description: >-
      Legacy Lightship ARDK model. An API key created in the developer account is
      configured into the app; VPS validates the app's API key against the
      developer account. Superseded by token-based auth in NSDK 4.0.
    deprecated: true
    sources: [docs]