Querying the Change History of a Parameter Template

API Description

This API is used to view change history of a parameter template.

Restrictions

Only the parameter template change history of the last seven days can be viewed.

URI

URI format
GET https://{Endpoint}/v3/{project_id}/configurations/{config_id}/histories

**Table 1** Path parameters
Parameter	Type	IN	Mandatory	Description
project_id	string	path	Yes	Project ID of a tenant in a region. Obtain the project ID by following the instructions in Obtaining a Project ID.

**Table 2** Path parameters
Parameter	Mandatory	Type	Description
config_id	Yes	String	Parameter template ID.

**Table 3** Query parameters
Parameter	Mandatory	Type	Description
offset	No	Integer	Index offset. If offset is set to N, the resource query starts from the N+1 piece of data. The default value is 0, indicating that the query starts from the first piece of data. The value must be a positive number.
limit	No	Integer	Maximum records to be queried. The value ranges from 1 to 100. If this parameter is not transferred, the first 100 records are queried by default.

Request Parameters

**Table 4** Request header parameters
Parameter	Type	IN	Mandatory	Description
X-Auth-Token	string	header	Yes	User token

Response Parameters

Parameter description

**Table 5** Response body parameters
Name	Type	Description
histories	Array of Table 5-5 objects	Change history of the parameter template.

**Table 6** HistoryInfo
Name	Type	Description
parameter_name	String	Parameter name.
old_value	String	Value before modification.
new_value	String	New value.
updated_at	String	Modification time. The format is "yyyy-MM-ddTHH:mm:ssZ". T is the separator between the calendar and the hourly notation of time. Z indicates the time zone offset. For example, in the Beijing time zone, the time zone offset is shown as +0800.

Example response

{ 
  "histories" : [ { 
    "parameter_name" : "rateLimit.mbps", 
    "old_value" : "500", 
    "new_value" : "350", 
    "updated_at" : "2022-06-07T09:25:45+0000" 
  } ] 
}