All Products
Search
Document Center

Virtual Private Cloud:ApplyPhysicalConnectionLOA

Last Updated:Feb 22, 2024

Applies for a Letter of Authorization (LOA) for an Express Connect circuit.

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:ApplyPhysicalConnectionLOAWrite
  • PhysicalConnection
    acs:vpc:{#regionId}:{#accountId}:physicalconnection/{#PhysicalConnectionId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
ClientTokenstringNo

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

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

Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.
123e4567-e89b-12d3-a456-426655440000
RegionIdstringYes

The region ID of the Express Connect circuit.

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

cn-hangzhou
BandwidthintegerNo

The bandwidth of the Express Connect circuit. Unit: Mbit/s.

Valid values: 2 to 10240.

3
PeerLocationstringNo

The geographic location where the Express Connect circuit is deployed.

cn-hangzhou
InstanceIdstringYes

The ID of the Express Connect circuit.

pc-bp1qrb3044eqi****
CompanyNamestringYes

The name of the customer company that requires the Express Connect circuit.

company
LineTypestringYes

The type of the Express Connect circuit. Valid values:

  • MSTP: MSTP line
  • MPLSVPN: MPLSVPN line
  • FIBRE: fiber line
  • Other: other types
FIBRE
SistringYes

The construction company.

company
ConstructionTimestringYes

The time when construction started. Specify the time in the ISO 8601 standard in the YYYY-MM-DDThh:mm:ssZ format. The time is displayed in UTC.

2022-02-28T16:00:00Z
PMInfoobject []No

The information about the construction engineer.

PMCertificateNostringYes

The ID number of the construction engineer. You can specify the ID number of an ID card or an international passport.

You can configure information for up to 16 construction engineers.

5****************9
PMNamestringYes

The name of the construction engineer.

Zhangsan
PMCertificateTypestringYes

The type of the identity document of the construction engineer. Valid values:

  • IDCard
  • Passport
IDCard
PMGenderstringYes

The gender of the construction engineer.

Male
PMContactInfostringYes

The contact information about the construction engineer.

1390000****

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

A47BD386-7FDE-42C4-8D22-C6223D18AA1C

Examples

Sample success responses

JSONformat

{
  "RequestId": "A47BD386-7FDE-42C4-8D22-C6223D18AA1C"
}

Error codes

HTTP status codeError codeError messageDescription
400MissingParam.AliUid%s-
400MissingParam.InstanceId%s-
400MissingParam.RegionNo%s-
400MissingParam.PMInfo%s-
400IllegalParam.LineOperator%s-
400IllegalParam.LineType%s-
400IllegalParam.PeerLocation%s-
400IllegalParam.PmCertificateType%s-
400IllegalParam.PmCertificateNo%s-
400IllegalParam.PmContactInfo%s-
400IllegalParam.PmGender%s-
400IllegalParam.PmName%s-
400IllegalParam.Si%s-
400InvalidConstructionTime.Malformed%s-
400InvalidInstanceId.NotFound%s-
400IncorrectStatus.PhysicalConnectionLOA%s-
400IncorrectStatus.PhysicalConnection%s-
400IllegalParam.CompanyName%s-
400OperationFailed.PconnTrafficNotEnableThe operation is failed because of PconnTrafficNotEnable.Billing for outbound data transfer is disabled.
400IllegalParam.BandwidthThe param of bandwidth is illegal.The Bandwidth parameter is set to an invalid value.

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

Change history

Change timeSummary of changesOperation
2021-11-17The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400