Sensorup Inc Authentication

generated: '2026-10-23'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.sensorup.com/api/graphql/authentication.md
sources:
- https://docs.sensorup.com/api/graphql/authentication.md
- https://docs.sensorup.com/api/graphql/subgraphs/auth.md
- https://docs.sensorup.com/use-sensorup/getting-started/platform-overview.md
- https://docs.sensorup.com/use-sensorup/getting-started/building-complete-methane-management-program.md
description: Authentication methods for the SensorUp GraphQL API
schemes:
- type: other
  name: Session ID (Cookie)
  evidence: 'When you sign in through a web browser, the `sensorup_sessionid` cookie is automatically set and sent with each request:'
  location: cookie
  how_to_obtain: Obtained after a successful sign‑in mutation; the server sets the `sensorup_sessionid` cookie.
- type: other
  name: Session ID (Header)
  evidence: 'For API clients, mobile apps, and integrations, pass the session ID in the `x-sensorup-sessionid` header:'
  location: header
  header: x-sensorup-sessionid
  how_to_obtain: Obtained after a successful sign‑in mutation (or API‑key creation); use the returned session ID.
- type: other
  name: API Key Session ID
  evidence: 'Use the API key session ID in the `x-sensorup-sessionid` header (same as regular sessions):'
  location: header
  header: x-sensorup-sessionid
  how_to_obtain: Create an API key via the `createAPIKey` mutation; the response includes `apiKeySessionId`.
- type: other
  name: Federated Sign‑In (Cognito ID Token)
  evidence: 'For organizations using SSO, you can authenticate with Cognito tokens:'
  location: header
  header: x-sensorup-sessionid
  how_to_obtain: Provide a Cognito ID token to the `federatedSignIn` mutation; the mutation returns a session ID.
note: No OAuth2, HTTP Basic, Bearer, JWT, HMAC, or mTLS schemes are documented on the provided pages.
docs: https://docs.sensorup.com/api/graphql/authentication.md