DHL · OAuth Scopes

DHL OAuth Scopes

OAuth 2.0 derived

DHL publishes 3 OAuth 2.0 scopes via the clientCredentials and password flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the DHL API on a user’s behalf.

Tokens are issued from https://api-bat.dhlecs.com/auth/v4/accesstoken.

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.

FreightLogisticsShippingE-CommerceTrackingSupply ChainExpress DeliveryPostal ServicesParcel

Scopes: 3 Flows: clientCredentials, password Method: derived

OAuth endpoints

Token URL
https://api-bat.dhlecs.com/auth/v4/accesstoken https://api.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials https://api-sandbox.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials /parcel/de/account/auth/ropc/v1/token https://api-sandbox.dhlecs.com/auth/v4/accesstoken https://api-sandbox.dhl.com/ccc/v1/auth/accesstoken https://api-uat.dhl.com/parceluk/auth/v1/accesstoken https://api-dev.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials

Flows
clientCredentialspassword

Scopes (3)

Scope	Description	Flows
document-management		clientCredentials
pushAPI		clientCredentials
shipmentBooking		clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-11-12'
method: derived
source: openapi/dhl-container-dhl-ecommerce-americas-openapi.yml, openapi/dhl-dgf-document-openapi.yml,
  openapi/dhl-dgf-push-api-openapi.yml, openapi/dhl-dgf-shipment-booking-openapi.yml, openapi/dhl-dhl-parcel-de-returns-post-parcel-germany-openapi.yml,
  openapi/dhl-duty-tax-dhl-ecommerce-americas-openapi.yml, openapi/dhl-ecommerce-europe-openapi.yml,
  openapi/dhl-ecommerce-uk-openapi.json, openapi/dhl-econnect-beta-dhl-ecommerce-europe-openapi.yml,
  openapi/dhl-label-dhl-ecommerce-americas-openapi.yml, openapi/dhl-manifest-dhl-ecommerce-americas-openapi.yml,
  openapi/dhl-parcel-de-shipping-post-parcel-germany-v2-openapi.yml, openapi/dhl-product-finder-dhl-ecommerce-americas-openapi.yml,
  openapi/dhl-return-label-dhl-ecommerce-americas-openapi.yml, openapi/dhl-shipment-label-dhl-global-forwarding-openapi.yml,
  openapi/dhl-time-and-attendance-api-openapi.yml, openapi/dhl-tracking-dhl-ecommerce-americas-openapi.yml,
  openapi/dhl-tracking-webhooks-dhl-ecommerce-americas-openapi.yml
schemes:
- name: OAuth2
  source: openapi/dhl-container-dhl-ecommerce-americas-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-bat.dhlecs.com/auth/v4/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow
- name: oAuth2Token
  source: openapi/dhl-dgf-document-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials
- name: oAuth2Token_PROD
  source: openapi/dhl-dgf-push-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials
  description: Production URL
- name: oAuth2Token_SANDBOX
  source: openapi/dhl-dgf-push-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials
  description: Sandbox URL
- name: oAuth2Token
  source: openapi/dhl-dgf-shipment-booking-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials
- name: OAuth2
  source: openapi/dhl-dhl-parcel-de-returns-post-parcel-germany-openapi.yml
  flows:
  - flow: password
    tokenUrl: /parcel/de/account/auth/ropc/v1/token
  description: See https://developer.dhl.com/api-reference/authentication-api-post-parcel-germany.
    For the POST call to get a token, provide all parameters in the request body. Refer to the
    above link for details, or to the RFC describing OAuth2 Password Grant. After having obtained
    the access token, use this as Bearer token in the HTTP authorization header.
- name: OAuth2
  source: openapi/dhl-duty-tax-dhl-ecommerce-americas-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhlecs.com/auth/v4/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow.
- name: OAuth2
  source: openapi/dhl-ecommerce-europe-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhl.com/ccc/v1/auth/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow
- name: OAuth2
  source: openapi/dhl-ecommerce-uk-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-uat.dhl.com/parceluk/auth/v1/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow
- name: OAuth2
  source: openapi/dhl-econnect-beta-dhl-ecommerce-europe-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhl.com/ccc/v1/auth/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow
- name: OAuth2
  source: openapi/dhl-label-dhl-ecommerce-americas-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-bat.dhlecs.com/auth/v4/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow
- name: OAuth2
  source: openapi/dhl-manifest-dhl-ecommerce-americas-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhlecs.com/auth/v4/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow.
- name: OAuth2
  source: openapi/dhl-parcel-de-shipping-post-parcel-germany-v2-openapi.yml
  flows:
  - flow: password
    tokenUrl: /parcel/de/account/auth/ropc/v1/token
  description: See https://developer.dhl.com/api-reference/authentication-api-post-parcel-germany.
    For the POST call to get a token, provide all parameters in the request body. Refer to the
    above link for details, or to the RFC describing OAuth2 Password Grant. After having obtained
    the access token, use this as Bearer token in the HTTP authorization header.
- name: OAuth2
  source: openapi/dhl-product-finder-dhl-ecommerce-americas-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhlecs.com/auth/v4/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow
- name: OAuth2
  source: openapi/dhl-return-label-dhl-ecommerce-americas-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhlecs.com/auth/v4/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow
- name: oAuth2Token_SANDBOX
  source: openapi/dhl-shipment-label-dhl-global-forwarding-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials
- name: oAuth2Token_PROD
  source: openapi/dhl-shipment-label-dhl-global-forwarding-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials
- name: oAuth2ClientCredentials
  source: openapi/dhl-time-and-attendance-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-dev.dhl.com/auth/v1/token?response_type=access_token&grant_type=client_credentials
  description: OAuth2 token authentication
- name: OAuth2
  source: openapi/dhl-tracking-dhl-ecommerce-americas-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhlecs.com/auth/v4/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow
- name: OAuth2
  source: openapi/dhl-tracking-webhooks-dhl-ecommerce-americas-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-sandbox.dhlecs.com/auth/v4/accesstoken
  description: This API uses OAuth 2 with the client-credentials grant flow
scopes:
- scope: document-management
  flows:
  - clientCredentials
  sources:
  - openapi/dhl-dgf-document-openapi.yml
- scope: pushAPI
  flows:
  - clientCredentials
  sources:
  - openapi/dhl-dgf-push-api-openapi.yml
- scope: shipmentBooking
  flows:
  - clientCredentials
  sources:
  - openapi/dhl-dgf-shipment-booking-openapi.yml

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/dhl-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.