API preview
Error shape
Supported APIs should use appropriate HTTP status codes together with stable machine-readable error identifiers and a safe human-readable explanation. Error bodies must not leak credentials, secrets or cross-tenant information.
Client behavior
- Correct validation errors before retrying.
- Refresh or replace invalid credentials rather than repeatedly retrying authentication failures.
- Treat authorization failures as a permissions problem, not a signal to probe other resources.
- Apply documented retry guidance only to transient failures.
- Log request correlation identifiers when Wewed provides them.