Tesla Fleet API
Official vendor OpenAPI document · agent-readyE CommerceStorefrontbearer58 EndpointsREST
For Agents
Programmatically adjusts the site backup reserve, returns aggregated site energy measurements. Covers 58 operations with bearer authentication.
Use for: I need to adjusts the site backup reserve, I want to returns aggregated site energy measurements, Search for returns wall connector charging history, Find all controls grid charging and energy export permissions
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
The Tesla Fleet API provides endpoints to manage Tesla vehicles and energy products, including vehicle commands, telemetry, energy site management, and fleet configuration. The API exposes 58 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Tesla Fleet API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tesla Fleet API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftesla.com%2Ftesla" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftesla.com%2Ftesla" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Tesla Fleet API.
Adjusts the site backup reserve
Returns aggregated site energy measurements
Controls grid charging and energy export permissions
Modifies backup reserve for vehicle charging during outages
Sets site operating mode
Use Cases
Patterns agents use Tesla Fleet API for, with concrete tasks.
★ E-Commerce Operations
Use the Tesla Fleet API to perform e commerce operations programmatically. The API provides 58 endpoints covering core functionality including adjusts the site backup reserve, returns aggregated site energy measurements, returns wall connector charging history.
Call POST /api/1/energy_sites/{energy_site_id}/backup to adjusts the site backup reserve
Automated Energy Management
Automate energy operations by combining multiple Tesla Fleet API endpoints. Agents can returns aggregated site energy measurements and then returns wall connector charging history in a single workflow.
Call GET /api/1/energy_sites/{energy_site_id}/calendar_history to returns aggregated site energy measurements, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Tesla Fleet API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'adjusts the site backup reserve', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
58 endpoints — the tesla fleet api provides endpoints to manage tesla vehicles and energy products, including vehicle commands, telemetry, energy site management, and fleet configuration.
METHOD
PATH
DESCRIPTION
POST
/api/1/energy_sites/{energy_site_id}/backup
Adjusts the site backup reserve
GET
/api/1/energy_sites/{energy_site_id}/calendar_history
Returns aggregated site energy measurements
GET
/api/1/energy_sites/{energy_site_id}/telemetry_history
Returns wall connector charging history
POST
/api/1/energy_sites/{energy_site_id}/grid_import_export
Controls grid charging and energy export permissions
GET
/api/1/energy_sites/{energy_site_id}/live_status
Returns real-time site status
POST
/api/1/energy_sites/{energy_site_id}/off_grid_vehicle_charging_reserve
Modifies backup reserve for vehicle charging during outages
POST
/api/1/energy_sites/{energy_site_id}/operation
Sets site operating mode
GET
/api/1/energy_sites/{energy_site_id}/site_info
Provides site details including assets and settings
POST
/api/1/energy_sites/{energy_site_id}/backup
Adjusts the site backup reserve
GET
/api/1/energy_sites/{energy_site_id}/calendar_history
Returns aggregated site energy measurements
GET
/api/1/energy_sites/{energy_site_id}/telemetry_history
Returns wall connector charging history
POST
/api/1/energy_sites/{energy_site_id}/grid_import_export
Controls grid charging and energy export permissions
GET
/api/1/energy_sites/{energy_site_id}/live_status
Returns real-time site status
POST
/api/1/energy_sites/{energy_site_id}/off_grid_vehicle_charging_reserve
Modifies backup reserve for vehicle charging during outages
POST
/api/1/energy_sites/{energy_site_id}/operation
Sets site operating mode
GET
/api/1/energy_sites/{energy_site_id}/site_info
Provides site details including assets and settings
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Tesla Fleet API by hand means learning its OAuth2 bearer auth, pointing at the regional fleet-api.prd.na.vn.cloud.tesla.com host, and coding each energy-site call yourself. Through Jentic you install once, import the Tesla Fleet API from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
The Tesla Fleet API puts the energy site id in the URL path (/api/1/energy_sites/{energy_site_id}/...), so a rule can pin your agent to one energy site: it can read live status and history for that site and nothing else. You choose the operations it may call, so changing grid import/export or backup settings is not included unless you add it.
Credential isolation
Your Tesla Fleet API bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read energy site live status' or 'fetch calendar history', and Jentic returns the matching Tesla Fleet API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using Tesla Fleet API through Jentic.
What authentication does the Tesla Fleet API use?
The Tesla Fleet API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I adjusts the site backup reserve with the Tesla Fleet API?
Yes. Use the POST /api/1/energy_sites/{energy_site_id}/backup endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Tesla Fleet API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I adjusts the site backup reserve through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'adjusts the site backup reserve'. Jentic returns the matching Tesla Fleet API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Tesla Fleet API have?
The Tesla Fleet API exposes 58 endpoints covering energy, fleet, products operations.
Can I limit what my agent is allowed to do with the Tesla Fleet API?
Yes. Because you run Jentic One yourself and set its rules, you decide which Tesla Fleet API operations and which stored credentials your agent may use. Since the energy site id sits in the URL path (/api/1/energy_sites/{energy_site_id}/...), you can pin the agent to a single site and allow only read calls such as live status and calendar history. Write operations like changing grid import and export or adjusting the backup reserve stay off limits unless you explicitly grant them.
GET STARTED