Data is aggregated by instance_id and received time in 30 minute windows. The service does best-effort to aggregate data received in a 30 minute window into a single file, however it does not guarantee there will only be one file. Multiple files per window could happen under certain scenarios and should be expected by the consumer.

Messaging semantics of the service is “at-least-once” on a per data row basis. Duplicated data may happen under certain scenarios and should be expected by the consumer. The service provides best-effort to not aggregate duplicated data.

Under certain scenarios (for example loss of internet connectivity at an individual site), some devices might be reporting data with signficant latency. Data will be aggregated by received time of the Tesla server, not by measurement time at the device.

Command	Endpoint	Description
GET	/telemetry/bulk/site/signals	Returns all site-level (aggregated) signals. For example, if there are multiple batteries on the site, this endpoint will return a single aggregated value for batter power.
GET	/telemetry/bulk/device/signals	Returns all device-level signals. For example, if there are multiple batteries on the site, this endpoint will return a battery power signal for each individual battery separately.

Parameters

• instance_id: (Required) UUID of an instance. Example: 94010dfa-b49f-4833-8e19-b7468052f3ef
• start_datetime: (Required) Date time using the ISO8601 standard format representing the start time. Example: 2023-02-15T00:00:00Z
• end_datetime: (Required) Date time using the ISO8601 standard format representing the end time. Example: 2023-02-16T00:00:00Z

Only files generated between start_datetime (inclusive) and end_datetime (exclusive) will be returned by the API.