Quartzy · OAuth Scopes
Quartzy OAuth Scopes
OAuth 2.0
derived
Quartzy 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://api.quartzy.com/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.
Lab ManagementInventory ManagementLife SciencesProcurementOrderingLaboratoryWebhooks
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://app.quartzy.com/oauth/authorize
https://app.quartzy.com/oauth/authorize
Token URL
https://api.quartzy.com/oauth/token
https://api.quartzy.com/oauth/token
Flows
authorizationCode
authorizationCode
Scopes (0)
Quartzy 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.
Quartzy documents per-user AccessToken authentication (Access-Token header) and references OAuth2 in endpoint authorizations, but publishes no OAuth scopes or permission granularity (https://docs.quartzy.com/api/).
Quartzy documents per-user AccessToken authentication (Access-Token header) and references OAuth2 in endpoint authorizations, but publishes no OAuth scopes or permission granularity (https://docs.quartzy.com/api/).
📄 Provider scope reference: https://docs.quartzy.com/api/