Skip to content

Commit

Permalink
Update tesla_fleet.markdown
Browse files Browse the repository at this point in the history
  • Loading branch information
Bre77 committed Sep 28, 2024
1 parent 3ad4024 commit 9a9f30a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion source/_integrations/tesla_fleet.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ You must have a [Tesla](https://tesla.com) account and a Tesla vehicle, PowerWal

{% details "Use a custom OAuth application" %}

The integration has a built-in OAuth application that will be suitable for most users. However, you can [create your own application](https://developer.tesla.com/dashboard) for the Tesla Fleet API and configure it as an [application credential](https://my.home-assistant.io/redirect/application_credentials). When creating the application, you must set `https://my.home-assistant.io/redirect/oauth` as the redirect URL.
The integration has a built-in OAuth application that will be suitable for most users. However, you can [create your own application]([https://developer.tesla.com/dashboard](https://developer.tesla.com/docs/fleet-api/getting-started/what-is-fleet-api#step-2-create-an-application)) for the Tesla Fleet API and configure it as an [application credential](https://my.home-assistant.io/redirect/application_credentials). When creating the application, you must set the redirect URL to `https://my.home-assistant.io/redirect/oauth`, but the other URLs can be set as desired. You must also complete both [step 3](https://developer.tesla.com/docs/fleet-api/getting-started/what-is-fleet-api#step-3-generate-a-public-private-key-pair) and [step 4](https://developer.tesla.com/docs/fleet-api/getting-started/what-is-fleet-api#step-4-call-the-register-endpoint) before the application will be able to make API calls.

You will be prompted to pick your custom application credential when creating a Tesla Fleet config entry.

Expand Down

0 comments on commit 9a9f30a

Please sign in to comment.