Update tesla_fleet.markdown (#37410)

This commit is contained in:
Brett Adams 2025-02-11 16:51:27 +10:00 committed by GitHub
parent ee31033060
commit 42a45dc674
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -123,7 +123,7 @@ The following steps involve sensitive credentials. Never share your `Client Secr
3. The CURL request should return a response that looks something like: 3. The CURL request should return a response that looks something like:
```json ```json
{"access_token":"JSON_WEB_TOKEN","expires_in":28800,"token_type":"Bearer"} {"access_token":"ACCESS_TOKEN","expires_in":28800,"token_type":"Bearer"}
``` ```
This is your access token. Copy everything between the double-quotes to be used next. This is your access token. Copy everything between the double-quotes to be used next.
@ -132,14 +132,14 @@ The following steps involve sensitive credentials. Never share your `Client Secr
```shell ```shell
curl --location 'https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/partner_accounts' \ curl --location 'https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/partner_accounts' \
--header 'Content-Type: application/json' \ --header 'Content-Type: application/json' \
--header 'Authorization: Bearer JSON_WEB_TOKEN' \ --header 'Authorization: Bearer ACCESS_TOKEN' \
--data '{ --data '{
"domain": "my.domain.com" "domain": "my.domain.com"
}' }'
``` ```
- If you had to change the `AUDIENCE` URL for your region in step 2, update the main domain of the `--location` arg. - If you had to change the `AUDIENCE` URL for your region in step 2, update the main domain of the `--location` arg.
- Replace `LONG_GIBBERISH_ACCESS_TOKEN_STRING` with the access token that you copied in the previous step. - Replace `ACCESS_TOKEN` with the access token that you copied in the previous step.
- In the `domain:` line, enter your domain without the leading `https://` and the trailing `/`. - In the `domain:` line, enter your domain without the leading `https://` and the trailing `/`.
5. You should see a response that contains information about your Tesla Fleet developer app, pricing info, and such. This confirms that the Tesla Fleet API has successfully registered your developer application as a partner. The hard part is over. 5. You should see a response that contains information about your Tesla Fleet developer app, pricing info, and such. This confirms that the Tesla Fleet API has successfully registered your developer application as a partner. The hard part is over.
@ -165,7 +165,7 @@ When connecting your Tesla account to Home Assistant, you **must** select at lea
Previously, Tesla restricted this integration to a very modest rate limit. However, from January 2025, accounts in eligible countries will be charged for every API call. Here's what you need to know: Previously, Tesla restricted this integration to a very modest rate limit. However, from January 2025, accounts in eligible countries will be charged for every API call. Here's what you need to know:
- Tesla provides a $10 credit per developer account per calendar month - Tesla provides a USD$10 credit per developer account per calendar month
- Every vehicle coordinator refresh, vehicle command, and wake up has a cost - Every vehicle coordinator refresh, vehicle command, and wake up has a cost
- This credit only allows for a maximum of 5000 coordinator refreshes - This credit only allows for a maximum of 5000 coordinator refreshes
- Energy product APIs are free to use at this time - Energy product APIs are free to use at this time