Bulk API Frequently Asked Questions

How can clients associate data provided from Telemetry Bulk API with other APIs within Powerhub API?
  • The only identifier provided by the Telemetry Bulk API is the Device identifier. This is an individual Tesla Gateway device located at a site. This will correspond directly with the gateway’s din field provided by the /asset/sites/{site_id} Powerhub API route.
How many bulk files may exist during one time window?
  • There may be more than one file. There is a size threshold where the processing application splits files. The current size threshold is 6GB.
As the fleet scales, how will the file size change, or are there subdivisions?
  • The files will grow until reaching the splitting size threshold.
How do the signals evolve over time?
  • It will be dynamic. They will appear as Tesla allows them and as they are produced by the device.
What is the guidance for looking for data before the retention policy?
  • Data is deleted after the retention policy in the system without recovery mechanism.
Are there options to process data on behalf on the client? e.g. create a 15 min aggregation of the time-series values
  • There is no support for the Tesla servers to process or transform data on behalf of the client.
What happens if the file generation fails?
  • The file generation process will retry when there is a failure. Tesla monitors for sustained failures and will alert on-call engineers when this occurs.
What if the API call returns an error?
  • The client should retry the call. The client needs to track what files they have downloaded and should use the start_datetime as the key.