> ## 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.

# API Error Rate, Japan Post

> API Error Rate for Japan Post stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Operational Health](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Share of calls to the Japan Post API that returned an error (4xx or 5xx) over the trailing 24 hours. It is the integration-health pulse for the connector: when it climbs, label generation, tracking lookups, and claim queries are failing somewhere between Vortex IQ and Japan Post. The alert fires above 2 percent, which for a busy despatch operation is the line between background noise and a real fault.

## What it tracks

The card computes `failed_calls ÷ total_calls` across all Japan Post API endpoints (label and manifest generation, tracking, claims, billing) over the rolling 24-hour window, expressed as a percentage. A sustained reading above the `>2%` threshold usually has one of three causes: an expired or revoked auth token (4xx, cross-check [Days to Token Expiry](/nerve-centre/kpi-cards/japan-post/days-to-token-expiry)), a Japan Post infrastructure outage (5xx, cross-check [Japan Post Tracking API Unavailable / 5xx](/nerve-centre/kpi-cards/japan-post/japan-post-tracking-api-unavailable-5xx)), or malformed request payloads such as bad address or weight data. A 24-hour window is short enough to catch an outage quickly but long enough to smooth single-minute blips. The downstream symptom shows on [Label Generation Success](/nerve-centre/kpi-cards/japan-post/label-generation-success): when error rate spikes, label success drops in lock-step. Use the error class to decide the action: a 4xx storm is usually yours to fix (token, payload), a 5xx storm is Japan Post's to fix and the right move is to wait and retry rather than re-authenticate.

## Reconciling against the source

There is no merchant-facing error-rate dashboard at Japan Post; reconcile by reading the HTTP status breakdown in your own integration logs against the [Japan Post Business Customer Portal](https://www.post.japanpost.jp/biz/) service-status notices, and split 4xx (your token or payload) from 5xx (Japan Post infrastructure). Timestamps in Japan Post tooling are carrier-local (JST).

***

### Tracked live in Vortex IQ Nerve Centre

*API Error Rate* is one of hundreds of KPI pulses Vortex IQ tracks across Japan Post 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.