LiveRamp · OAuth Scopes

LiveRamp OAuth Scopes

OAuth 2.0 searched

LiveRamp publishes 1 OAuth 2.0 scope via the clientCredentials and password flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the LiveRamp API on a user’s behalf.

Tokens are issued from https://api.habu.com/v1/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.

Data ConnectivityData CollaborationIdentity ResolutionActivationCleanroomPrivacyAdTechMarketingConsentAudience Segments

Scopes: 1 Flows: clientCredentials, password Method: searched

OAuth endpoints

Token URL
https://api.habu.com/v1/oauth/token https://serviceaccounts.liveramp.com/authn/v1/oauth2/token

Flows
clientCredentialspassword

Scopes (1)

Scope	Description	Flows
openid	The only scope value documented in the LiveRamp Service Account token request. Yields an OIDC id_token alongside the bearer access_token.	password

📄 Provider scope reference: https://developers.liveramp.com/activation-api/reference/oauth2defaultv1token

Source

OAuth Scopes

generated: '2026-08-13'
method: searched
source: openapi/liveramp-clean-room-api-openapi.yml
docs: https://developers.liveramp.com/activation-api/reference/oauth2defaultv1token
note: >-
  LiveRamp does not publish a scope/permission reference. The Clean Room API declares an oauth2
  clientCredentials scheme with an EMPTY scopes map, and the LiveRamp Service Account token
  request documents exactly one scope value, `openid`. Authorization is carried by the service
  account itself (provisioned per organization by a LiveRamp representative) and by the LR-Org-Id
  header, not by OAuth scopes. Recorded as an honest near-absence rather than an invented scope
  list.
schemes:
- name: application
  source: openapi/liveramp-clean-room-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.habu.com/v1/oauth/token
- name: LiveRamp Service Accounts
  source: https://developers.liveramp.com/activation-api/reference/oauth2defaultv1token
  flows:
  - flow: password
    tokenUrl: https://serviceaccounts.liveramp.com/authn/v1/oauth2/token
scopes:
- scope: openid
  description: >-
    The only scope value documented in the LiveRamp Service Account token request. Yields an
    OIDC id_token alongside the bearer access_token.
  flows:
  - password
  sources:
  - https://developers.liveramp.com/activation-api/reference/oauth2defaultv1token
authorization_model:
  style: service-account
  tenant_header: LR-Org-Id
  description: >-
    Access is bounded by the service account a LiveRamp representative issues, plus the LR-Org-Id
    header that names the customer organization the call acts on behalf of. There is no
    consent-screen scope selection surface.

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/liveramp-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.

GitHub Google LinkedIn

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