Note that, a data-export to complete may require several minutes.
Checkout periodically the data-export status, by calling the get details method issuing the data-export identifier.
Limitations:
- Only one bulk export can be scheduled at a time.
- Only the archives of the compelted exports during the last 30 days are keep stored for further downloads.
Required permissions: EXPORT_DATA.
The name of the target tenant (e.g. acme).
The details of the scheduled data-export.
The bean providing data-export details.
The data-export friendly name.
The timestamp UTC the data-export has been scheduled.
The file name mask (without .CSV extension) used for the generated CSV files.
The flag indicating whether the file name (without extension) must be anonimized through an MD5 hashing.
The list of thing-definition identifiers whose associated thing data must be exported.
The list of metric identifiers whose associated data must be exported.
The start timestamp UTC related to the exported period of data.
The end timestamp UTC related to the exported period of data.
Successful created.
The bean providing data-export details.
The data-export unique identifier.
The data-export friendly name.
The timestamp UTC the data-export has been scheduled.
The file name mask (without .CSV extension) used for the generated CSV files.
The flag indicating whether the file name (without extension) must be anonimized through an MD5 hashing.
The data-export status.
The list of thing-definition identifiers whose associated thing data must be exported.
The list of metric identifiers whose associated data must be exported.
The start timestamp UTC related to the exported period of data.
The end timestamp UTC related to the exported period of data.
The data-export genrated archive URL (available only retrieving the data-export details).
Request data not valid.
The error response.
User not authenticated.
The error response.
User not authorized.
The error response.
API call rate limit exeeded.
The error response.
Internal server error.
The error response.