API returning wrong option codes

[DrJFoster]

I thought I'd got this working as the API returns the VIN and the name of my car but the option codes are for a completely different car. As its all within the JSON response it seems like its the API reply and not me. Can anyone confirm if they're seeing the same?

Thanks

 

[jasonhr13]

I am seeing the same thing here. Option codes are for model 3, and I have a model S

 

[DrJFoster]

Thanks Jason, we're either both doing it wrong, Tesla have a problem with the API or there are new client id and client_secrets

 

[PatrickCH4313]

I checked the option codes of my Model S, but they changed for a Model 3 (MDL3) .

 

[KWReid]

I checked the option codes of my Model S, but they changed for a Model 3 (MDL3)

I'm seeing something similar. Took my X in for to fix a rattle, they upgraded FSD computer to HW3. I went to the API to check on the optino codes and... MDL3? APF3? That's not my car. Other data on the vehicles call shows my correct car name. Details call seems to grab my cars details, but the get-vehicles call option codes aren't correct.

 

[PatrickCH4313]

I'm seeing something similar. Took my X in for to fix a rattle, they upgraded FSD computer to HW3. I went to the API to check on the optino codes and... MDL3? APF3? That's not my car. Other data on the vehicles call shows my correct car name. Details call seems to grab my cars details, but the get-vehicles call option codes aren't correct.

Still wrong data today for my Model S.

 

[KWReid]

Still wrong data today for my Model S.

I'm not expecting it to be corrected. It looks like it's being giving me the Model 3 response since before September.

 

[brianman]

Option codes have been having issues for a while on the REST API. Been mentioned on the REST API thread multiple times.