Pitney Bowes · OAuth Scopes

Pitney Bowes OAuth Scopes

OAuth 2.0 derived

Pitney Bowes 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://shipping-api.pitneybowes.com/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.

MailingShippingFortune 1000
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://shipping-api.pitneybowes.com/oauth/token
Flows
clientCredentials

Scopes (0)

Pitney Bowes 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.

Pitney Bowes Shipping APIs use the OAuth client_credentials grant with a Base64-encoded API key and secret, and do not publish user-selectable OAuth scopes; access is tied to the developer account credentials (https://docs.shippingapi.pitneybowes.com/api/post-oauth-token.html).

📄 Provider scope reference: https://docs.shippingapi.pitneybowes.com/api/post-oauth-token.html

Source

OAuth Scopes

pitney-bowes-scopes.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/pitney-bowes-openapi.yml
docs: https://docs.shippingapi.pitneybowes.com/api/post-oauth-token.html
note: Pitney Bowes Shipping APIs use the OAuth client_credentials grant with a Base64-encoded
  API key and secret, and do not publish user-selectable OAuth scopes; access is tied to
  the developer account credentials (https://docs.shippingapi.pitneybowes.com/api/post-oauth-token.html).
schemes:
- name: oauth2
  source: openapi/pitney-bowes-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://shipping-api.pitneybowes.com/oauth/token
scopes: []