Status and error codes¶
Use the HTTP status together with the endpoint’s response body to decide the next action. A successful HTTP status does not establish that an asynchronous resource has reached its terminal state.
Status |
Check first |
|---|---|
|
Request fields, incompatible credentials, and endpoint-specific validation. |
|
Credential value, header name, and current environment. |
|
Model visibility, workspace membership, role, and resource permissions. |
|
Complete base URL, product prefix, and resource ID from the current environment. |
|
Bounded retry suitability and diagnostic context. |
Last updated on