variants
Localized specs for one variant
Spec values and units resolved into the requested language. In the demo tier this is answered from the blob, for the 40 cars, in all 20 languages.
get/variants/{id}/specs
Request
- Base URL: https://api.cars-data.com/v1
- URL: https://api.cars-data.com/v1/variants/{id}/specs
- Auth: one of:
- API key in header X-Api-Key
- HTTP bearer
- none
Path parameters
idstring required
Example:v_1a2b3c4d
Opaque variant token, v_ followed by 8 hex characters.
Query parameters
locale'ar' | 'bg' | 'cs' | 'da' | 'de' | 'el' | 'en' | 'es' | 'fr' | 'hr' | 'hu' | 'it' | 'no' | 'pl' | 'pt' | 'ro' | 'sk' | 'sr' | 'sv' | 'tr'
One of the 20 published languages. Anything else — including a language the site does not publish — falls back to en silently.
Headers
PAYMENT-SIGNATUREstring
x402 v2 payment proof, base64 JSON, built by an x402 client from the PAYMENT-REQUIRED header of a previous 402. Only on the two paid routes, and only without a key — a request with a key ignores it.
Response
OK. Paid with x402, it also carries PAYMENT-RESPONSE.
Example response
{
"data": {
"variant_id": "v_1a2b3c4d"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.