BP · OAuth Scopes

BP OAuth Scopes

OAuth 2.0 searched

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

EnergyOilGasRenewablesDeveloper PlatformFleetFuel CardsMobilityRetail FuelEV Charging
Scopes: 0 Flows: Method: searched

Scopes (0)

BP 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://developer.fleet.bp.com/DE/getting-started

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-04'
method: searched
source: https://b2bid.bp.com/.well-known/openid-configuration (fetched, HTTP 200)
provider: BP
providerId: bp
docs: https://developer.fleet.bp.com/DE/getting-started
description: >-
  OAuth scopes advertised by BP's B2B identity host (b2bid.bp.com, ForgeRock AM), which is the
  authorization server behind the bp Open Fleet developer portal. These are the scopes the
  authorization server itself publishes as supported.
authorization_server: https://b2bid.bp.com/am/oauth2
scopes:
  - name: openid
    description: Standard OpenID Connect scope; requests an ID token.
    standard: true
  - name: profile
    description: Standard OIDC profile claims.
    standard: true
  - name: email
    description: Standard OIDC email claims.
    standard: true
  - name: phone
    description: Standard OIDC phone claims.
    standard: true
  - name: b2b-profile
    description: BP-specific scope carrying the B2B business-account profile.
    standard: false
  - name: b2b-consent
    description: BP-specific scope covering B2B consent state for the authenticated business user.
    standard: false
claims_supported:
  - sub
  - email
  - email_verified
  - phone
  - phone_verified
  - nickname
  - locale
  - appname
  - subname
  - external_id
  - custom_username
  - passwordless
notes:
  - >-
    The six bp Open Fleet resource OpenAPIs declare a bearer securityScheme with NO oauth2
    scopes block, so no per-operation scope requirements are published. The scopes above govern
    the portal sign-in flow, not fine-grained API authorization.
  - >-
    Authorization for the resource APIs is instead scoped by the credential's environment
    (sandbox vs production) and by the AuthorityIds / ParentIds the caller may query.
maintainers:
  - FN: Kin Lane
    email: info@apievangelist.com

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