Bodygram · OAuth Scopes

Bodygram OAuth Scopes

OAuth 2.0 searched

Bodygram 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.

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.

CompanyBody MeasurementComputer VisionArtificial IntelligenceSizingRetail3D AvatarHealthSDK

Scopes: 0 Flows: Method: searched

Scopes (0)

Bodygram 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://docs.bodygram.com/platform/api-reference

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://docs.bodygram.com/platform/api-reference
docs: https://docs.bodygram.com/platform/api-reference
api: Bodygram Platform API
style: api-key permission scopes
audience: api.platform.bodygram.com
scopes:
- name: api.platform.bodygram.com/scans:create
  description: Create a body scan (submit stats and/or two photos for measurement).
- name: api.platform.bodygram.com/scans:read
  description: >-
    Read a previously created scan's measurements, 3D avatar, and (when photos were
    provided) body composition and posture data.
notes: >-
  Scopes are permission strings attached to Bodygram API keys, addressed to the
  api.platform.bodygram.com audience; the API does not run a full OAuth 2.0
  authorization-code flow.