Habu · OAuth Scopes

Habu OAuth Scopes

OAuth 2.0 searched

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

CompanyData Clean RoomData CollaborationAdvertisingPrivacyIdentityMarketingAnalytics

Scopes: 0 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://api.habu.com/v1/oauth/token

Flows
clientCredentials

Scopes (0)

Habu 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://developers.liveramp.com/clean-room-api/reference/configuring-a-clean-room-api-user

Source

OAuth Scopes

generated: '2026-08-12'
method: searched
source: openapi/habu-clean-room-api-openapi.yml (components.securitySchemes.application) plus a search
  of the Clean Room API documentation for a scopes/permissions reference.
docs: https://developers.liveramp.com/clean-room-api/reference/configuring-a-clean-room-api-user
schemes:
- name: application
  source: openapi/habu-clean-room-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.habu.com/v1/oauth/token
scope_count: 0
scopes: []
finding: 'The OAuth 2.0 client-credentials flow declares scopes: {} and LiveRamp publishes no scope or
  permission reference for the Clean Room API. Authorization is enforced by CLEAN ROOM ROLE (getCleanroomRoles
  / addCleanroomUser / configureCleanRoomQuestionPermissions), which is data in the platform rather than
  a claim in the token. An agent therefore cannot reason about what a token may do before calling — it
  can only discover it from a 403.'

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