Skip to main content
Metrics type: Key Metrics • Category: Shipping & Courier

​
At a glance

Days remaining until the Evri API authentication token currently used by the Vortex IQ connector will expire. Evri’s web service issues an OAuth-style access token, typically 90 days lifetime on the standard merchant API. When the token expires every label-print, tracking-pull, and shipment-status webhook stops; the connector goes silent. This card is the early-warning siren.

​
Calculation

Calculated automatically from your Evri (formerly Hermes UK) 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 DTC clothing brand running Evri Standard, one Evri account, automatic refresh-token rotation enabled. Reading taken at 09:00 BST on 12 Mar 26. The reading on 12 Mar 26 is 76 days, healthy steady state. Five things to notice:
  1. Auto-rotation should fire 14 days before expiry. Vortex IQ’s connector logic refreshes proactively. If the number sits at 14 for more than 24 hours, rotation has failed and is not retrying.
  2. Failed refresh causes are usually credential changes. Either the Evri account password was changed without updating the connector, or Evri rotated their OAuth client secret on their side (rare).
  3. Below 3 days is incident-priority. Stop label printing during the final hours; orphan labels (Evri has tracking number but dispatch system has no record) are messy to clean up.
  4. Legacy Hermes-era accounts may not support refresh tokens. Accounts onboarded before March 2022 sometimes need manual re-authentication every 90 days; check the account’s API settings page.
  5. The card does not auto-rotate. It surfaces the gap. Rotation is the connector’s job; the card is the alarm.

​
Sibling cards merchants should reference together

Token expiry is an operational-health metric. Pair with these:

​
Reconciling against the vendor’s own dashboard

Where to look in Evri’s own portal: Evri Business Portal → API Settings → Active Tokens. The portal lists active OAuth tokens with issued-at and expires-at timestamps. Why our number may legitimately differ from Evri’s portal: Internal identity (within Evri): (token_expiry → 0) → (api_error_rate spikes 401) → (label_generation_success → 0) → (shipments_total → 0 from this minute). Sequential failure cascade. Cross-connector reconciliation:
Documentation cross-reference (token-expiry on other connectors).

​
Known limitations / merchant FAQs

The card says 18 days, do I need to do anything? Not yet, verify auto-rotation is configured. Healthy steady-state is 60 to 90 days. If the number sits at 18 for more than 24 hours without ticking up after a refresh job, rotation has failed. My token expired and labels stopped, what now? Re-authenticate from the connector settings page; click “Re-connect Evri” and complete the OAuth flow. New token issues immediately, card resets to ~89 days. Reprocess any orphan labels. Confirm webhook ingestion resumed. Auto-rotation is enabled but the token still expired, why? Three causes. (1) Evri account password changed without updating connector. (2) OAuth client secret rotated by Evri during platform updates. (3) The legacy account doesn’t actually support refresh-token grant, requires manual re-auth. My account is from the Hermes era pre-2022, does it support refresh tokens? Most do, but some legacy accounts onboarded before the API rebrand still require manual re-authentication. Check API Settings page; if “automatic rotation” is not available, set a calendar reminder for 80 days from each manual re-auth. Multiple Evri accounts, how do I see all expiries? Each account is a separate connector instance with its own card. Filter the dashboard by connector instance to see all expiry numbers. Does this card warn me 14 days in advance? Yes if alerting is configured. Email / Slack / Teams notification on the threshold trip. Why does the card sometimes show negative numbers? Token has expired and rotation has not succeeded. Connector is failing. Re-authenticate immediately. How does this interact with Evri’s platform maintenance windows? Evri publishes scheduled maintenance windows on its developer portal. Auth endpoint may briefly return 503 during maintenance; the card may show a refresh failure during the window. Check the maintenance schedule before treating as a real incident.

​
Tracked live in Vortex IQ Nerve Centre

Days to Token Expiry is one of hundreds of KPI pulses Vortex IQ tracks across Evri (formerly Hermes UK) 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.