# NetworkLinks Object

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

Schema for the `NetworkLinks` resource in **Unified Cloud Infrastructure API**.

## Properties

- **`id`** _(string, required)_
  Truto's stable unified identifier for this object. Opaque; use provider_id to address the object in the provider's own console or API.
- **`provider_id`** _(string)_
  The provider's own identifier, passed through verbatim — a full ARN, resource id, or self-link. Never truncated, prefixed, or normalized.
- **`provider`** _(string)_
  Which cloud this object was read from.
  Allowed: `aws`, `azure`, `gcp`
- **`account`** _(string)_
  The account, subscription or project this object belongs to.
- **`region`** _(string)_
  Where the object is located. 'global' denotes genuinely global resources (e.g. IAM, GCP VPC networks) rather than a guessed region. A substituted region (when none is derivable) is flagged in unreadable_fields.
- **`native_type`** _(string)_
  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, key/value normalization, or merging of separate provider concepts. An empty object means no tags; tags that could not be read appear in unreadable_fields instead.
- **`collected_at`** _(string)_
  When Truto actually read this object from the provider, in UTC ISO 8601 with the offset present — not the request time, and not a provider timestamp.
- **`updated_at`** _(string)_
  When the object was last modified at the provider, in UTC ISO 8601. Null when the provider does not record one - see unreadable_fields.
- **`created_at`** _(string)_
  When the object was created at the provider, in UTC ISO 8601. Null when the provider does not record one - see unreadable_fields.
- **`unreadable_fields`** _(array<object>)_
  Fields on this object that could not be read, and why. An empty array means everything was read. Use this to tell a real value from a missing one.
  - **`field`** _(string)_
    The property on this resource that could not be read.
  - **`reason`** _(string)_
    Why the field could not be read. available_on_get: Not read on list to keep the list fast; call GET for this resource's id to get it.
    Allowed: `not_supported_by_provider`, `not_configured`, `permission_denied`, `not_collected`, `collection_error`, `partially_collected`, `available_on_get`
  - **`detail`** _(string)_
    Explanation of the reason, where one adds anything.
- **`remote_data`** _(object)_
  Raw data returned from the remote API call.
- **`link_id`** _(string)_
  The provider's own identifier for the link.
- **`link_type`** _(string)_
  What kind of connection this is.
  Allowed: `peering`, `transit_attachment`, `shared_network`, `vpn`, `interconnect`, `other`
- **`local_boundary`** _(object)_
  The network on this side of the link.
  - **`id`** _(string)_
    The target's `id`.
- **`remote_boundary`** _(object)_
  The network on the far side of the link. Resolves only when the far side is an account this connection also reads.
  - **`id`** _(string)_
    The target's `id`.
- **`remote_account_id`** _(string)_
  The account owning the far side of the link. Local/remote are assigned by account ownership, not by which side initiated the connection.
- **`remote_region`** _(string)_
  The region on the far side of the link.
- **`state`** _(string)_
  The provider's own state string for the link, verbatim.
- **`routes_installed`** _(boolean)_
  Whether routes actually exist for this link. An active peering state doesn't mean routes were added — that's a separate, manual step on AWS.
- **`allows_transit`** _(boolean)_
  Whether traffic can transit to a third network through this link. Always false for AWS VPC peering. For transit gateways, it's derived from associations and propagations combined, not one attachment field.
- **`route_exchange_settings`** _(object)_
  Route exchange configuration, where the provider has one. AWS VPC peering has no real equivalent (only a DNS-resolution option survives); null with not_supported_by_provider there.
  - **`allow_dns_resolution_from_remote_vpc`** _(boolean)_
    AWS allowDnsResolutionFromRemoteVpc. Whether the remote network can resolve private DNS on this side. This is DNS, not routing - AWS VPC peering exchanges no routes automatically.
- **`default_route_table_association`** _(boolean)_
  For transit gateways, whether attachments associate with the default route table automatically. With default_route_table_propagation both true, every attached network can reach every other.
- **`default_route_table_propagation`** _(boolean)_
  For transit gateways, whether attachment routes propagate into the default route table automatically.

## Methods

- [GET /unified/cloud-infrastructure/network_links](/docs/api-reference/unified-cloud-infrastructure-api/networklinks/list) — List Network links