AWAKENS · OAuth Scopes

AWAKENS OAuth Scopes

OAuth 2.0 derived

AWAKENS uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://genomelink.io/oauth/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.

CompanyGenomicsDNABioinformaticsHealthConsumer GeneticsAncestryOAuthPersonal Genomics

Scopes: 0 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://genomelink.io/oauth/authorize

Token URL
https://genomelink.io/oauth/token

Flows
authorizationCode

Scopes (0)

AWAKENS implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference: https://genomelink.io/developers/

Source

OAuth Scopes

generated: '2026-07-18'
method: derived
source: https://github.com/genomelink/genomelink-python
docs: https://genomelink.io/developers/
schemes:
- name: oauth2
  source: https://github.com/genomelink/genomelink-python/blob/master/genomelink/oauth.py
  flows:
  - flow: authorizationCode
    authorizationUrl: https://genomelink.io/oauth/authorize
    tokenUrl: https://genomelink.io/oauth/token
scopes: []
notes: >-
  The OAuth authorization-code flow accepts a `scope` parameter (passed through
  the SDK authorize_url / authorizeUrl helpers), and access is granted per
  genetic-trait report requested by the consenting user (reports are addressed
  by trait name, e.g. eye-color, and population). AWAKENS does not publish an
  enumerated scope reference on the developers page, so no specific scope
  strings are asserted here to avoid fabrication. scopes[] is intentionally
  empty pending a published permissions reference.