Returns the authoritative destructive impact that must be confirmed before policy purge.
const url = 'https://example.com/api/v1/admin/policies/1/forced-purge-preview';const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}use reqwest;
#[tokio::main]pub async fn main() { let url = "https://example.com/api/v1/admin/policies/1/forced-purge-preview";
let mut headers = reqwest::header::HeaderMap::new(); headers.insert("Authorization", "Bearer <token>".parse().unwrap());
let client = reqwest::Client::new(); let response = client.post(url) .headers(headers) .send() .await;
let results = response.unwrap() .json::<serde_json::Value>() .await .unwrap();
dbg!(results);}curl --request POST \ --url https://example.com/api/v1/admin/policies/1/forced-purge-preview \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Policy ID
Responses
Section titled “Responses”Storage policy forced-purge impact
统一 API 响应格式
成功: { "code": "success", "msg": "", "data": {...} }
失败: { "code": "auth.credentials_failed", "msg": "Invalid Credentials" }
object
Complete impact preview that must be confirmed before destructive task creation.
object
Logical quota bytes represented by affected revisions.
Canonical revisions backed by source-policy blobs.
Blob rows whose metadata will be removed after all references are purged.
Bytes represented by source-policy blob rows.
Whether placement topology blockers have been cleared.
Exact phrase required by the destructive confirmation endpoint.
Direct shares removed with the affected files.
Distinct file histories permanently removed.
Digest binding task creation to this exact policy and impact snapshot.
Placement targets that must be detached before purge can start.
Policy selected for permanent removal.
Current policy name used by the confirmation phrase.
Current policy revision bound into the impact digest.
Affected files that are currently in trash.
Active upload sessions that the confirmed task will abandon locally.
object
object
Connector-owned field that caused a configuration validation failure.
This is intentionally optional so existing diagnostics remain wire-compatible.
Connector field scope, for example connector_config or static_credential.
Example
{ "code": "success"}Unauthorized
Forbidden
Policy not found