Error reference

no_availability

The listing exists, but the requested STAY is not bookable — at least one night between checkIn and checkOut is already taken, so the platform quotes no price for that range. This is a true answer about the property’s calendar, not an upstream failure.

HTTP 404not_foundNot retryable0 credits

HTTP 404error.type = not_found

How to fix it

Try different dates, or call /v1/availability first to find open ranges before pricing them. Not retryable — the same dates will keep returning this. The call is never billed.

Example response

404 not_found

// HTTP 404
{
  "error": {
    "type": "not_found",
    "code": "no_availability",
    "message": "The listing exists, but the requested STAY is not bookable — at least one night between checkIn and checkOut is already taken, so the platform quotes no price for that range. This is a true answer about the property’s calendar, not an upstream failure.",
    "param": null,
    "requestId": "req_…",
    "creditsCharged": 0,
    "retryable": false,
    "docUrl": "https://stayingapi.com/docs/errors/no_availability"
  }
}

This error is free

Like every StayingAPI error, no_availability returns creditsCharged: 0. You are never billed for a failed, empty, blocked or not-found call.

See the full error catalog or the response envelope. The canonical URL for this page is https://stayingapi.com/docs/errors/no_availability.