EV Charger API only providing limited values

I've recently received my EV Charger and have been trying to my wits end to get the API to provide my home assistant with all the information I need for automated charging. Specifically, I'm dying to access the vehicles SOC, to no avail.

The problem I've been encountering with the API is that it only seems to be spitting out 4 of the 22 datapoints I'd be expecting. https://givenergy.cloud/docs/api/v1#ev-charger-meter-data
The only measurands I get are 1, 4, 13, 21.

Standard caveat applies that I'm not well versed in advanced coding (I'd consider polling API's in a terminal advanced), so if there's something crucial I'm missing with my queries, please let me know. Below is a copy of the query, with appropriate information redacted.

curl --request GET \
--get "https://api.givenergy.cloud/v1/ev-charger/{EV UUID}/meter-data?start_time=2024-06-02T15%3A00%3A00Z&end_time=2024-06-02T16%3A00%3A00Z" \
--header "Authorization: Bearer {GivEnergy API KEY}" \
--header "Content-Type: application/json" \
--header "Accept: application/json"

Bumping this, as with multiple other attempts, I've not gotten any further with any of the other measurands.

LewisWatt Specifically, I'm dying to access the vehicles SOC

Does the charger have access to the vehicle's SoC ? It's not available through the basic AC charging wire protocol, though there are some moves to provide a higher level Comms mechanism.

Can you get the SoC using the car's API ?

DD Can you get the SoC using the car's API ?

Unfortunetely not yet. I'm dealing with the early adopters tax of the Volvo EX30, so it's lacking in some critical software areas, as most new products do these days.

I'm not well versed in the underlying capabilities of the comms protocol, but vehicle SoC isn't communicated? Seems a bit daft to include it in the charging API if it's not possible in the basic form. Could you provide a resource for me to read up on this higher level comms you're talking about?

LewisWatt Sure.
https://en.wikipedia.org/wiki/J1772#Signaling is my go-to reference for the low-level comms protocol, where the chargepoint uses a low-voltage PWM line to advertise how much power is available, and the car adjusts the resistance to ground to indicate its precesnce and intentions.

For the higher level protocol, https://en.wikipedia.org/wiki/ISO_15118 seems to be some sort of umbrella standard - I've not yet found a good summary of the higher-level protocols, of which "Plug'n'charge" is one client (for identifying a car for billing purposes ..?)
https://electroverse.octopus.energy/community/ev-blogs-and-guides/what-is-plug-and-charge
https://www.switch-ev.com/blog/basics-of-plug-and-charge
It would require that both car and chargepoint implement it.

SoC is certainly the sort of thing that could be communicated, but I'm not sure it is. (DC charging does of course communicate SoC and such things. Not sure if it uses the same standards.)

Probably have to pay for the actual ISO documents, so I've not seen details.

Oh, see also https://en.wikipedia.org/wiki/J1772#P1901_powerline_communication - not sure how that fits in.