Sinai Technologies OAuth Scopes

OAuth 2.0 searched

Sinai Technologies publishes 6 OAuth 2.0 scopes via the clientCredentials and authorizationCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Sinai Technologies API on a user’s behalf.

Tokens are issued from https://auth.sinai.com/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyCarbon ManagementCarbon AccountingEmissionsSustainabilityESGDecarbonizationClimate

Scopes: 6 Flows: clientCredentials, authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://auth.sinai.com/oauth2/authorize

Token URL
https://auth.sinai.com/oauth2/token

Flows
clientCredentialsauthorizationCode

Scopes (6)

Scope	Description	Flows
https://api.sinai.com/organization	Organization-level data and features	clientCredentials
https://api.sinai.com/carbon_accounting	Read/write access to carbon accounting data	clientCredentials
https://api.sinai.com/baseline_forecasts	Read/write access to baseline forecasts data	clientCredentials
https://api.sinai.com/transition_plan	Transition plan modeling and access	clientCredentials
https://api.sinai.com/reduction_projects	Emissions reduction project data	clientCredentials
https://api.sinai.com/decarbonization_roadmap	Strategic decarbonization roadmap	clientCredentials

📄 Provider scope reference: https://docs.sinai.com/reference/accessing-the-api

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: openapi/sinai-technologies-openapi-original.yml
docs: https://docs.sinai.com/reference/accessing-the-api
notes: >-
  Scopes are resource-URI style and apply to the Client Credentials flow; request
  one or more as a space-separated `scope` parameter at the token endpoint. The
  Authorization Code flow currently supports no scopes (access is governed by the
  user's platform permissions). Docs enumerate an additional
  `https://api.sinai.com/decarbonization_roadmap` scope alongside those in the
  spec's flow map.
schemes:
- name: OAuth2ClientCredentialsProduction
  source: openapi/sinai-technologies-openapi-original.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.sinai.com/oauth2/token
- name: OAuth2AuthCodeProduction
  source: openapi/sinai-technologies-openapi-original.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://auth.sinai.com/oauth2/authorize
    tokenUrl: https://auth.sinai.com/oauth2/token
scopes:
- scope: https://api.sinai.com/organization
  description: Organization-level data and features
  flows:
  - clientCredentials
  sources:
  - openapi/sinai-technologies-openapi-original.yml
- scope: https://api.sinai.com/carbon_accounting
  description: Read/write access to carbon accounting data
  flows:
  - clientCredentials
  sources:
  - openapi/sinai-technologies-openapi-original.yml
- scope: https://api.sinai.com/baseline_forecasts
  description: Read/write access to baseline forecasts data
  flows:
  - clientCredentials
  sources:
  - openapi/sinai-technologies-openapi-original.yml
- scope: https://api.sinai.com/transition_plan
  description: Transition plan modeling and access
  flows:
  - clientCredentials
  sources:
  - openapi/sinai-technologies-openapi-original.yml
- scope: https://api.sinai.com/reduction_projects
  description: Emissions reduction project data
  flows:
  - clientCredentials
  sources:
  - openapi/sinai-technologies-openapi-original.yml
- scope: https://api.sinai.com/decarbonization_roadmap
  description: Strategic decarbonization roadmap
  flows:
  - clientCredentials
  sources:
  - openapi/sinai-technologies-openapi-original.yml