> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Days to Token Expiry, Evri (formerly Hermes UK) > Days to Token Expiry for Evri (formerly Hermes UK) stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Shipping & Courier](/nerve-centre/connectors#connectors-by-type) ## 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. | | | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `DATEDIFF(token_expiry_at, NOW())` on the active Evri API credential. | | **API endpoint** | Evri's auth endpoint within the post-rebrand REST API surface. The card refreshes every 15 minutes. | | **What gets blocked at expiry** | Label generation stops, tracking refreshes go stale, shipment-status webhooks stop ingesting. | | **Token rotation** | Evri supports automated rotation via refresh-token grant on most account tiers. Some legacy Hermes-era accounts (pre-2022 rebrand) require manual re-authentication. | | **Service level scope** | Per Evri account / sub-account. | | **Time window** | `RT` (real-time). | | **Alert trigger** | `<14 days` warn, `<3 days` critical. | | **Currency** | n/a. | | **Returns / RTO** | n/a. | | **Roles** | owner, operations | ## 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. | State | Days to expiry | Status | Action | | -------------------- | -------------- | ------------ | ------------------------------------------------- | | Healthy steady state | 76 | Green | None. Rotation refreshes \~30 days before expiry. | | Approaching renewal | 18 | Green | None yet. Refresh fires at day 14. | | Refresh failed | 11 | Amber | Investigate refresh log. Run manual refresh. | | Refresh failed twice | 4 | Red | Incident. Re-authenticate manually. | | Expired | -1 | Red (silent) | Connector silent. Label printing stopped. | 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: | Card | Why pair it | What the combination tells you | | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | [API Error Rate](/nerve-centre/kpi-cards/hermes-evri/api-error-rate) | A token approaching expiry produces 401 / 403 responses on edge calls. | Spike in API errors when this card reads \<14 days is the rotation about to fail. | | [Label Generation Success](/nerve-centre/kpi-cards/hermes-evri/label-generation-success) | First-line operational impact of token failure. | If label-success drops while expiry is still positive, issue is upstream of auth. | | [Shipments Total](/nerve-centre/kpi-cards/hermes-evri/shipments) | Drop to zero new shipments concurrent with expiry confirms outage. | Useful for confirming the gap; not a leading indicator. | | Cross-connector: Token-expiry cards on other connectors | Each connector has its own auth credential. | Panel of all token cards is the single-glance health dashboard. | ## Reconciling against the vendor's own dashboard **Where to look in Evri's own portal:** [Evri Business Portal](https://www.evri.com/) → **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:** | Reason | Direction | Why | | --------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | **Cache lag** | Ours stale by 15 minutes | Card refreshes every 15 minutes. | | **Token revoked but not expired** | Portal shows expired, ours positive | A revoked token is immediately blocked at API level but the expires-at field still shows the original future date. | | **Multiple tokens** | Either | Failed-refresh leaves an old + new token state; card reads the active one. | | **Time zone of expires-at** | Boundary days off | Portal in UK local; card uses UTC. | | **Legacy Hermes-era accounts** | Either | Pre-rebrand auth tokens behave differently from current OAuth flow. | **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. * [`hermes_evri.her_api_error_rate`](/nerve-centre/kpi-cards/hermes-evri/api-error-rate) * [`hermes_evri.her_label_generation_success`](/nerve-centre/kpi-cards/hermes-evri/label-generation-success) **Cross-connector reconciliation:** | Card | Expected relationship | Causes of legitimate divergence | | -------------------------------------- | --------------------- | -------------------------------------- | | Token-expiry cards on other connectors | Independent. | Each connector has its own credential. | *** *Documentation cross-reference (token-expiry on other connectors).* * [`royal_mail.roy_auth_token_expiry_days`](/nerve-centre/kpi-cards/royal-mail/days-to-token-expiry) * [`dpd.dpd_auth_token_expiry_days`](/nerve-centre/kpi-cards/dpd/days-to-token-expiry) * [`apc.apc_auth_token_expiry_days`](/nerve-centre/kpi-cards/apc/days-to-token-expiry) ## 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.