Updated on 2023-06-29 GMT+08:00

Querying Signature Keys Bound to an API

Function

This API is used to query the signature keys that have been bound to a specified API. Only one signature key can be bound to an API in an environment.

URI

GET /v2/{project_id}/apic/instances/{instance_id}/sign-bindings/binded-signs

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.

Table 2 Query Parameters

Parameter

Mandatory

Type

Description

offset

No

Long

Offset from which the query starts. If the offset is less than 0, the value is automatically converted to 0.

Default: 0

limit

No

Integer

Number of items displayed on each page.

Minimum: 1

Maximum: 500

Default: 20

api_id

Yes

String

API ID.

sign_id

No

String

Signature key ID.

sign_name

No

String

Signature key name.

env_id

No

String

Environment ID.

Request Parameters

Table 3 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).

Response Parameters

Status code: 200

Table 4 Response body parameters

Parameter

Type

Description

size

Integer

Length of the returned resource list.

total

Long

Number of resources that match the query conditions.

bindings

Array of SignApiBindingInfo objects

List of binding relationships between APIs and signature keys.

Table 5 SignApiBindingInfo

Parameter

Type

Description

publish_id

String

API publication ID.

api_id

String

API ID.

group_name

String

API group name.

binding_time

String

Time when the policy is bound to the API.

env_id

String

ID of the environment in which the API was published.

env_name

String

Name of the environment in which the API was published.

api_type

Integer

API type.

api_name

String

API name.

id

String

Binding record ID.

api_remark

String

API description.

sign_id

String

Signature key ID.

sign_name

String

Signature key name, The value contains 3 to 64 characters, including letters, digits, and underscores (_). It must start with a letter.

sign_key

String

Signature key.

  • hmac: The value must start with a letter or digit and can include letters, digits, underscores (_), and hyphens (-) (8 to 32 characters). If not specified, a key is automatically generated.

  • basic: The value must start with a letter and can include letters, digits, underscores (_), and hyphens (-) (4 to 32 characters). If not specified, a key is automatically generated.

  • public_key: The value can start with a letter, digit, plus sign (+), or slash (/), and can include letters, digits, underscores (_), hyphens (-), plus signs (+), and slashes (/) (8 to 512 characters). If not specified, a key is automatically generated.

  • aes: The value contains 16 characters if the aes-128-cfb algorithm is used or 32 characters if the aes-256-cfb algorithm is used. Letters, digits, and special characters (_-!@#$%+/=) are allowed. It must start with a letter, digit, plus sign (+), or slash (/). If not specified, a key is automatically generated.

sign_secret

String

Signature secret.

  • hmac: The value must start with a letter or digit, and can include letters, digits, and special characters (_-!@#$%) (16 to 64 characters). If not specified, a key is automatically generated.

  • basic: The value must start with a letter or digit, and can include letters, digits, and special characters (_-!@#$%) (8 to 64 characters). If not specified, a key is automatically generated.

  • public_key: The value can start with a letter, digit, plus sign (+), or slash (/), and can include letters, digits, and special characters (_-!@#$%+/=) (15 to 2048 characters). If not specified, a key is automatically generated.

  • aes: The value contains 16 characters, including letters, digits, and special characters (_-!@#$%+/=). It must start with a letter, digit, plus sign (+), or slash (/). If not specified, a key is automatically generated.

sign_type

String

Signature key type:

  • hmac

  • basic

  • public_key

  • aes

To use a basic signature key, ensure that your instance version supports it. Contact technical support to upgrade your instance if needed.

To use a public_key signature key, ensure that the public_key feature has been configured for your instance. For details, see "Appendix" > "APIC Features Supported by ROMA Connect Instances". If your instance does not support this feature, contact technical support to enable it.

To use an AES signature key, ensure that your instance version supports it. Contact technical support to upgrade your instance if needed.

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

None

Example Responses

Status code: 200

OK

{
  "total" : 1,
  "size" : 1,
  "bindings" : [ {
    "api_id" : "5f918d104dc84480a75166ba99efff21",
    "group_name" : "api_group_001",
    "binding_time" : "2020-08-03T04:00:11Z",
    "env_id" : "DEFAULT_ENVIRONMENT_RELEASE_ID",
    "env_name" : "RELEASE",
    "sign_id" : "0b0e8f456b8742218af75f945307173c",
    "sign_name" : "signature_demo",
    "sign_key" : "a071a20d460a4f639a636c3d7e3d8163",
    "sign_secret" : "dc02fc5f30714d6bb21888389419e2b3",
    "api_type" : 1,
    "api_name" : "Api_http",
    "id" : "25082bd52f74442bb1d273993d567938",
    "api_remark" : "Web backend Api",
    "publish_id" : "66a645f1d6294fa6899cb1ed1c51bc4c",
    "sign_type" : "hmac"
  } ]
}

Status code: 400

Bad Request

{
  "error_code" : "APIG.2012",
  "error_msg" : "Invalid parameter value,parameterName:api_name. 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.3002",
  "error_msg" : "API 5f918d104dc84480a75166ba99efff21 does not exist"
}

Status code: 500

Internal Server Error

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

Status Codes

Status Code

Description

200

OK

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

500

Internal Server Error

Error Codes

See Error Codes.