Liquid Instruments · OAuth Scopes

Liquid Instruments OAuth Scopes

OAuth 2.0 probed

Liquid Instruments publishes 5 OAuth 2.0 scopes via the authorizationCode, clientCredentials, deviceCode, implicit, and password flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Liquid Instruments API on a user’s behalf.

Tokens are issued from https://auth.liquidinstruments.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.

CompanyTest and MeasurementInstrumentationHardwareOscilloscopeSpectrum AnalyzerData AcquisitionFPGAPhotonicsScientific InstrumentsElectronicsLaboratory
Scopes: 5 Flows: authorizationCode, clientCredentials, deviceCode, implicit, password Method: probed

OAuth endpoints

Authorization URL
https://auth.liquidinstruments.com/oauth2/authorize
Token URL
https://auth.liquidinstruments.com/oauth2/token
Flows
authorizationCodeclientCredentialsdeviceCodeimplicitpassword

Scopes (5)

ScopeDescriptionFlows
openid Standard OpenID Connect scope — requests an ID token identifying the end user.
offline_access Requests a refresh token so the client can obtain new access tokens without the user being present.
email Releases the email and email_verified claims.
phone Releases the phone_number claim.
profile Releases the profile claims (name, given_name, family_name, middle_name, preferred_username, picture, birthdate).

Source

OAuth Scopes

liquid-instruments-scopes.yml Raw ↑
generated: '2026-08-04'
method: probed
source: https://auth.liquidinstruments.com/.well-known/openid-configuration
docs: https://apis.liquidinstruments.com/cli/login.html
note: 'There is no OpenAPI declaring oauth2 securitySchemes for Liquid Instruments, so
  derive-oauth-scopes.py has nothing to read. These scopes were taken verbatim from the
  live OpenID Connect discovery document at auth.liquidinstruments.com (HTTP 200,
  application/json, fetched 2026-08-04). Only the standard OIDC scope set is advertised
  — no product- or resource-specific scopes are published. Liquid Instruments does not
  publish a scopes/permissions reference page.'
schemes:
- name: LiquidInstrumentsOIDC
  type: openIdConnect
  issuer: https://auth.liquidinstruments.com
  source: https://auth.liquidinstruments.com/.well-known/openid-configuration
  flows:
  - flow: authorizationCode
    authorizationUrl: https://auth.liquidinstruments.com/oauth2/authorize
    tokenUrl: https://auth.liquidinstruments.com/oauth2/token
    pkce: S256
  - flow: clientCredentials
    tokenUrl: https://auth.liquidinstruments.com/oauth2/token
  - flow: deviceCode
    deviceAuthorizationUrl: https://auth.liquidinstruments.com/oauth2/device_authorize
    tokenUrl: https://auth.liquidinstruments.com/oauth2/token
  - flow: implicit
    authorizationUrl: https://auth.liquidinstruments.com/oauth2/authorize
  - flow: password
    tokenUrl: https://auth.liquidinstruments.com/oauth2/token
scopes:
- scope: openid
  description: Standard OpenID Connect scope — requests an ID token identifying the end user.
  standard: true
  sources: [https://auth.liquidinstruments.com/.well-known/openid-configuration]
- scope: offline_access
  description: Requests a refresh token so the client can obtain new access tokens without
    the user being present.
  standard: true
  sources: [https://auth.liquidinstruments.com/.well-known/openid-configuration]
- scope: email
  description: Releases the email and email_verified claims.
  standard: true
  sources: [https://auth.liquidinstruments.com/.well-known/openid-configuration]
- scope: phone
  description: Releases the phone_number claim.
  standard: true
  sources: [https://auth.liquidinstruments.com/.well-known/openid-configuration]
- scope: profile
  description: Releases the profile claims (name, given_name, family_name, middle_name,
    preferred_username, picture, birthdate).
  standard: true
  sources: [https://auth.liquidinstruments.com/.well-known/openid-configuration]
claims_supported:
- applicationId
- at_hash
- aud
- authenticationType
- birthdate
- c_hash
- email
- email_verified
- exp
- family_name
- given_name
- iat
- iss
- jti
- middle_name
- name
- nbf
- nonce
- phone_number
- picture
- preferred_username
- roles
- sub
gaps:
- 'No resource-specific scopes are advertised — nothing describes what a token may do
  against Moku Cloud Compile, licensing, or device features. Authorization appears to be
  carried in a "roles" claim rather than in scopes.'
x-evidence:
  fetched: '2026-08-04'
  url: https://auth.liquidinstruments.com/.well-known/openid-configuration
  http_status: 200
  content_type: application/json

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/liquid-instruments-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.