Tesla Fleet API
✓ Official Vendor SpecE 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Tesla Fleet API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'adjusts the site backup reserve') and Jentic returns the matching Tesla Fleet API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Tesla Fleet API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED