Changes to List Transit Gateways

Changed in 10 of the 75 revisions of this API.▲54●9○47

1. Apr 17, 2026c80d57ed14ab▲1
2. Mar 16, 2026377981ac9f14○1
3. Mar 11, 2026c5d7b6bc7ab1○2
4. Jan 20, 20267bc7400170e0▲1
5. Jan 7, 202641f50b46b442●5○3
6. Oct 23, 20258ab3ec3ed301●1
7. Aug 22, 20253c0154b2053a▲19
8. Aug 14, 20256333a0d3b095▲4○35
9. Jul 22, 202576b0fefddb0d▲29●3○3
10. May 14, 202587c135153b84○3

What changed

• Apr 17, 2026c80d57ed14ab▲1See the full diff
  • ▲

    for the query request parameter filter, the type of property name was specialized from no type to object

    request-parameter-property-type-specialized

  This revision also has 7 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Mar 16, 2026377981ac9f14○1See the full diff
  • ○

    added the required property data/items/oneOf[subschema #4: Azure Virtual Hub Peering Gateway]/transit_gateway_attachment_config to the response with the 200 status

    response-required-property-added

• Mar 11, 2026c5d7b6bc7ab1○2See the full diff
  • ○

    added the optional property data/items/oneOf[subschema #1: AWS Transit Gateway]/transit_gateway_attachment_config/attachment_id to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property data/items/oneOf[subschema #2: AWS VPC Peering Gateway]/transit_gateway_attachment_config/peering_connection_id to the response with the 200 status

    response-optional-property-added

• Jan 20, 20267bc7400170e0▲1See the full diff
  • ▲

    added AzureVHubPeeringGatewayResponse to the data/items response property oneOf list for the response status 200

    response-property-one-of-added

• Jan 7, 202641f50b46b442●5○3See the full diff
  • ●

    added the new error enum value to the data/items/oneOf[subschema #1: AWS Transit Gateway]/state response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new error enum value to the data/items/oneOf[subschema #2: AWS VPC Peering Gateway]/state response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new error enum value to the data/items/oneOf[subschema #3: Azure Transit Gateway]/state response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new error enum value to the data/items/oneOf[subschema #4: GCP VPC Peering Transit Gateway]/state response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new error enum value to the data/items/oneOf[subschema #5: AWS Resource Endpoint Gateway]/state response property for the response status 200

    response-property-enum-value-added

  • ○

    added the enum value error to the property state/oneOf[subschema #1: TransitGatewayStateFieldEqualsFilter]/oneOf[subschema #1: Transit Gateway State]/ of the query request parameter filter

    request-parameter-property-enum-value-added

  • ○

    added the enum value error to the property state/oneOf[subschema #1: TransitGatewayStateFieldEqualsFilter]/oneOf[subschema #2: TransitGatewayStateFieldEqualsComparison]/eq of the query request parameter filter

    request-parameter-property-enum-value-added

  • ○

    added the enum value error to the property state/oneOf[subschema #2: TransitGatewayStateFieldNotEqualsFilter]/neq of the query request parameter filter

    request-parameter-property-enum-value-added

• Oct 23, 20258ab3ec3ed301●1See the full diff
  • ●

    added the new type enum value to the allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterStandard]/rule response property for the response status 400

    response-property-enum-value-added

• Aug 22, 20253c0154b2053a▲19See the full diff
  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterChoiceItem]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterDependentItem]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterMaximumLength]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterMinimumLength]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterStandard]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #1: AWS Transit Gateway]/state_metadata/reason became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #1: AWS Transit Gateway]/state_metadata/reported_status became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #2: AWS VPC Peering Gateway]/state_metadata/reason became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #2: AWS VPC Peering Gateway]/state_metadata/reported_status became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #3: Azure Transit Gateway]/state_metadata/reason became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #3: Azure Transit Gateway]/state_metadata/reported_status became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #4: GCP VPC Peering Transit Gateway]/state_metadata/reason became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #4: GCP VPC Peering Transit Gateway]/state_metadata/reported_status became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #5: AWS Resource Endpoint Gateway]/state_metadata/reason became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/oneOf[subschema #5: AWS Resource Endpoint Gateway]/state_metadata/reported_status became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property detail became nullable for the status 401

    response-property-became-nullable

  • ▲

    the response property instance became nullable for the status 401

    response-property-became-nullable

  • ▲

    the response property status became nullable for the status 401

    response-property-became-nullable

  • ▲

    the response property title became nullable for the status 401

    response-property-became-nullable

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 14, 20256333a0d3b095▲4○35See the full diff
  • ▲

    added GCPVPCPeeringGatewayResponse AwsResourceEndpointGatewayResponse to the data/items response property oneOf list for the response status 200

    response-property-one-of-added

  • ▲

    the data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway] response's property type changed from no type to object for status 200

    response-property-type-changed

  • ▲

    the data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway] response's property type changed from no type to object for status 200

    response-property-type-changed

  • ▲

    the data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway] response's property type changed from no type to object for status 200

    response-property-type-changed

  • ○

    added the enum value pending-user-action to the property state/oneOf[subschema #1: TransitGatewayStateFieldEqualsFilter]/oneOf[subschema #1: Transit Gateway State]/ of the query request parameter filter

    request-parameter-property-enum-value-added

  • ○

    added the enum value pending-user-action to the property state/oneOf[subschema #1: TransitGatewayStateFieldEqualsFilter]/oneOf[subschema #2: TransitGatewayStateFieldEqualsComparison]/eq of the query request parameter filter

    request-parameter-property-enum-value-added

  • ○

    added the enum value pending-user-action to the property state/oneOf[subschema #2: TransitGatewayStateFieldNotEqualsFilter]/neq of the query request parameter filter

    request-parameter-property-enum-value-added

  • ○

    added the optional property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/state_metadata to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/state_metadata to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/state_metadata to the response with the 200 status

    response-optional-property-added

  • ○

    removed AwsTransitGateway BaseTransitGatewayResponse subschema #2 from the data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway] response property allOf list for the response status 200

    response-property-all-of-removed

  • ○

    removed AwsVpcPeeringGateway BaseTransitGatewayResponse subschema #2 from the data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway] response property allOf list for the response status 200

    response-property-all-of-removed

  • ○

    removed AzureTransitGateway BaseTransitGatewayResponse from the data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway] response property allOf list for the response status 200

    response-property-all-of-removed

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/cidr_blocks to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/created_at to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/dns_config to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/entity_version to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/id to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/name to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/state to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/transit_gateway_attachment_config to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/updated_at to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/cidr_blocks to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/created_at to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/dns_config to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/entity_version to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/id to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/name to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/state to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/transit_gateway_attachment_config to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/updated_at to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/created_at to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/dns_config to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/entity_version to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/id to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/name to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/state to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/transit_gateway_attachment_config to the response with the 200 status

    response-required-property-added

  • ○

    added the required property data/items/oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/updated_at to the response with the 200 status

    response-required-property-added

  This revision also has 15 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Jul 22, 202576b0fefddb0d▲29●3○3See the full diff
  • ▲

    the data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse] response's property type changed from object to no type for status 200

    response-property-type-changed

  • ▲

    the data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse] response's property type changed from object to no type for status 200

    response-property-type-changed

  • ▲

    the data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse] response's property type changed from object to no type for status 200

    response-property-type-changed

  • ▲

    removed the required property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/cidr_blocks from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/created_at from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/dns_config from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/entity_version from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/id from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/name from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/state from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/transit_gateway_attachment_config from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/updated_at from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/cidr_blocks from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/created_at from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/dns_config from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/entity_version from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/id from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/name from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/state from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/transit_gateway_attachment_config from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/updated_at from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/created_at from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/dns_config from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/entity_version from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/id from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/name from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/state from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/transit_gateway_attachment_config from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/updated_at from the response with the 200 status

    response-required-property-removed

  • ●

    removed the optional property data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/state_metadata from the response with the 200 status

    response-optional-property-removed

  • ●

    removed the optional property data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/state_metadata from the response with the 200 status

    response-optional-property-removed

  • ●

    removed the optional property data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/state_metadata from the response with the 200 status

    response-optional-property-removed

  • ○

    added AwsTransitGateway BaseTransitGatewayResponse subschema #2 to the data/items/oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse] response property allOf list for the response status 200

    response-property-all-of-added

  • ○

    added AwsVpcPeeringGateway BaseTransitGatewayResponse subschema #2 to the data/items/oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse] response property allOf list for the response status 200

    response-property-all-of-added

  • ○

    added AzureTransitGateway BaseTransitGatewayResponse to the data/items/oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse] response property allOf list for the response status 200

    response-property-all-of-added

• May 14, 202587c135153b84○3See the full diff
  • ○

    added the optional property data/items/oneOf[subschema #1: AWS Transit Gateway]/state_metadata to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property data/items/oneOf[subschema #2: AWS VPC Peering Gateway]/state_metadata to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property data/items/oneOf[subschema #3: Azure Transit Gateway]/state_metadata to the response with the 200 status

    response-optional-property-added

  This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog