All Products
Search
Document Center

Virtual Private Cloud:CreateRouteEntry

Last Updated:May 14, 2024

Creates a custom route entry in the route table of a VRouter or virtual border router (VBR).

Operation description

  • CreateRouteEntry is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the DescribeRouteEntryList operation to query the status of the task:

    • If a route is in the Creating state, the route is being added.
    • If a route is in the Created state, the route is added.
  • You cannot repeatedly call CreateRouteEntry within a specific period of time.

When you call this operation to add a custom route entry to the route table of a vRouter, take note of the following limits:

Note When you add a route entry from a prefix list, the quota usage is calculated by adding the number of existing route entries and the maximum number of route entries of the prefix list.
  • A route table can contain up to 200 custom route entries.

  • The destination CIDR block (DestinationCidrBlock) of a custom route entry cannot be the same as or be a subset of the CIDR block of a vSwitch in the virtual private cloud (VPC). The destination CIDR block can contain the CIDR block of a vSwitch.

  • The destination CIDR block (DestinationCidrBlock) of a custom route entry cannot be 100.64.0.0/10 or a subset of it.

  • The destination CIDR blocks (DestinationCidrBlock) of route entries in the same route table must be unique.

  • If you do not include the mask length when you specify the destination CIDR block (DestinationCidrBlock), the destination CIDR block is considered a host IP address whose mask length is 32 bits.

  • Multiple custom route entries can point to the same next hop (NextHopId).

  • The next hop (NextHopId) of a custom route entry must in the same VPC as the route table.

  • Equal-cost multi-path (ECMP) routing can be configured by specifying the NextHopList parameter.

    • When you add non-ECMP route entries, you must specify DestinationCidrBlock, NextHopType, and NextHopId, and you must not specify NextHopList.
    • When you add route entries for ECMP routing, you must specify DestinationCidrBlock and NextHopList, and you must not specify NextHopType or NextHopId.

When you call this operation to add a custom route entry to the route table of a VBR, take note of the following limits:

  • A route table can contain up to 200 custom route entries.
  • NextHopList is not supported.
  • The destination CIDR block (DestinationCidrBlock) of a custom route entry cannot be 100.64.0.0/10 or a subset of it.
  • The destination CIDR blocks (DestinationCidrBlock) of route entries in the same route table must be unique.
  • If you do not include the mask length when you specify the destination CIDR block (DestinationCidrBlock), the destination CIDR block is considered a host IP address whose mask length is 32 bits.
  • Multiple custom route entries can point to the same next hop (NextHopId).
  • The next hop (NextHopId) of a custom route entry must be a router interface associated with the VBR.
  • You can add route entries only when the VBR is in the Active state, and the Express Connect circuit associated with the VBR is in the Enabled state and is not locked due to overdue payments.
  • Only non-ECMP route entries are supported. When you add non-ECMP route entries, you must specify DestinationCidrBlock, NextHopType, and NextHopId, and you cannot specify NextHopList.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
