# List Object stores

> Source: https://truto.one/docs/api-reference/unified-cloud-infrastructure-api/objectstores/list/

`GET /unified/cloud-infrastructure/object_stores`

Resource: **ObjectStores** · API: **Unified Cloud Infrastructure API**

## Supported integrations

Amazon Web Services

## Query parameters

- **`integrated_account_id`** _(string, required)_
  The ID of the integrated account to use for the request.
- **`truto_response_format`** _(string)_
  The format of the response. - `unified` returns the response with unified mappings applied. - `raw` returns the unprocessed, raw response from the remote API. - `normalized` applies the unified mappings and returns the data in a normalized format. - `stream` returns 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. - `debug` returns the final unified result alongside raw remote fetch information. The response is an envelope containing `result` (identical to unified mode output) and `debug` (with `requestUrl`, `requestOptions`, `data`, `responseHeaders`, and for list operations: `nextCursor`, `isLooping`, `isEmptyResult`, `resultCount`). When the upstream body exceeds 1 MiB, `data` is replaced by `{ truto_truncated: true, truto_max_bytes, truto_excerpt }`. `debug` is `null` for static responses or when `truto_skip_api_call=true`. Defaults to `unified`.
  Allowed: `unified`, `raw`, `normalized`, `stream`, `debug`
- **`truto_key_by`** _(string)_
  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.
- **`truto_ignore_limit`** _(boolean)_
  Ignores the `limit` query parameter.
- **`truto_ignore_remote_data`** _(boolean)_
  Excludes the `remote_data` attribute from the response.
- **`truto_exclude_fields`** _(array<string>)_
  Array of fields to exclude from the response.
