Rocketlane · Authentication Profile

Rocketlane Authentication

Authentication

Rocketlane secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyProfessional Services AutomationProject ManagementCustomer OnboardingResource ManagementTime TrackingPSASaaS
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

apiKeyAuth apiKey
· in: header ()

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://developer.rocketlane.com/docs/overview + https://developer.rocketlane.com/docs/api-explorer
docs: https://developer.rocketlane.com/docs/overview
summary:
  types: [apiKey]
  api_key_in: [header]
  oauth2_flows: []
schemes:
- name: apiKeyAuth
  type: apiKey
  in: header
  parameter_name: api-key
  description: Requests authenticate with a per-workspace API key passed in the
    'api-key' request header. Keys are generated from Rocketlane workspace settings.
notes: Rocketlane uses a static API-key header ('api-key') for all API access; no
  OAuth 2.0 / OpenID Connect flow is documented, so scopes/ is intentionally not
  produced (key auth has no scope surface).