Skip to main content
Card class: Hero • Category: Shipping & Courier

​
At a glance

Days until your DHL InExpress API authentication credentials expire. The “is the integration about to break” gauge, when this hits zero, label generation, tracking pulls, and claims sync all stop until you renew. The card alerts at 14 days remaining to give finance and ops time to coordinate the renewal.
What it countsexpiryTimestamp - now() for the active OAuth credential or API key on the connector. Refreshes every poll cycle (~5 minutes).
Credential typeDHL InExpress uses long-lived API keys (typically 12 to 24 month validity) plus short-lived OAuth tokens (refreshed automatically). The card surfaces the long-lived expiry, the one that requires manual renewal.
Renewal scopeAPI key renewal is a manual step on MyDHL+ → Developer Portal → API Credentials. The renewed key has to be pasted into the Vortex IQ connector configuration; auto-rotation is not currently supported.
Multi-accountMerchants with multiple DHL accounts have one credential per account. The card surfaces the soonest-expiring; per-account view is on the roadmap.
Brexit / customs scopeNot applicable, credentials are account-level, not lane-specific.
CurrencyThis card is unitless (days).
Time windowRT (real-time, polls every 5 minutes)
Alert trigger<14 days. DHL InExpress doesn’t auto-renew; the integration breaks the moment the key expires. 14 days is enough lead time to coordinate the renewal across DHL portal access and Vortex IQ config.
Rolesowner, operations

​
Calculation

Calculated automatically from your DHL InExpress data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A UK retailer running InExpress for 18 months. Reading taken at 09:00 GMT on 12 Mar 26.
AccountAPI key expiryDays remainingStatus
Primary GB account (created 14 Mar 25)14 Mar 262Critical
Secondary IE account (created 02 Sep 25)02 Sep 26174Healthy
The card reads 2 days (the soonest expiry across all credentials). The alert at <14 days is tripped and has been since 28 Feb 26. What this means in practice:
  1. At 02:00 GMT on 14 Mar 26, label generation will start failing on the primary account. The Vortex IQ → DHL handoff returns 401 Unauthorized. Existing labels remain valid; new label requests fail. Tracking pulls also fail.
  2. Customer-facing impact escalates after a few hours. New orders can’t be shipped. Support tickets pile up.
  3. The renewal is a 15 to 30 minute job if you have MyDHL+ access. Log into MyDHL+ Developer Portal, generate a new API key, paste it into the Vortex IQ connector settings, save. Test by attempting one label generation.
  4. DHL doesn’t email you the expiry warning by default. Check your MyDHL+ notification settings; many merchants have these turned off and don’t realise until the integration breaks.
  5. The secondary IE account is fine for ~6 months. No action needed there. Stagger renewals so they don’t both fall in the same week, pick a calm month for the next regeneration to avoid clashing with peak season.
Action items right now: (1) check who has MyDHL+ admin access; (2) book a 30-minute slot in the next 48h to renew; (3) test label generation immediately after renewal to confirm the new key is valid.

​
Sibling cards merchants should reference together

Token expiry is an integration-health card. Pair with downstream impact cards:
CardWhy pair itWhat the combination tells you
API Error RateDownstream symptom. Expired token = 401 errors.If API errors spike on the day of expiry, the token didn’t get renewed in time.
Label Generation SuccessDownstream symptom. No token, no labels.A flat-zero on label success rate after expiry confirms the integration is offline.
ShipmentsDownstream symptom (delayed). Volume cliff happens 24 to 48 hours after expiry once warehouse cutoff hits.If shipment volume drops sharply day-after expiry, that’s the operational impact.

​
Reconciling against the vendor’s own dashboard

Where to look in DHL InExpress’s own dashboard: MyDHL+ Developer Portal → My Apps → API Credentials. Each credential has an “Expires on” date. The card surfaces the same value as days-remaining. Why our number may legitimately differ from the developer portal:
ReasonDirectionWhy
Time zone±1 dayThe portal shows the date in your portal time zone; the card uses UTC days-remaining. May differ by 1 calendar day at the boundary.
Multiple credentialsEitherIf you have multiple API keys (e.g. test + production) configured, the card surfaces the soonest-expiring of those Vortex IQ is using; the portal lists all.
Recently renewedCard lower brieflyAfter renewal, the card needs one poll cycle (~5 minutes) to pick up the new expiry.
Cross-connector reconciliation: Not applicable, credentials are connector-specific. Each connector has its own auth_token_expiry_days card; they do not reconcile across connectors.

​
Known limitations / merchant FAQs

Why doesn’t DHL InExpress auto-renew the API key? Most carrier APIs use long-lived keys for security and audit reasons; auto-rotation would require trust delegation that DHL’s developer programme does not currently grant. The OAuth refresh token handles short-lived bearer rotation automatically; the underlying API key is the manual piece. Can I renew before expiry to avoid the gap? Yes, you can generate a new key at any time on MyDHL+. The old key remains valid until its expiry; pasting the new key into the Vortex IQ connector switches over immediately. Best practice: renew at the 30-day-before-expiry mark to avoid any same-day pressure. The card shows 14 days but the developer portal shows 15. Why? Time zone. The portal uses your portal-account time zone; the card uses UTC days-remaining. Difference is 1 calendar day at the boundary. Trust the lower number; renew at whichever shows under 14 first. Is the connector going to auto-recover after I renew? Yes, on the next poll cycle (~5 minutes). No restart required. Test by triggering a label print after the poll cycle to confirm. Should I rotate the key during peak (BFCM)? No. Schedule rotation at least 30 days before BFCM and at least 14 days after. A failed rotation during peak is a service-level event you cannot afford. Who owns the renewal in my organisation? Usually IT or operations, with a calendar reminder ~30 days before expiry. The card alert is the safety net for a missed reminder. The integration is offline already, the count is 0 or negative. What now? Renew the key on MyDHL+ immediately, paste into the connector, wait one poll cycle, test a label print. The integration recovers within minutes of the new key being saved. Catch up on backlog labels via the connector’s manual retry queue.

​
Tracked live in Vortex IQ Nerve Centre

Days to Token Expiry is one of hundreds of KPI pulses Vortex IQ tracks across DHL InExpress and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.