Invoices

[wannesdemaeght]

in the endpoints file there is some documentation about invoices.
I would like to automatically download my supercharging invoices, but can not get it to work.

"DOWNLOAD_CHARGING_INVOICE": {
    "TYPE": "GET",
    "URI": "bff/v2/mobile-app/charging/invoice/{uuid}",
    "AUTH": true
  },
  "DOWNLOAD_CHARGING_SUBSCRIPTION_INVOICE": {
    "TYPE": "GET",
    "URI": "bff/v2/mobile-app/charging/subscription/invoice/{invoiceId}",
    "AUTH": true
  },

using these endpoints needs a uuid or invoiceId, which I am trying to obtain with this endpoint:

  "MANAGE_GET_SUBSCRIPTION_INVOICES": {
    "TYPE": "GET",
    "URI": "bff/v2/mobile-app/subscriptions/invoices",
    "AUTH": true
  },

I am using this url:
https://owner-api.teslamotors.com/bff/v2/mobile-app/subscriptions/invoices

I am using GET, with requestheader application/json
params is: {"vehicle_id":"xxxxxxxxxxxx"} (id is correct, and works for all other api requests)

response is:
{"response":null,"error":"param is missing or the value is empty: vehicle_id","error_description":""}

I tried attaching the vehicle_id in the url, as needs to be done for other calls, but then I get a 404 error.
Any help?

[jamesdeck]

Curious about this too. I've tried for days to get supercharging costs from the API but have not gotten anywhere.

[idriskhenchil]

What headers are you sending?

[timdorr]

The BFF (backend-for-frontend) endpoints don't appear to authenticate the same way as the other vehicle endpoints do. I'd love to figure out what's going on here. Since they started obfuscating the JavaScript bundle in the app, it's gotten a little more difficult to figure out what the app is up to with these endpoints. I either need to packet sniff or just de-obfuscate the JS bundle, but we should probably focus a bit on figuring out how to call these endpoints.

[idriskhenchil]

The BFF (backend-for-frontend) endpoints don't appear to authenticate the same way as the other vehicle endpoints do. I'd love to figure out what's going on here. Since they started obfuscating the JavaScript bundle in the app, it's gotten a little more difficult to figure out what the app is up to with these endpoints. I either need to packet sniff or just de-obfuscate the JS bundle, but we should probably focus a bit on figuring out how to call these endpoints.

I've been able to packet sniff the app and I'll post that information here when I get a chance. Currently trying to packet sniff the actual car as well, but that's proving to be a little tricky so far.

[idriskhenchil]

Through checking the HTTP requests on the app, I've been able to get Invoice data through:

POST https://ownership.tesla.com/graphql?deviceLanguage=en&deviceCountry=US&vin={vin}&operationName=getChargingHistoryV2

The request is as follows:

