Request logs
Path: /org/logs
Audience: members and administrators. Aggregates are in Usage; balance movements in Balance and ledger.
What you can see
Enterprise records in reverse chronological order, for questions like “who made this call, with which model, and what did it cost”.
Type filters
| Type | Meaning |
|---|---|
| All | No filter |
| Consumption | Charges from normal calls |
| Errors | Failed requests |
| Refunds | Post-settlement refunds |
| Top-ups | Enterprise balance credits |
Whether the “Errors” filter has records depends on whether the platform has error logging enabled. When it is off — the default — an empty Errors view does not mean no request failed; it means failures were not recorded. To diagnose a failure, prefer the error code the caller received (see the FAQ).
Export
CSV export keeps the current filters: narrow the range first, then export exactly that set. Timestamps are emitted in Asia/Shanghai (Beijing time).
Known boundaries
- Top-ups, system and administrative records are not attributed to an enterprise, so they do not appear in enterprise request logs. For enterprise balance credits, use Balance and ledger.
- Platform-side operations do not appear in enterprise Audit records either — audit covers the enterprise’s own scope.
To be completed: how long records are retained. Retention is platform configuration and no unified figure has been published; confirm with the platform before relying on it for compliance.
Related
- Usage — read the trend first, then come here for specifics
- Audit records — administrative actions