Help Center/ ROMA Connect/ API Reference/ Service Integration APIs/ Client Quotas/ Binding Client Applications to a Client Quota
Updated on 2023-06-29 GMT+08:00
View PDF
Share

Binding Client Applications to a Client Quota

Function

Binding Client Applications to a Client Quota

URI

POST /v2/{project_id}/apic/instances/{instance_id}/app-quotas/{app_quota_id}/binding-apps

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID. For details about how to obtain the project ID, see Appendix > Obtaining a Project ID in the ROMA Connect API Reference.

instance_id

Yes

String

Instance ID.

app_quota_id

Yes

String

Client quota ID.

Request Parameters

Table 2 Request header parameters

Parameter

Mandatory

Type

Description

X-Auth-Token

Yes

String

User token, which can be obtained by calling the IAM API (value of X-Subject-Token in the response header).
Table 3 Request body parameters

Parameter

Mandatory

Type

Description

app_ids

Yes

Array of strings

Client application ID list.

Response Parameters

Status code: 201

Table 4 Response body parameters

Parameter

Type

Description

applies

Array of AppQuotaAppBinding objects

List of client applications bound to client quotas.
Table 5 AppQuotaAppBinding

Parameter

Type

Description

app_quota_id

String

Client quota ID.

app_id

String

Client application ID.

bound_time

String

Time when the policy is bound to the API.

Status code: 400

Table 6 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Status code: 401

Table 7 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Status code: 403

Table 8 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Status code: 404

Table 9 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Status code: 500

Table 10 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Example Requests

{
  "app_ids" : [ "98df09fb-d459-4cbf-83a7-2b55ca6f3d5d" ]
}

Example Responses

Status code: 201

OK

{
  "applies" : [ {
    "app_id" : "98df09fb-d459-4cbf-83a7-2b55ca6f3d5d",
    "app_quota_id" : "c900c5612dbe451bb43cbcc49cfaf2f3",
    "bound_time" : "2020-09-19T07:43:11.948178051Z"
  } ]
}

Status code: 400

Bad Request

{
  "error_code" : "APIG.2012",
  "error_msg" : "Invalid parameter value,parameterName:instance_id. Please refer to the support documentation"
}

Status code: 401

Unauthorized

{
  "error_code" : "APIG.1002",
  "error_msg" : "Incorrect token or token resolution failed"
}

Status code: 403

Forbidden

{
  "error_code" : "APIG.1005",
  "error_msg" : "No permissions to request this method"
}

Status code: 404

Not Found

{
  "error_code" : "APIG.3093",
  "error_msg" : "The App quota c900c5612dbe451bb43cbcc49cfaf2f3 does not exist"
}

Status code: 500

Internal Server Error

{
  "error_code" : "APIG.9999",
  "error_msg" : "System error"
}

Status Codes

Status Code

Description

201

OK

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

500

Internal Server Error

Error Codes

See Error Codes.

Parent topic: Client Quotas