La Poste Groupe · OAuth Scopes

La Poste Groupe OAuth Scopes

OAuth 2.0 derived

La Poste Groupe 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 /.

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.

CompanyLogisticsShippingPackage TrackingPostalAddressesGeocodingOpen DataDocument ManagementIdentityGovernmentFrance

Scopes: 0 Flows: authorizationCode, implicit Method: derived

OAuth endpoints

Authorization URL
/ https://test.com

Token URL
/

Flows
authorizationCodeimplicit

Scopes (0)

La Poste Groupe 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

generated: '2026-09-02'
method: derived
source: openapi/la-poste-groupe-digiposte-openapi.json, openapi/la-poste-groupe-lettre-recommandee-en-ligne-openapi.json
schemes:
- name: oauth2
  source: openapi/la-poste-groupe-digiposte-openapi.json
  flows:
  - flow: authorizationCode
    authorizationUrl: /
    tokenUrl: /
- name: default
  source: openapi/la-poste-groupe-lettre-recommandee-en-ligne-openapi.json
  flows:
  - flow: implicit
    authorizationUrl: https://test.com
scopes: []
scope_count: 0
finding: >-
  Both oauth2 declarations in this estate carry an EMPTY scopes map, and no scope or
  permission reference page exists on developer.laposte.fr,
  faq.developer.laposte.fr or documentation-okapi.laposte.fr (searched 2026-09-02).
  Digiposte v3 uses client_credentials with no scope narrowing - a partner token is
  all-or-nothing across memberships, certified deposit, organisation safes and
  sharing. Lettre recommandee en ligne's oauth2 block is a springdoc placeholder
  pointed at https://test.com and is not a real authorization surface.
  Authorisation on the rest of the estate is not OAuth at all: it is a per-plan
  X-Okapi-Key, where the PLAN (not a scope) decides which routes and methods the
  key may call - the portal exposes that as filteredRoutes / filteredMethods /
  filteredResourcesCount on each plan.

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/la-poste-groupe-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 email required.

GitHub Google LinkedIn

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