> ## Documentation Index
> Fetch the complete documentation index at: https://yn-c9bb3266.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# HTTP status codes

> Conventional codes Yuno returns, and what each means for your client.

Yuno follows REST conventions. The full code catalog and what each error means lives on [Error handling](/core-concepts/error-handling); this page is the at-a-glance map.

| Code                    | Meaning                                                                                                                                                          | What to do                                                                                                                   |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `200 OK`                | Request succeeded. May still carry `transaction_status: "PENDING"` for async flows — see [Async results and timeouts](/api-reference/conventions/async-results). | Process the response. Don't treat `PENDING` as final.                                                                        |
| `201 Created`           | Resource created (customer, payment, subscription, etc.).                                                                                                        | Store the returned `id`.                                                                                                     |
| `400 Bad Request`       | Validation error. The body details which field is wrong.                                                                                                         | Fix the request payload; do not retry as-is.                                                                                 |
| `401 Unauthorized`      | Missing or invalid `public-api-key` / `private-secret-key`.                                                                                                      | Check headers and the environment they target.                                                                               |
| `403 Forbidden`         | Auth succeeded but the action is not allowed (e.g., method not enabled for the account).                                                                         | Check Dashboard configuration.                                                                                               |
| `404 Not Found`         | Resource (or endpoint path) does not exist.                                                                                                                      | Verify IDs and URL.                                                                                                          |
| `409 Conflict`          | Duplicate detected via business key (e.g., reused `merchant_order_id` with conflicting payload).                                                                 | Inspect the existing resource before retrying.                                                                               |
| `429 Too Many Requests` | Rate limited by edge infrastructure.                                                                                                                             | Back off with jitter; honor `Retry-After` if present. See [Rate limits and retries](/api-reference/conventions/rate-limits). |
| `5xx`                   | Server-side failure. Safe to retry idempotent operations.                                                                                                        | Exponential backoff; report `request_id` to support if persistent.                                                           |