- **`remote_query`** _(object)_
  Query parameters to pass to the underlying API without any transformations. Refer [this guide](https://truto.one/docs/api-reference/overview/querying#remote-query-parameters) to see how to structure the query parameters.

## Response body

- **`result`** _(array<object>)_
  List of Object stores
  - **`id`** _(string, required)_
    Truto's stable unified identifier for this object. Opaque; use provider_ref to address the object in the provider's own console or API.
  - **`provider_ref`** _(string, required)_
    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.
  - **`provider`** _(string, required)_
    Which cloud this object was read from.
    Allowed: `aws`, `azure`, `gcp`
  - **`account_ref`** _(string, required)_
    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.
  - **`region`** _(string)_
    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.
  - **`native_type`** _(string, required)_
    The provider's own type string, unmodified -- for example 'AWS::S3::Bucket', 'aws_iam_role', 'Microsoft.Sql/servers'. Used for display and drill-down.
  - **`tags`** _(object)_
    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.
  - **`collected_at`** _(string, required)_
    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.
  - **`unreadable_fields`** _(array<object>)_
    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'.
  - **`remote_data`** _(object)_
    Raw data returned from the remote API call.
  - **`store_ref`** _(string, required)_
    The provider's own identifier for the store.
  - **`name`** _(string, required)_
    The bucket or container name.
  - **`location`** _(string, required)_
    Where the store's data physically sits. A compliance answer in its own right.
  - **`public_access_blocked`** _(boolean)_
    Whether public access is comprehensively blocked. On AWS this is true only when all four effective block-public-access flags are set, taking the most restrictive of the account-level and bucket-level configurations; a missing configuration counts as all-false, not as blocked.
  - **`anonymous_access_allowed`** _(boolean)_
    Whether the store is effectively reachable without credentials. Computed, not read: on AWS, BlockPublicAcls and BlockPublicPolicy are write-time guards that AWS documents as not affecting existing policies or ACLs, so only IgnorePublicAcls and RestrictPublicBuckets change effective read access. Computing exposure from the two block flags produces false clean results.
  - **`policy_grants_anyone`** _(boolean)_
    Whether the access POLICY grants access to anyone, reflecting the policy itself and not only an account-level toggle -- the two disagree often. Note that on AWS a cross-account role cannot read a bucket policy at all (405 regardless of IAM), so this falls back to the bucket policy status operation and any field that needs the policy body is marked permission_denied.
  - **`acl_grants_anyone`** _(boolean)_
    Whether an ACL grants access to a public group. Kept distinct from policy_grants_anyone because the two mechanisms fail independently.
  - **`acl_grants_authenticated_users`** _(boolean)_
    Whether an ACL grants access to any authenticated account on the provider. Not anonymous -- requests must be signed -- but it means any account on earth, and it is kept distinguishable rather than folded into anonymous_access_allowed.
  - **`effective_public_access_block`** _(object)_
    The per-flag effective block configuration after combining account-level and store-level settings, so the consumer can see which specific guard is missing rather than only the rolled-up boolean.
  - **`encryption_key_type`** _(string)_
    Who manages the encryption key. The real control on modern AWS is whether the key is customer-managed: default provider-side encryption is now applied to every bucket, so 'no default encryption' is an obsolete control.
    Allowed: `provider_managed`, `provider_owned`, `customer_managed`, `customer_supplied`, `none`, `unknown`
  - **`encryption_key_ref`** _(string)_
    Reference to the key, stored as the provider returned it -- which may be a key id, an ARN or an alias. Not canonicalised, because canonicalising needs a further key-service call that may be denied.
  - **`encryption_algorithm`** _(string)_
    The provider's own algorithm string, verbatim.
  - **`versioning_enabled`** _(boolean)_
    Whether object versioning is on. On AWS a never-enabled bucket returns an empty document with no status element at all, which is read as false rather than unknown.
  - **`object_lock_enabled`** _(boolean)_
    Whether write-once retention is enabled on the store.
  - **`retention_policy_days`** _(integer)_
    Default retention period applied to objects, in days.
  - **`retention_locked`** _(boolean)_
    Whether the retention period itself cannot be shortened or removed. Not a real S3 field: the closest honest AWS mapping is a COMPLIANCE-mode default rule, which is a default for FUTURE objects rather than a statement about anything currently stored, and legal holds are per object version. Carried with that caveat in unreadable_fields.
  - **`lifecycle_rules`** _(array<object>)_
    Lifecycle rules as objects, carrying the provider's own rule id, status, prefix or filter and transition and expiry settings. An empty array means no rules are configured; null means they could not be read.
  - **`access_logging_enabled`** _(boolean)_
    Whether access logging is on. On AWS an unlogged bucket returns an empty document rather than an error, read as false.
  - **`min_tls_version`** _(string)_
    Minimum TLS version accepted. No bucket-level setting exists on AWS: the only mechanism is a per-action condition key inside the bucket policy, so a policy can require TLS 1.2 for writes and allow TLS 1.0 for reads and there is no honest bucket-wide scalar. Emitted as null with not_supported_by_provider rather than guessed.
  - **`replication_targets`** _(array<object>)_
    Replication destinations as objects carrying the destination store reference, its region and the rule status. Load-bearing for the data residency check: a replica quietly created on another continent is a serious finding.
  - **`replication_enabled`** _(boolean)_
    Whether any replication rule is configured and enabled.
- **`next_cursor`** _(string)_
  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.
- **`debug`** _(object)_
  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`.
  - **`requestUrl`** _(string)_
  - **`requestOptions`** _(object)_
  - **`data`** _(unknown)_
  - **`responseHeaders`** _(object)_
  - **`nextCursor`** _(string)_
  - **`isLooping`** _(boolean)_
  - **`isEmptyResult`** _(boolean)_
  - **`resultCount`** _(number)_

## Code examples

### Truto CLI

```bash
truto unified cloud-infrastructure objectstores \
  -a '<integrated_account_id>' \
  -o json
```

### Truto TS SDK

```typescript
import Truto from '@truto/truto-ts-sdk';

const truto = new Truto({
  token: '<your_api_token>',
});

const result = await truto.unifiedApi.list(
  'cloud-infrastructure',
  'objectstores',
  { integrated_account_id: '<integrated_account_id>' }
);

console.log(result);
```

### Truto Python SDK

```python
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",
        "objectstores",
        {"integrated_account_id": "<integrated_account_id>"}
    ):
        print(item)

asyncio.run(main())
```

### curl

```bash
curl -X GET 'https://api.truto.one/unified/cloud-infrastructure/object_stores?integrated_account_id=<integrated_account_id>' \
  -H 'Authorization: Bearer <your_api_token>' \
  -H 'Content-Type: application/json'
```

### JavaScript

```javascript
const integratedAccountId = '<integrated_account_id>';

const response = await fetch(`https://api.truto.one/unified/cloud-infrastructure/object_stores?integrated_account_id=${integratedAccountId}`, {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer <your_api_token>',
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);
```

### Python

```python
import requests

url = "https://api.truto.one/unified/cloud-infrastructure/object_stores"
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())
```