OpenAI reported a delay affecting the ChatGPT Compliance API Costs API. The status history records investigation beginning on November 17, monitoring after a fix, and resolution on November 18. The incident is limited to the named component. It is not evidence of an API-wide outage, missing customer spend or a frontend defect.
Treat freshness as a first-class field
If a client dashboard consumes costs data, display the last successful collection time, the source window and a freshness state. During a provider delay, do not turn an empty or old response into zero cost. Keep the last known value visibly separate from newly reconciled records.
Define the reconciliation path
Record the API request window, response timestamp, local ingestion time, page or cursor state and the dashboard range shown to users. When the provider reports recovery, replay the bounded missing interval if the endpoint supports it. Compare record counts and totals with the pre-incident checkpoint. Preserve the original delayed state so an auditor can see what the dashboard showed at the time.
Use idempotent keys for account, period, model or usage record as appropriate to the response contract. Do not blindly append a replay if the API can return the same record twice. If the provider has not confirmed completeness, label the dashboard as pending reconciliation and route the decision to the data owner.
Decide what the frontend should show
The client-facing decision is whether to keep the dashboard visible with a freshness warning, temporarily hide affected totals, or provide a manual report. Keep billing or contract decisions separate from an operational display until the delayed interval is reconciled. If a manual export is used, record who produced it and what interval it covers.
Applicability and limits
This article applies only to systems using the OpenAI Compliance API Costs API during the reported incident window. It does not claim lost data, incorrect billing or an affected customer. The practical handoff is a freshness record, replay plan, idempotency check and reconciliation sign-off.
Primary source: OpenAI Status - Costs API data is delayed.