Ibotta · OAuth Scopes

Ibotta OAuth Scopes

OAuth 2.0 probed

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

CompanyConsumerCashbackRewardsRetail MediaCouponsLoyaltyShoppingAdvertisingPromotionsProduct SearchRetailAffiliatesCPG
Scopes: 0 Flows: Method: probed

Scopes (0)

Ibotta 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:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-12'
method: probed
source: https://auth.dashboard.ibotta.com/.well-known/openid-configuration
docs: null
summary: >-
  Ibotta's public Product API declares no OAuth 2.0 security scheme — it uses a single service
  bearer token with no scopes. The only scope surface Ibotta publishes anonymously is the
  scopes_supported list from the Auth0 tenant that fronts the IPN partner portal
  (auth.dashboard.ibotta.com). These are stock OIDC identity scopes for portal sign-in, NOT
  API authorization scopes for the Ibotta Performance Network partner APIs — those are not
  publicly documented. Recorded here as measured, not as an API permission model.
authorization_servers:
- issuer: https://auth.dashboard.ibotta.com/
  applies_to: Ibotta Performance Network partner portal (portal.ipn.ibotta.com)
  discovery: https://auth.dashboard.ibotta.com/.well-known/openid-configuration
  status: 200
  scope_kind: oidc-identity
  scopes:
  - name: openid
    description: Standard OIDC scope requesting an ID token.
  - name: profile
    description: Basic profile claims for the signed-in partner user.
  - name: offline_access
    description: Issues a refresh token for long-lived portal sessions.
  - name: name
    description: name claim.
  - name: given_name
    description: given_name claim.
  - name: family_name
    description: family_name claim.
  - name: nickname
    description: nickname claim.
  - name: email
    description: email claim.
  - name: email_verified
    description: email_verified claim.
  - name: picture
    description: picture claim.
  - name: created_at
    description: created_at claim (Auth0 extension).
  - name: identities
    description: Linked identity providers for the account (Auth0 extension).
  - name: phone
    description: phone_number claim.
  - name: address
    description: address claim.
  claims_supported:
  - aud
  - auth_time
  - created_at
  - email
  - email_verified
  - exp
  - family_name
  - given_name
  - iat
  - identities
  - iss
  - name
  - nickname
  - phone_number
  - picture
  - sub
api_scopes:
  documented: false
  note: >-
    No API authorization scopes are published for either the Ibotta Product API (bearer token,
    no scopes) or the IPN partner APIs (documentation is behind the partner portal login).

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