Retrieves the sensitive data identification results from Data Security Guard.
Operation description
This API operation corresponds to the query feature on the Data Security Guard console interface. It retrieves the sensitive data identification results for a specified tenant by associating with the tenant ID.
Supports filtering by data source type, project workspace, and other dimensions.
Supports ascending or descending sorting on a specific field.
Supports paged query.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
dataworks:DsgQuerySensResult |
list |
*All Resource
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| TenantId |
string |
No |
The tenant ID. Log on to the DataWorks console, go to the DataStudio page, click the username in the upper-right corner, and choose Menu > User Info to obtain the tenant ID. |
10241024 |
| DbType |
string |
No |
The database type. Valid values:
|
ODPS.ODPS |
| ProjectName |
string |
No |
The name of the DataWorks workspace. Log on to the DataWorks console and go to the workspace configuration page to obtain the workspace name. |
project |
| SchemaName |
string |
No |
The schema name. |
schema |
| Table |
string |
No |
The table name. |
table |
| Col |
string |
No |
The field name. |
col |
| NodeName |
string |
No |
The classification node name. |
Personal information |
| Level |
string |
No |
The sensitivity level of the field. |
3 |
| SensStatus |
string |
No |
The sensitivity status of the field. Valid values:
|
1 |
| SensitiveId |
string |
No |
The ID of the sensitive field. |
10241024 |
| SensitiveName |
string |
No |
The name of the sensitive field. |
name |
| Order |
string |
No |
The sort order. Valid values:
|
DESC |
| OrderField |
string |
No |
The field used for sorting. Valid values:
|
gmt_create |
| PageNo |
integer |
No |
The page number. Minimum value: 1. |
1 |
| PageSize |
integer |
No |
The number of entries per page. Default value: 10. Maximum value: 20. |
10 |
| startDate |
string |
No |
The query start time in the format of yyyy-MM-dd or yyyy-MM-dd HH:mm:ss. |
2026-05-19 |
| endDate |
string |
No |
The query end time in the format of yyyy-MM-dd or yyyy-MM-dd HH:mm:ss. |
2026-05-19 |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response data. |
||
| Success |
boolean |
Indicates whether the call was successful. Valid values:
|
true |
| ErrorCode |
string |
The error code. |
400 |
| ErrorMessage |
string |
The error message. |
Missing parameter |
| HttpStatusCode |
integer |
The HTTP status code. |
400 |
| Data |
any |
The returned data. |
1234 |
| RequestId |
string |
The request ID. It is a unique identifier for the request. |
900000001 |
| DynamicErrorCode |
string |
The error code. The value is the same as ErrorCode. |
400 |
| DynamicErrorMessage |
string |
The error message. The value is the same as ErrorMessage. |
Missing parameter |
Examples
Success response
JSON format
{
"Success": true,
"ErrorCode": "400",
"ErrorMessage": "Missing parameter",
"HttpStatusCode": 400,
"Data": "1234",
"RequestId": "900000001",
"DynamicErrorCode": "400",
"DynamicErrorMessage": "Missing parameter"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | BADPARAMETERS | Parameters are missing or in the wrong format. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.