vpc:CreateRouteEntryWrite
  • RouteTable
    acs:vpc:{#regionId}:{#accountId}:routetable/{#RouteTableId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringNo

The region ID of the route table.

You can call the DescribeRegions operation to query the most recent region list.

cn-hangzhou
RouteTableIdstringYes

The ID of the route table to which you want to add a custom route entry.

vtb-bp145q7glnuzd****
DestinationCidrBlockstringYes

The destination CIDR block of the custom route entry. Both IPv4 and IPv6 CIDR blocks are supported. Make sure that the destination CIDR block meets the following requirements:

  • The destination CIDR block is not 100.64.0.0/10 or a subset of 100.64.0.0/10.
  • The destination CIDR block of the custom route entry is different from the destination CIDR blocks of other route entries in the same route table.
192.168.0.0/24
NextHopIdstringNo

The ID of the next hop.

i-j6c2fp57q8rr4jlu****
ClientTokenstringNo

The client token that is used to ensure the idempotence of the request.

You can use the client to generate the value, but you must make sure that the value is unique among different requests. The ClientToken value can contain only ASCII characters.

Note If you do not specify this parameter, ClientToken is set to the value of RequestId. The value of RequestId for each API request may be different.
02fb3da4-130e-11e9-8e44-001****
RouteEntryNamestringNo

The name of the custom route entry that you want to add.

The name must be 1 to 128 characters in length, and cannot start with http:// or https://.

test
DescriptionstringNo

The description of the custom route entry.

The description must be 1 to 256 characters in length, and cannot start with http:// or https://.

test
NextHopTypestringNo

The type of next hop of the custom route entry. Valid values:

  • Instance: an Elastic Compute Service (ECS) instance. This is the default value.
  • HaVip: a high-availability virtual IP address (HAVIP).
  • RouterInterface: a router interface.
  • NetworkInterface: an elastic network interface (ENI).
  • VpnGateway: a VPN gateway.
  • IPv6Gateway: an IPv6 gateway.
  • NatGateway: a NAT gateway.
  • Attachment: a transit router.
  • VpcPeer: a VPC peering connection.
RouterInterface
NextHopListobject []No

The next hop list.

NextHopIdstringNo

The ID of the next hop of the ECMP route.

ri-2zeo3xzyf3cd8r4****
WeightintegerNo

The weight of the next hop of the ECMP route entry.

10
NextHopTypestringNo

The type of next hop of the ECMP route entry. Set the value to RouterInterface.

RouterInterface

Response parameters

ParameterTypeDescriptionExample
object

The returned information.

RouteEntryIdstring

The ID of the custom route entry.

rte-sn6vjkioxte1gz83z****
RequestIdstring

The ID of the request.

0ED8D006-F706-4D23-88ED-E11ED28DCAC0

Examples

Sample success responses

JSONformat

{
  "RouteEntryId": "rte-sn6vjkioxte1gz83z****",
  "RequestId": "0ED8D006-F706-4D23-88ED-E11ED28DCAC0"
}

Error codes

HTTP status codeError codeError messageDescription
400IllegalParam.CidrBlockThe specified CidrBlock is illegal.The operation failed because CidrBlock is set to an invalid value.
400QuotaExceededRoute entry quota exceeded in this route table.The number of route entries in the route table has reached the upper limit.
400MissingParameterMiss mandatory parameter.Some required parameters are not specified. Specify all required parameters and try again.
400InvalidCidrBlock.MalformedSpecified CIDR block is not valid.The format of the CIDR block is invalid.
400InvalidCIDRBlock.DuplicateSpecified CIDR block is already exists.This CIDR block already exists in the routing table.
400IncorrectVpcStatusCurrent VPC status does not support this operation.This operation cannot be performed when the VPC is in the current state.
400IncorrectInstanceStatusCurrent instance status does not support this operation.This operation cannot be performed while the instance is in the current state.
400IncorrectRouteEntryStatusSome route entry status blocked this operation.The operation is not supported because the route table contains routes in the Pending or Modifying state.
400IncorrectVSwitchStatusThe current virtual switch status does not support this operation.The error message returned because the vSwitch is in the Pending state and cannot be deleted.
400InvalidCidrBlockSpecified CIDR block is not valid.Possible causes include: 1. The CIDR block does not exist on the subnet whitelist. 2. The block being added must not exist in another vSwitch within this VPC. 3. The CIDR block must not be 100.64.0.0/10.
400InvalidNextHopTypeSpecified parameter "NextHopType" is not validThe specified next hop type is invalid.
400InvalidNextHop.NotFoundSpecified next hop does not exist.The specified next hop does not exist.
400InvalidVRouter.NotFoundvRouter not exists.The specified vRouter does not exist. Check whether the specified vRouter is valid.
400InvalidVPC.NotFoundvpc not exists.The VPC does not exist. Check whether the specified VPC is valid.
400InvalidNexthopTypeAndList.BothNullboth nexthopType and nextHopList are null.NextHopType and NextHopList are not specified.
400InvalidNexthopTypeAndList.BothNotNullboth nexthopType and nextHopList are not null.You cannot leave both NextHopType and NextHopList empty.
400InvalidRouterInterfaceinvalid router interface.The specified router interface does not exist.
400InvalidOppositeRouterTypenexthop list cannot only contain router interface whose opposite router interface is on vbr.The specified next hop is invalid. The peer router of the router interface that you specify as the next hop must be a VBR.
400InvalidNexthopListSizenexthop size is illegal. Must be between 2 and 4.You must specify two to four router interfaces as next hops.
400InvalidEntryRuleQuota.NotFoundRoute entry quota rule not exists.The quota rules of route entries do not exist.
400Forbidden.CheckEntryRuleQuotaRoute entry quota rule check error.An error occurred when the system was checking the quota of route entries.
400InvalidVBRStatusinvalid virtual border router status.The VBR is in an invalid state.
400InvalidPhysicalConnectionBusinessStatusinvalid physical connection business status.The Express Connect circuit is in an invalid state.
400InvalidRouterTypeCannot specify nexthop list in vbr's route table.-
400IncorrectHaVipStatusThis operation is denied because satus of the specified HaVip is neither Available nor InUse.You cannot perform the operation when the specified HAVIP is in the Available or InUse state.
400CountLimitExceed.HaVipRouteEntryThe count of route entry to HaVip in one route table is exceeded.The number of routes that point to the HAVIP in a route table exceeds the upper limit.
400InvalidRouteEntry.DuplicateThe route entry already exist.The specified route entry already exists.
400IncorrectRouteEntryStatusSpecified routeEntry status error.The operation is not supported because the route table contains routes in the Pending or Modifying state.
400IncorrectRouteEntryStatusVBR has NotStable route entry.The operation is not supported because the route table contains routes in the Pending or Modifying state.
400InvalidParamThe Ecmp routerEntry with router interfaces local vgw vip not match.The Ecmp routerEntry with router interfaces local vgw vip not match.
400INVALID_WEIGHT_PARAMSpecified value of weight invalidThe specified weight is invalid.
400FORBIDDEN_USE_VPC_AS_INTERNET_GATEWAYThe Specified CIDR must be in vpc CIDR.The specified CIDR block must be a subset of the VPC CIDR block.
400InvalidNexthopThe Specified nexthop illegal.-
400INVALID_VPC_IDThe Specified VpcId not match.The specified VPC does not exist.
400InvalidRouteEntrySizeThe Specified routerEntry size not legal.You must specify two to four router interfaces as next hops if you want to configure ECMP routing.
400TaskConflictThe operation is too frequent, please wait a moment and try again.Your requests are too frequent. Try again later.
400InvalidRouteEntrySpecified routeEntry not exist.The specified route entry does not exist.
400InvalidDestinationCidrBlockThe specified destinationCidrBlock must not included in black list cidr.-
400Forbidden.VRouterNotFoundSpecified virtual switch is not found during access authentication.The specified vSwitch is not found during access authentication.
400DefaultValidate.Errorvalidte fail.-
400Region.NotSupportThe specified region does not currently support nextHopType for networkInterface-
400OperationFailed.NotifyCenCreateFailed to notify cen when create route entry.-
400Forbidden.PrivateIpNotFoundPrivate ip address not exist.-
400RouteConflict.AlreadyExistRoute conflict exists in routing table.Route conflicts exist in the route table.
400OperationUnsupported.InactiveModeVpc multi scope route only support active standby.-
400InvalidRouteEntryName.MalformedSpecified RouteEntry name is not valid.The new name of the route is invalid.
400IncorrectStatus.MultiScopeRiRouteEntryMultiScope ri status must not in idle.-
400OperationUnsupported.MoreThanOneVpnOrHavipMultiScope can not support more than one vpn/havip.-
400OperationUnsupported.EcmpRiTypeOrNumberEmcp entry not supported if vpc-vbr or vbr-vlan ri does not exist.-
400Duplicated.VpcNextHopRoute entry nexthop duplicate.Duplicate next hops are specified.
400OperationUnsupported.SubRouteTableECMPVpc subRouteTable don't support ecmp or multiScope.-
400InvalidNexthop.NotFoundVRouterEntry nexthop does not exist.-
400IllegalParam.NextHopIdInstance not exists or not vpc vm.-
400InvalidVpnInstanceId.NotFound%s-
400OperationFailed.ScopeActiveRouteEntryType%s-
400OperationFailed.ScopeStandbyRouteEntryQuota%s-
400OperationFailed.ScopeActiveRouteEntryQuota%s-
400OperationUnsupported.ScopeInvalidRouteType%s-
400OperationFailed.EcmpInvalidRouterInterfaceOppositeType%s-
400OperationUnsupported.Ipv6EcmpRouteEntry%s-
400OperationUnsupported.Ipv6CidrBlock%s-
400OperationUnsupported.Ipv6ForVBR%s-
400QuotaExceeded.HaVipRouteEntryVpc havip route entry quota exceed.-
400InvalidNexthop.DirectEniThe direct Eni cannot be nexthop.An ENI in cut-through mode cannot be specified as a next hop.
400OperationFailed.InvalidNexthopvpc multi scope route must has a enable nexthop.-
400OperationFailed.NotifyCenDeleteFailed to notify cen when delete route entry.-
400InvalidNatGateway.NotFoundNatgateway not exist.-
400OperationFailed.CxpRouteExistCxp route alreay existed.-
400IncorrectStatus.RouteTableStatus%s-
400OperationFailed.GetEniInfoFailed to get networkInterface info.-
400QuotaExceeded.EcmpRouteEntryNextHopCount%s-
400OperationFailed.InvalidNextHopType%s-
400OperationUnsupported.InvalidRouterInterfaceTypeOnly vpc vbr interface support ecmp route.-
400InvalidHaVip.NotFoundThe specified HaVip does not exist in the specified region.-
400OperationFailed.MultiScopeTypeThe specified nexthop type is not support in multiScope.-
400OperationFailed.DistibuteLockDistibute lock fail.-
400QuotaExceeded.VpnRouteEntryVpn route entry quota exceeded.The system failed to create the route because the number of routes in the VPN gateway route table has reached the upper limit.
400InvalidAttachment.NotFoundThe attachment is not found.The specified transit router does not exist.
400OperationFailed.ActiveNetworkInterfaceNotFoundNo active network interface is found on the attachment.No ENI is available on the specified transit router.
400InvalidNetworkInterface.NotFoundThe network interface is not found on the attachment.No ENI is associated with the specified transit router.
400OperationFailed.QueryAttachmentInfoFailed to query attachment information.The system fails to query the transit router.
400IllegalParam.AttachmentIdThe attachment is invalid.The specified transit router is invalid.
400OperationFailed.NotSupportIPV6The specified next hop does not support IPv6.The specified next hop does not support IPv6.
400IncorrectStatus.Ipv6AddressThe IPv6 address of the specified next hop is being assigned or deleted.The IPv6 address that is specified as the next hop is being created or being deleted.
400OperationUnsupported.Ipv6EntryOnPrimaryNetworkInterfaceYou cannot create IPv6 route entries on a primary network interface.You cannot create an IPv6 route whose next hop is a primary ENI.
400OperationUnsupported.SpecifyIpOnIpv6EntryYou cannot specify the private IP address when you create IPv6 route entries.You cannot specify a private IPv6 address as the destination CIDR block.
400OperationUnsupported.MutipleIpv6AddressYou cannot specify a next hop that has bound multiple IPv6 addresses.You cannot specify a next hop that is assigned multiple IPv6 addresses.
400OperationDenied.Ipv6EntryOnCustomTableYou cannot create any IPv6 route entry on a custom route table.-
400OperationDenied.CloudBoxVbrEntryAllowedInCustomRouteTableThe operation is not allowed because only the custom routing table can add a routing entry with the next hop pointing to the cloud box type VBR.-
400OperationDenied.RouteTableAssociateNotCloudBoxVSwitchThe operation is not allowed because of the routing table is bound to a non-cloud box type vswitch, and routing entries pointing to the cloud box VBR cannot be added.The operation is not allowed because the route table is associated with a non-CloudBox vSwitch. You cannot add routes that point to VBRs of the CloudBox instance.
400OperationDenied.VbrMisMatchCloudBoxThe operation is not allowed because the routing table is bound to a cloud box vswitch, and routing entries pointing to other cloud box VBRs cannot be added.The operation failed because the route table is associated with the vSwitch of a CloudBox instance. You cannot add routes that point to VBRs of other CloudBox instances.
400OperationDenied.VbrIdleThe operation is not allowed because the next hop of the added routing entry is a VBR type RI at the opposite end, which cannot be in an idle state.The operation failed because the next hop of the added route is a router interface whose peer device is a VBR, and the VBR must not be in the Idle state.
400OperationDenied.RouterInterfaceToDifferentVpcThe operation is not allowed because the router interface is connected to different VPCs.The operation failed because the router interfaces point to different VPCs.
400OperationDenied.RouterInterfaceFromDifferentZonesThe operation is not allowed because the router interface resides in different zones.-
400OperationFailed.PconnTrafficNotEnableThe operation is failed because of PconnTrafficNotEnable.Billing for outbound data transfer is disabled.
400ResourceNotFound.VpcPeerThe specified resource of %s is not found.The peer VPC cannot be found.
400IncorrectStatus.VpcPeerThe status of %s [%s] is incorrect.The status of %s[%s] is invalid.
400OperationDenied.RouteTableTypeNotPermittedThe operation is not allowed because the type of route table is not permitted.You cannot create routes for route tables of the specified type.
400OperationDenied.GatewayRouteTableNotPermittedThe operation is not allowed to create a route pointing to this nextHop type on gateway route table.You cannot create routes that point to instances of this type in the gateway route table.
400UnsupportedFeature.VpcPeerIpv6IPv6 route entries for VPC peering connections cannot be created in this region.The error message returned because the peer of the router interface is a VPC and you cannot create a route whose next hop type is IPv6 address in this region.
400OperationDenied.VpcIpv6NotEnabledIPv6 has not been enabled for the VPC.The error message returned because the VPC does not support IPv6 and the operation is denied.
400IncorrectStatus.Ipv4GatewayThe status of Ipv4Gateway is incorrect.The error message returned because the IPv4 gateway is unstable.
400ResourceNotFound.PrefixListThe specified resource of prefixList is not found.The prefix list does not exist.
400UnsupportedFeature.CreatePrefixListEcmpRouteEntryThe feature of creating ecmp route entry with prefixList is not supported.You cannot create ECMP routes by using a prefix list.
400OperationDenied.RouterInterfaceIpv6NotEnabledRouterinterface does not support IPv6.The operation failed because the router interface does not support IPv6.
400OperationDenied.NextHopTypeNotPermittedThe operation is not allowed because the nextHop type is invalid.You are not allowed to create a route whose next hop is of this type.
400ResourceAlreadyAssociated.PrefixListThe operation failed because the specified prefixList route entry already exists.The operation failed because the prefix list route already exists.
400OperationFailed.CidrConflictWithPrefixListThe specified CIDR block already exists in a prefixList route entry.The route conflicts with an existing prefix list route.
400ResourceNotFound.Ipv4GatewaySpecified Ipv4Gateway does not exist.The specified IPv4 gateway is not found.
400Mismatch.HaVipIdAndRouteTableIdThe HaVip and RouteTable are mismatched.The specified HAVIP and route table do not belong to the same VPC.
400OperationFailed.OperationLockedThe operation failed because the nextHop instance is in the O&M lock state.The operation failed because the next hop instance is locked for O&M.
400Mismatch.Ipv4GatewayIdAndRouteTableIdThe specified IPv4Gateway and RouteTable are not matched.The operation failed because the IPv4 gateway and route table do not belong to the same VPC.
400OperationUnsupported.DestinationCidrBlockOverlapWithVSwitchThe destination IPv6 network segment specified in the route entry overlaps with the vSwitch network segment.The error message returned because the destination IPv6 CIDR block of the route overlaps with the vSwitch CIDR block.
400ResourceNotAssociated.CenThe Vpc and Cen are not associated.Failed to attach the VPC to the CEN instance.
400IncorrectStatus.CenRelationThe status of Vpc in Cen is incorrect.The operation failed because the VPC attached to the CEN instance is in an unstable state.
400OperationDenied.CenTypeInvalidThe operation is not allowed because of Cen type is invalid..You cannot add a route that points to a CEN instance of this type to the route table.
400ResourceNotFound.CenThe specified resource of Cen is not found.The operation failed because the CEN resources do not exist.
400ResourceNotFound.NetworkInterfaceThe specified resource of network interface is not found.The specified ENI does not exist.
403IncorrectInstanceStatusThe current status of the resource does not support this operation.The specified resource is in a state that does not support the operation.
404InvalidParameterInstance not exists or not vpc vm-
404InvalidNatGatewayId.NotFoundSpecified value of NatGatewayId is not found in our record.-
404InvalidInstanId.NotFoundSpecified instance does not exist.The specified instance does not exist.
404InvalidNextHopId.NotFoundSpecified next hop does not exist.The next hop does not exist.
404InvalidRouteTableId.NotFoundSpecified route table does not exist.The specified route table does not exist.
404InvalidHaVipId.NotFoundThe specified HaVip does not exist in the specified VPC.The specified HAVIP does not exist in the VPC.
404InvalidNetworkInterface.NotFoundThe specified networkInterface does not exist.-
404InvalidVpc.NotFoundSpecified vpc is not found in our record.-
404OperationFailed.InstanceDismatchCurrentVpcThe specified instance does not exist in current vpc.The specified instance does not exist in the VPC.
404InvalidIpv6Gateway.NotFoundSpecified Ipv6Gateway does not exist.-
500VPC.ERRORerror code 500,Internal server error.-
500InternalErrorThe request processing has failed due to some unknown error, exception or failure.An internal error occurred.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-04-02The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2024-03-25The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2024-01-04The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-09-25The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-09-01The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-07-25API Description Update. The Error code has changedsee changesets
Change itemChange content
API DescriptionAPI Description Update.
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-06-25The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-06-21The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-06-16The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-06-09The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-06-07The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-06-06The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-05-05The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-05-04The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-04-04The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500
2023-03-07The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 500