POST /graphql?deviceLanguage=en&deviceCountry=US&vin={VIN}&operationName=getChargingHistoryV2 HTTP/1.1
Host: ownership.tesla.com
Accept: */*
Authorization: Bearer {token}
Accept-Encoding: gzip, deflate, br
Accept-Language: en
Cache-Control: no-cache
charset: utf-8
Content-Length: 1376
User-Agent: Tesla/1032 CFNetwork/1331.0.7 Darwin/21.4.0
Connection: keep-alive
x-tesla-user-agent: TeslaApp/4.8.1/5e1bfb8d0d/ios/15.4.1
Content-Type: application/json
x-txid: {x-txid}
Cookie: bm_sv={value}; ak_bmsc={value}

Which in turn will return roughly the following response

"charging": {
        "historyV2": {
          "data": [{
            "countryCode": "US",
            "programType": "PTSCH",
            "billingType": "IMMEDIATE",
            "vin": "{VIN}",
            "credit": null,
            "invoices": null,
            "chargeSessionId": "1234565-0-12345566",
            "siteLocationName": "LOCATION",
            "chargeStartDateTime": "2022-05-21T21:06:18-04:00",
            "chargeStopDateTime": "2022-05-21T21:46:20-04:00",
            "unlatchDateTime": "2022-05-21T21:46:21-04:00",
            "fees": [{
              "sessionFeeId": 1234566,
              "feeType": "CHARGING",
              "payorUid": null,
              "amountDue": null,
              "currencyCode": "USD",
              "pricingType": "PAYMENT",
              "usageBase": 61,
              "usageTier1": 10,
              "usageTier2": 12,
              "usageTier3": 17,
              "usageTier4": 0,
              "rateBase": 0.17,
              "rateTier1": 0,
              "rateTier2": 0,
              "rateTier3": null,
              "rateTier4": null,
              "totalTier1": 0,
              "totalTier2": 0,
              "totalTier3": 0,
              "totalTier4": 0,
              "uom": "kwh",
              "isPaid": true,
              "uid": 1234567,
              "totalBase": 10.37,
              "totalDue": 10.37,
              "netDue": 10.37,
              "status": "PAID"
            }],
            "vehicleMakeType": "TESLA",
            "sessionId": 1234567,
            "surveyCompleted": null,
            "surveyType": null,
            "postId": "0",
            "cabinetId": "vehicleMakeType",
            "din": ""
          }

I've only been able to view the request on the Tesla app. I'm still trying to figure out the header situation since I believe the x-txid or the cookies are single use.

If you are trying to get the actual PDF invoice instead, you can try:

GET https://ownership.tesla.com/mobile-app/charging/invoice/{INVOICE_ID}?deviceCountry=US&deviceLanguage=en&vin={VIN}

Which takes the same headers as above.

I do get a 401 when trying to make the request through a REST client, which I think may be related to this

[wannesdemaeght]

Any update on this? As there is no way to get my invoices (premium connectivity and supercharging) via mail, I’d like to access them via api…

[davidhodge]

I'm also curious if you found anything here. If i were to guess, the secret is in the cookies.

[idriskhenchil]

PDF invoices can be accessed with

GET https://ownership.tesla.com/mobile-app/charging/invoice/{INVOICE_ID}?deviceCountry=US&deviceLanguage=en&vin={VIN}

The inconvenience is that you'd need to know the INVOICE_ID.

[davidhodge]

thanks @idriskhenchil, we're still a bit stuck on getting the list of invoices. Presently getting back "Bad Request". Perhaps missing some headers.

[idriskhenchil]

@davidhodge Also the same error I get back when trying to access the request outside of the app. I used the same headers present in the mobile request as the headers I used in the client.

My wild guess is that I think the app may generate a client-side token that is used to validate where the request is coming from, in order to prevent the request from being made elsewhere. In a sense each request would only be single-use which could be why it works once when analyzing the request in the app, and doesn't work elsewhere.

[chadhurin]

@idriskhenchil @wannesdemaeght
I was able to get invoice history response off the app without cookies with this endpoint:
POST https://akamai-apigateway-charging-ownership.tesla.com/graphql?deviceLanguage=en&deviceCountry=US&ttpLocale=en_US&vin={vin}&operationName=getChargingHistoryV2

I've seen other "akamai-apigateway-" host prefixes but I searched a while and couldn't find "akamai-apigateway-charging-ownership.tesla.com".

I did not need to add the "x-txid" key to the header (or even the bm_sv cookies).

I hope I'm on the right track and this is helping.

[wannesdemaeght]

hi @chadhurin
unfortunately it's not working for me. responsestatus is 400 - Bad Request.
accompanying text: {"errors":[{"message":"Oops! Something went wrong. 387be28a-4046-4479-9d86-61bebf6a10cf","txId":"387be28a-4046-4479-9d86-61bebf6a10cf"}]}

I used both POST and GET, with the url you provided, and a working bearer-token...

[chadhurin]

Hey, @wannesdemaeght
Try this in your body

{ "query": "\n query getChargingHistoryV2($pageNumber: Int!, $sortBy: String, $sortOrder: SortByEnum) {\n me {\n charging {\n historyV2(pageNumber: $pageNumber, sortBy: $sortBy, sortOrder: $sortOrder) {\n data {\n ...SparkHistoryItemFragment\n }\n totalResults\n hasMoreData\n pageNumber\n }\n }\n }\n}\n \n fragment SparkHistoryItemFragment on SparkHistoryItem {\n countryCode\n programType\n billingType\n vin\n credit {\n distance\n distanceUnit\n }\n chargingPackage {\n distance\n distanceUnit\n energyApplied\n }\n invoices {\n fileName\n contentId\n invoiceType\n }\n chargeSessionId\n siteLocationName\n chargeStartDateTime\n chargeStopDateTime\n unlatchDateTime\n fees {\n ...SparkHistoryFeeFragment\n }\n vehicleMakeType\n sessionId\n surveyCompleted\n surveyType\n postId\n cabinetId\n din\n}\n \n fragment SparkHistoryFeeFragment on SparkHistoryFee {\n sessionFeeId\n feeType\n payorUid\n amountDue\n currencyCode\n pricingType\n usageBase\n usageTier1\n usageTier2\n usageTier3\n usageTier4\n rateBase\n rateTier1\n rateTier2\n rateTier3\n rateTier4\n totalTier1\n totalTier2\n totalTier3\n totalTier4\n uom\n isPaid\n uid\n totalBase\n totalDue\n netDue\n status\n}\n ", "variables": { "sortBy": "start_datetime", "sortOrder": "DESC", "pageNumber": 1 }, "operationName": "getChargingHistoryV2" }

with these headers:

--header 'User-Agent: Tesla/1195 CFNetwork/1388 Darwin/22.0.0'
--header 'x-tesla-user-agent: TeslaApp/4.11.1/12ad93c62a/ios/16.0'
--header 'Content-Type: application/json'
--header 'Authorization: Bearer {token}

[chadhurin]

@wannesdemaeght Did that work?

[wannesdemaeght]

Hi @chadhurin, thanks for your help!
I got everything working exactly as I wanted.

could you maybe help me along with the correct body to get a list of the premium connectivity invoices?