Skip to content
GET /unified/cloud-infrastructure/human_identities

Query Parameters

Refer Specifying query parameters in Truto APIs

Show Truto-specific parameters
integrated_account_idstring · uuid
required·

The ID of the integrated account to use for the request.

Example: 62f44730-dd91-461e-bd6a-aedd9e0ad79d
truto_response_formatstring

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.

Example: unified
Possible values:
unifiedrawnormalizedstreamdebug
truto_key_bystring

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.

Example: id
truto_ignore_limitboolean

Ignores the limit query parameter.

truto_ignore_remote_databoolean

Excludes the remote_data attribute from the response.

truto_exclude_fieldsstring[]

Array of fields to exclude from the response.

Example: truto_exclude_fields[]=id&truto_exclude_fields[]=name
remote_queryRecord<string, any>

Query parameters to pass to the underlying API without any transformations. Refer this guide to see how to structure the query parameters.

Example: remote_query[foo]=bar

Response Body

debugobject

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.

data
isEmptyResultboolean
isLoopingboolean
nextCursorstring
requestOptionsRecord<string, any>
requestUrlstring
responseHeadersRecord<string, any>
resultCountnumber
next_cursorstring

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.

resultobject[]

List of Human identities

account_refstring
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.

1 supported
Amazon Web Services
supported
collected_atstring · date-time
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.

1 supported
Amazon Web Services
supported
enabledboolean
required·

Whether the identity can currently sign in. Real and readable for Identity Center (UserStatus). For AWS IAM users no such field exists -- it is synthesized from 'no login profile and no active access keys' and flagged as derived.

1 supported
Amazon Web Services
supported
idstring
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.

1 supported
Amazon Web Services
supported
identity_refstring
required·

The provider's own identifier for the identity.

1 supported
Amazon Web Services
supported
identity_storestring
required·

Which identity store this row came from. Load-bearing on AWS, where IAM users and Identity Center users share no identifiers and answer different subsets of this resource's fields.

1 supported
Amazon Web Services
supported
identity_typestring
required·

Whether this is a person, a service account or an external guest. Guests are counted differently against every standard.

Possible values:
humanserviceguestexternalunknown
1 supported
Amazon Web Services
supported
native_typestring
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.

1 supported
Amazon Web Services
supported
providerstring
required·

Which cloud this object was read from.

Possible values:
awsazuregcp
1 supported
Amazon Web Services
supported
provider_refstring
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.

1 supported
Amazon Web Services
supported
admin_rolesstring[]

The administrative roles or policies behind is_admin, as provider references.

1 supported
Amazon Web Services
supported
created_atstring · date-time

When the identity was created.

1 supported
Amazon Web Services
supported
display_namestring

The person's display name. Does not exist for AWS IAM users, which carry only a user name and a path; null there with a not_supported_by_provider entry.

1 supported
Amazon Web Services
supported
email_or_upnstring

Email address or user principal name -- the join key against the customer's staff directory. AWS IAM users have no email attribute anywhere in the API, so on that path this is null unless the customer happens to carry it as a tag.

1 supported
Amazon Web Services
supported
group_membershipsstring[]

Group references for this identity. Evidence that access is granted by role rather than one user at a time.

1 supported
Amazon Web Services
supported
has_console_accessboolean

Whether the identity has interactive sign-in, as distinct from programmatic-only. On AWS this is the 404 from GetLoginProfile read as an answer rather than an error. An IAM-only concept: null on the Identity Center path.

1 supported
Amazon Web Services
supported
has_static_credentialsboolean

Whether the identity holds long-lived credentials. An IAM-only concept on AWS; null on the Identity Center path.

1 supported
Amazon Web Services
supported
is_adminboolean

Whether this identity holds administrative privilege. No provider exposes an admin flag; this is entirely inference from attached permissions and is flagged as derived.

1 supported
Amazon Web Services
supported
last_sign_in_atstring · date-time

Last interactive sign-in. Console sign-in only on AWS, recorded at five-minute granularity, with a documented multi-week gap in 2018 and no tracking before 2014-10-20. Not available through any API for AWS Identity Center. A programmatic-only user reports null forever and must never be surfaced as 'never signed in'.

1 supported
Amazon Web Services
supported
mfa_device_countinteger

Number of MFA devices registered to this identity.

1 supported
Amazon Web Services
supported
mfa_methodsstring[]

The registered method types, because some standards now distinguish phishing-resistant methods. On AWS, ListMFADevices returns no device type: the type is inferred from the serial number shape and FIDO cannot be cleanly separated from TOTP, so entries are marked derived.

1 supported
Amazon Web Services
supported
mfa_registeredboolean

Whether THIS user has MFA registered. Per user, never per account -- 'the account has MFA enabled' is not an answer to 'does every user have MFA'. Not available at all for AWS Identity Center: no public API exposes it, and it is emitted as null with not_supported_by_provider rather than guessed.

1 supported
Amazon Web Services
supported
regionstring

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
Amazon Web Services
supported
remote_dataRecord<string, any>

Raw data returned from the remote API call.

tagsobject

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
Amazon Web Services
supported
unreadable_fieldsobject[]

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
Amazon Web Services
supported
truto unified cloud-infrastructure humanidentities \
  -a '<integrated_account_id>' \
  -o json
import Truto from '@truto/truto-ts-sdk';

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

const result = await truto.unifiedApi.list(
  'cloud-infrastructure',
  'humanidentities',
  { 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",
        "humanidentities",
        {"integrated_account_id": "<integrated_account_id>"}
    ):
        print(item)

asyncio.run(main())
curl -X GET 'https://api.truto.one/unified/cloud-infrastructure/human_identities?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/human_identities?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/human_identities"
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())