Skip to content
ScoutingAPI
Docs

Error reference

invalid_date_range

checkOut / endDate is not strictly after checkIn / startDate.

HTTP 400invalid_requestNot retryable0 credits
HTTP 400error.type = invalid_request

How to fix it

Ensure the end date is after the start date.

Example response

400 invalid_request
// HTTP 400
{
  "error": {
    "type": "invalid_request",
    "code": "invalid_date_range",
    "message": "checkOut / endDate is not strictly after checkIn / startDate.",
    "param": "checkOut",
    "requestId": "req_…",
    "creditsCharged": 0,
    "retryable": false,
    "docUrl": "https://scoutingapi.com/docs/errors/invalid_date_range"
  }
}

This error is free

Like every ScoutingAPI error, invalid_date_range 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://scoutingapi.com/docs/errors/invalid_date_range.