For AI agents: a documentation index is available at llms.txt. Markdown versions are available via .md routes or Accept: text/markdown content negotiation.

Documentation Get Started

Updates

←Back to changelog

JULY 8, 2026

Recall Availability Reason

ApiRecalls

Recalls responses now include not_available_reason when the data source explains why a remedy is not yet available.

Added

data.recalls[].not_available_reason on Vehicle Recalls (GET /v1/recalls, API documentation). When the upstream source provides a reason that a remedy is not yet available, that value is now returned instead of being dropped during response mapping. The field is null when the source does not supply a reason.

Notes

Additive, backward-compatible change. Existing clients can ignore the new field.
Present when the primary US recall source supplies a reason for the VIN; other sources may omit it or return null.

JULY 8, 2026

Recall Availability Reason

ApiRecalls

Recalls responses now include not_available_reason when the data source explains why a remedy is not yet available.

Added

data.recalls[].not_available_reason on Vehicle Recalls (GET /v1/recalls, API documentation). When the upstream source provides a reason that a remedy is not yet available, that value is now returned instead of being dropped during response mapping. The field is null when the source does not supply a reason.

Notes

Additive, backward-compatible change. Existing clients can ignore the new field.
Present when the primary US recall source supplies a reason for the VIN; other sources may omit it or return null.

←PreviousNew Docs SiteA dedicated documentation experience with guided onboarding, an interactive API reference, and full product…Next→CarsXE on RapidAPITwelve CarsXE endpoints are now live on the RapidAPI marketplace, each with its own playground.

On this page

←Back to changelog

JULY 8, 2026

Recall Availability Reason

ApiRecalls

Recalls responses now include not_available_reason when the data source explains why a remedy is not yet available.

Added

data.recalls[].not_available_reason on Vehicle Recalls (GET /v1/recalls, API documentation). When the upstream source provides a reason that a remedy is not yet available, that value is now returned instead of being dropped during response mapping. The field is null when the source does not supply a reason.

Notes

Additive, backward-compatible change. Existing clients can ignore the new field.
Present when the primary US recall source supplies a reason for the VIN; other sources may omit it or return null.

JULY 8, 2026

Recall Availability Reason

ApiRecalls

Recalls responses now include not_available_reason when the data source explains why a remedy is not yet available.

Added

data.recalls[].not_available_reason on Vehicle Recalls (GET /v1/recalls, API documentation). When the upstream source provides a reason that a remedy is not yet available, that value is now returned instead of being dropped during response mapping. The field is null when the source does not supply a reason.

Notes

Additive, backward-compatible change. Existing clients can ignore the new field.
Present when the primary US recall source supplies a reason for the VIN; other sources may omit it or return null.

←PreviousNew Docs SiteA dedicated documentation experience with guided onboarding, an interactive API reference, and full product…Next→CarsXE on RapidAPITwelve CarsXE endpoints are now live on the RapidAPI marketplace, each with its own playground.

On this page