Querying the Deployment History of a Backend API
Function
This API is used to query the deployment records of a backend API in an instance.
URI
GET /v2/{project_id}/apic/instances/{instance_id}/livedata-apis/{ld_api_id}/deploy
|
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. |
|
ld_api_id |
Yes |
String |
Backend API ID. |
Request 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
|
Parameter |
Type |
Description |
|---|---|---|
|
size |
Integer |
Length of the returned resource list. |
|
total |
Long |
Number of resources that match the query conditions. |
|
histories |
Array of LdApiDeployHistoryInfo objects |
Deployment history objects of a backend API. |
|
Parameter |
Type |
Description |
|---|---|---|
|
id |
String |
Deployment ID. |
|
ld_api_id |
String |
ID of the deployed backend API. |
|
group_id |
String |
ID of the deployed frontend API group. |
|
env_id |
String |
ID of the deployed environment. |
|
api_id |
String |
ID of the deployed frontend API. |
|
deploy_time |
String |
Deployment time. |
|
api_definition |
LdApiInfo object |
Custom backend API details. |
|
Parameter |
Type |
Description |
|---|---|---|
|
name |
String |
Backend API name. Must start with a letter or digit and can include letters, digits, and special characters -_./(): |
|
path |
String |
Backend API request path. Start with a slash (/), and use letters, digits, hyphens (-), underscores (_), and periods (.). When updating a backend API, status=4 indicates that the backend API has been deployed. In this status, the backend API request path cannot be modified. |
|
method |
String |
Backend API request method: GET, PUT, POST, and DELETE When updating a backend API, status=4 indicates that the backend API has been deployed. In this status, the backend API request method cannot be modified. |
|
description |
String |
Backend API description, which cannot contain < and >. |
|
version |
String |
Backend API version, which contains 2 to 16 characters excluding < and >. |
|
content_type |
String |
Type of the returned backend API. |
|
api_signature_id |
String |
ID of the signature key bound to the API for signature authentication |
|
roma_app_id |
String |
ID of the integration application to which a backend API belongs. When updating a backend API, status=4 indicates that the backend API has been deployed. In this status, the ID of the integration application to which the backend API belongs cannot be modified. |
|
return_format |
Boolean |
Indicates whether to format the API response information. true: The response information is formatted. false: The response information is not formatted. |
|
parameters |
Array of LdApiParameter objects |
Backend API request parameters. |
|
id |
String |
Backend API ID. |
|
instance |
String |
ID of the instance to which the backend API belongs. |
|
type |
String |
Backend API type:
|
|
status |
Integer |
Backend API status:
|
|
created_time |
String |
Time when the backend API is created. |
|
modified_time |
String |
Time when the backend API is modified. |
|
scripts |
Array of LdApiScript objects |
Backend API script. |
|
roma_app_name |
String |
Name of the integration application to which the backend API belongs. |
|
Parameter |
Type |
Description |
|---|---|---|
|
name |
String |
Parameter name.
|
|
in |
String |
Position of the parameter during API calling:
|
|
default |
String |
Default value. |
|
description |
String |
Parameter description, which cannot contain < and >. |
|
required |
Boolean |
Whether the parameter is mandatory. true: The parameter is mandatory. false: The parameter is optional. |
|
Parameter |
Type |
Description |
|---|---|---|
|
ds_id |
String |
Data source ID. This parameter is mandatory only if api_type is set to data. |
|
ds_name |
String |
Data source name. |
|
ds_type |
String |
Data source type.
|
|
type |
String |
Script type.
|
|
object_name |
String |
Returned object. |
|
content |
String |
API script content. Perform Base64 encoding on the script. |
|
enable_result_paging |
Boolean |
Indicates whether to display the data script result on multiple pages. This parameter is mandatory only if api_type is set to data. |
|
enable_preparestatement |
Boolean |
Indicates whether to pre-compile the data script. This parameter is mandatory only if api_type is set to data. |
|
created_time |
String |
Time when the backend API script is created. |
|
modified_time |
String |
Time when the backend API script is modified. |
Status code: 400
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Status code: 401
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Status code: 403
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Status code: 404
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Status code: 500
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error description. |
Example Requests
None
Example Responses
Status code: 200
OK
{
"histories" : {
"api_id" : "1d0432f1a82a49d08b9308ae7bd96ca6",
"deploy_time" : "2020-09-28T11:01:09Z",
"env_id" : "DEFAULT_ENVIRONMENT_RELEASE_ID",
"group_id" : "01ce7564a2544713b80c7c08eb85f5d0",
"id" : "abbe44b56eda428d84172343674c9cd6",
"ld_api_id" : "bd42841c20184da6bbf457c6d8a06e37"
}
}
Status code: 400
Bad Request
{
"error_code" : "APIG.2011",
"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.3084",
"error_msg" : "The livedata API does not exist, id: bd42841c20184da6bbf457c6d8a06e37"
}
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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.