Vehicle endpoints /list and /vehicle return `null` for property `option_codes`

[Darko]

Hey!

When fetching a vehicles list, or a single vehicle from the GET /api/1/vehicles/{id} or GET /api/1/vehicles the property option_codes is returned with a null value.

Is this intentional, and if so, which endpoint should be used to fetch the option codes for a car?

[rawmean]

They stopped populating option_codes correctly even in the legacy API. Use vehicle_config instead

[aaronpkahn]

@Darko that is confusing; this is a legacy field, and we'll remove it. There is a new option codes endpoint coming in the next few weeks.

[Darko]

@aaronpkahn that is awesome! Is there a particular discord channel or somewhere else where we can monitor change logs?

[itsMeDavidV]

There is a new option codes endpoint coming in the next few weeks.

Much needed, thank you!

[aaronpkahn]

For now we'll post updates here: https://developer.tesla.com/docs/fleet-api#announcements-amp-api-changelog, or if we move to somewhere else we'll link from the documentation

[Darko]

@aaronpkahn Any update on this? It's been a few weeks? 😅

[Whirlwind]

It still not works in china developer website.