日本語

Don't have an account?

Verify email / forgot password

TeslaMate JP Pro

Tesla vehicle data visualization with monthly or yearly billing and a 14-day free trial.

Authorize your Tesla account

You'll be redirected to Tesla's sign-in page. This service does not receive or store your Tesla password. Review the requested scopes and vehicle-command permission below.

Uses the official Fleet API (OAuth 2.0)

Authentication happens on Tesla's official servers. Your Tesla password is never stored.

Review permissions and setup before connecting Tesla

After Tesla authorization, your vehicle may need setup. Then check for the first received data. Review the permissions and steps below.

What happens next

  1. Authorize your Tesla account

    Review the scopes on Tesla’s screen and decide whether to grant them.

  2. Prepare your vehicle

    Your vehicle may need a virtual key or an in-vehicle data-streaming setting.

  3. Check for the first data

    Fields and timing vary by vehicle and network; until then, we show no data received.

OAuth scopes requested by this service (5)
  • openid

    Authenticates your Tesla account.

  • offline_access

    Refreshes the access token for an ongoing connection.

  • vehicle_device_data

    Accesses vehicle data.

  • vehicle_location

    Accesses vehicle location data.

  • vehicle_cmds

    Registers and updates Fleet Telemetry configuration through the Tesla Fleet API.

vehicle_charging_cmds is not requested by the current default authorization.

vehicle_cmds may also authorize vehicle commands such as unlocking. This service uses it to register and update Fleet Telemetry configuration and does not currently offer user-facing remote vehicle controls. Review the permission on Tesla’s consent screen.

Protection measures in the implementation
Tesla OAuth and passwords

Tesla OAuth and passwords

Tesla account authentication takes place on Tesla’s OAuth page; this service does not receive or store your Tesla password. Email-registration passwords are hashed separately with bcrypt.

Application-level tenant separation

Application-level tenant separation

Data is stored in a shared PostgreSQL database and separated by tenant_id in application queries. It is not a dedicated database per tenant and does not use row-level security (RLS). Admin APIs are governed by RBAC and audit logs.

Token encryption

Token encryption

Tesla Fleet API access tokens are encrypted with AES-GCM before database storage. See the scope list above for the purpose of the vehicle-command permission.

By logging in, you agree to our Terms of Service and Privacy Policy.