List Data snapshots
/unified/cloud-infrastructure/data_snapshots
Query Parameters
Refer Specifying query parameters in Truto APIs
Which snapshot API to read. 'ebs' (default) calls DescribeSnapshots with Owner.1=self - the owner filter is a correctness requirement, not an optimisation, because an unscoped call enumerates every public EBS snapshot in all of AWS. 'rds_instance' and 'rds_cluster' are separate APIs and neither returns the other's rows; calling only rds_instance against an Aurora-heavy account returns empty and would wrongly read as 'no backups'. All three must be called for a complete inventory. NOTE: the 'ebs' route cannot accept the region parameter - see the build note on EC2 query-parameter rejection.
block_volumedatabase_clusterdatabase_instancediskebsotherrds_clusterrds_instance
1 supported
ebsrds_instancerds_clusterShow Truto-specific parameters
The ID of the integrated account to use for the request.
62f44730-dd91-461e-bd6a-aedd9e0ad79dThe format of the response.
unifiedreturns the response with unified mappings applied.rawreturns the unprocessed, raw response from the remote API.normalizedapplies the unified mappings and returns the data in a normalized format.streamreturns the response as a stream, which is ideal for transmitting large datasets, files, or binary data. Using streaming mode helps to efficiently handle large payloads or real-time data flows without requiring the entire data to be buffered in memory.debugreturns the final unified result alongside raw remote fetch information. The response is an envelope containingresult(identical to unified mode output) anddebug(withrequestUrl,requestOptions,data,responseHeaders, and for list operations:nextCursor,isLooping,isEmptyResult,resultCount). When the upstream body exceeds 1 MiB,datais replaced by{ truto_truncated: true, truto_max_bytes, truto_excerpt }.debugisnullfor static responses or whentruto_skip_api_call=true.
Defaults to unified.
unifiedunifiedrawnormalizedstreamdebug
By default the result attribute is an array of objects. This parameter allows you to specify a field in each result objects to use as key, which transforms the result array into an object with the array items keyed by the field. This is useful for when you want to use the result as a lookup table.
idIgnores the limit query parameter.
Excludes the remote_data attribute from the response.
Array of fields to exclude from the response.
truto_exclude_fields[]=id&truto_exclude_fields[]=nameQuery parameters to pass to the underlying API without any transformations. Refer this guide to see how to structure the query parameters.
remote_query[foo]=barResponse Body
Present only when truto_response_format=debug. Contains raw fetch details: requestUrl, requestOptions, data, responseHeaders, nextCursor, isLooping, isEmptyResult, resultCount. data is the parsed upstream body; when its JSON form exceeds 1 MiB it is replaced by { truto_truncated: true, truto_max_bytes, truto_excerpt }, where truto_excerpt is the leading bytes of that body. The same applies to a string requestOptions.body. null for static responses or when truto_skip_api_call=true.
The cursor to use for the next page of results. Pass this value as next_cursor in the query parameter in the next request to get the next page of results.
List of Data snapshots
The account, subscription or project the object belongs to. An object with no account cannot be attributed to an environment, so this is always present for objects that live inside an account.
1 supported
When Truto actually read this object from the provider, in UTC ISO 8601 with the offset present. Not when the request was made and not a provider timestamp. Drives consumer staleness rules.
1 supported
When the snapshot was taken.
1 supported
Whether the snapshot is encrypted.
1 supported
Truto's stable unified identifier for this object. Opaque; use provider_ref to address the object in the provider's own console or API.
1 supported
Whether the snapshot is readable by any account on the provider.
1 supported
Where the snapshot sits NOW. Never mapped from a provider source-region field, which means 'created in or copied from' and therefore names the origin rather than the current home for a cross-region copy. For block-volume snapshots AWS returns no location at all and the collector stamps on the region it queried.
1 supported
The provider's own type string, unmodified -- for example 'AWS::S3::Bucket', 'aws_iam_role', 'Microsoft.Sql/servers'. Used for display and drill-down.
1 supported
Which cloud this object was read from.
awsazuregcp
1 supported
The provider's own unbroken identifier, passed through verbatim -- a full ARN, resource id or self-link. Never truncated, prefixed or normalised. This is the customer-facing key used to find the object in the console.
1 supported
Which snapshot service this came from. A discriminator, because the underlying shapes use different field names for encryption and carry different sharing semantics -- one shared mapper reports every clustered snapshot as unencrypted.
block_volumedatabase_instancedatabase_clusterdiskother
1 supported
The provider's own identifier for the snapshot.
1 supported
The account that owns the source. Half of the production-data-in-test check. Neither AWS database snapshot type carries an owner field, so this is parsed out of the ARN.
1 supported
The database or volume this snapshot was taken from.
1 supported
Reference to the encryption key, where the snapshot is encrypted.
1 supported
Where the object is. A compliance answer in its own right, not metadata. The literal string 'global' is emitted for genuinely global resources (for example IAM, or a GCP VPC network) rather than guessing a region. Never invented: where the provider does not return a location and none can be derived, the collector's queried region is used and that substitution is recorded in unreadable_fields.
1 supported
The account-and-region-wide snapshot sharing posture. Changes how is_public must be read: under a block-all-sharing setting, an already-public snapshot is treated as private and is not publicly available, so reporting it as exposed is a false positive. Both the per-snapshot ACL and this regional posture are reported.
1 supported
Raw data returned from the remote API call.
Accounts this snapshot has been explicitly shared with. An empty array means shared with nobody; null means the sharing attribute could not be read. On AWS this needs a separate per-snapshot call that has no batch form, making it the most expensive read in the collector.
1 supported
Whether the per-snapshot sharing attribute was actually read. False means shared_with_accounts and is_public are inferred rather than confirmed, so an empty sharing list is never mistaken for a verified clean result.
1 supported
Whether the snapshot was taken manually or by the provider's automated backup. Load-bearing: automated snapshots cannot be shared at all, so their sharing fields are true by construction rather than by a per-snapshot call.
manualautomatedunknown
1 supported
The provider's own status string for the snapshot, verbatim.
1 supported
Key-value pairs exactly as the customer set them: no case folding, no key or value normalisation, no merging of separate provider concepts. Present on every object because tags are the primary input for environment classification. An empty object means the object carries no tags; tags that could not be read are recorded in unreadable_fields instead.
1 supported
Per-object list of the fields that could not be read, and why -- the brief section 8.4 answer, chosen over per-field sentinel values. Each entry is an object with 'field' (the property name on this resource), 'reason' (a reason code) and an optional human-readable 'detail'. Reason codes: not_supported_by_provider, not_configured, permission_denied, not_collected, collection_error, partially_collected. An empty array means every property on this object was read successfully. A property absent from this array and null in the payload means the provider genuinely returned no value, which is different from 'we could not look'.
1 supported
truto unified cloud-infrastructure datasnapshots \
-a '<integrated_account_id>' \
-o jsonimport Truto from '@truto/truto-ts-sdk';
const truto = new Truto({
token: '<your_api_token>',
});
const result = await truto.unifiedApi.list(
'cloud-infrastructure',
'datasnapshots',
{ integrated_account_id: '<integrated_account_id>' }
);
console.log(result);import asyncio
from truto_python_sdk import TrutoApi
truto_api = TrutoApi(token="<your_api_token>")
async def main():
async for item in truto_api.unified_api.list(
"cloud-infrastructure",
"datasnapshots",
{"integrated_account_id": "<integrated_account_id>"}
):
print(item)
asyncio.run(main())curl -X GET 'https://api.truto.one/unified/cloud-infrastructure/data_snapshots?integrated_account_id=<integrated_account_id>' \
-H 'Authorization: Bearer <your_api_token>' \
-H 'Content-Type: application/json'const integratedAccountId = '<integrated_account_id>';
const response = await fetch(`https://api.truto.one/unified/cloud-infrastructure/data_snapshots?integrated_account_id=${integratedAccountId}`, {
method: 'GET',
headers: {
'Authorization': 'Bearer <your_api_token>',
'Content-Type': 'application/json',
},
});
const data = await response.json();
console.log(data);import requests
url = "https://api.truto.one/unified/cloud-infrastructure/data_snapshots"
headers = {
"Authorization": "Bearer <your_api_token>",
"Content-Type": "application/json",
}
params = {
"integrated_account_id": "<integrated_account_id>"
}
response = requests.get(url, headers=headers, params=params)
print(response.json())