Delete fact

Removes a verified fact. Alignment runs after this stop checking responses against it; verdicts already recorded are unchanged.

Requires the write:brand_profile scope, and the workspace must be enabled for API writes.


DELETE /v1/brands/{brand_id}/facts/{fact_id}

Authorization

Header	Type	Required
`Authorization`	`Bearer asky_sk_…`	required
`Idempotency-Key`	`string`	required

Path parameters

Parameter	Type	Required	Description
`brand_id`	`uuid`	required	From List brands
`fact_id`	`uuid`	required	From `verified_facts[].id` on Get brand profile

Query parameters

None.

Unlike Delete topic, there is no outcome parameter: a fact owns nothing beneath it, so there is no second decision to make.

Request

cURL


curl --request DELETE \
  --url 'https://api.askylabs.com/v1/brands/242546de-4cee-4a7d-952e-f6aa60c63ef8/facts/9f2c1d84-6b31-4a2e-9c77-1e5b0a3f8d42' \
  --header 'Authorization: Bearer <api-key>' \
  --header 'Idempotency-Key: <unique-per-attempt>'

Python


import requests
 
url = "https://api.askylabs.com/v1/brands/242546de-4cee-4a7d-952e-f6aa60c63ef8/facts/9f2c1d84-6b31-4a2e-9c77-1e5b0a3f8d42"
 
headers = {"Authorization": "Bearer <api-key>",
    "Idempotency-Key": "<unique-per-attempt>"}
 
response = requests.delete(url, headers=headers)
 
print(response.text)

JavaScript


const options = {
  method: 'DELETE',
  headers: {Authorization: 'Bearer <api-key>', 'Idempotency-Key': '<unique-per-attempt>'}
};
 
fetch('https://api.askylabs.com/v1/brands/242546de-4cee-4a7d-952e-f6aa60c63ef8/facts/9f2c1d84-6b31-4a2e-9c77-1e5b0a3f8d42', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

Response

200


{
  "data": {
    "deleted_fact_id": "9f2c1d84-6b31-4a2e-9c77-1e5b0a3f8d42"
  },
  "request_id": "req_7d21b0af59c34e18b6ac"
}

401


{
  "error": {
    "code": "token_revoked",
    "message": "This API key was revoked.",
    "request_id": "req_8f21c0aa47b1490d2e63"
  }
}

404


{
  "error": {
    "code": "not_found",
    "message": "fact_id not found for this brand.",
    "request_id": "req_5b0e77d213a94f6a8ce1"
  }
}

429


{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Retry after 24 seconds.",
    "request_id": "req_31c9ba7f0e5d4a118cc2"
  }
}

Response fields

Field	Type	Description
`data.deleted_fact_id`	`uuid`	required. The fact that was removed
`request_id`	`string`	required. Also returned as the `x-request-id` header

Errors

Status	Code	When
401	`invalid_token`	The key is missing, malformed, or does not exist
403	`insufficient_scope`	The key does not carry `write:brand_profile`
403	`plan_required`	This workspace is not enabled for API writes
404	`not_found`	The fact does not exist, was already deleted, belongs to another brand, or belongs to an alignment category
429	`rate_limited`	Over 60 requests per minute. See the `Retry-After` header

Notes

Deleting twice returns 404, not a second success. The fact is gone after the first call, and reporting success for a row that no longer exists would hide a bug in a client’s bookkeeping.

Past alignment verdicts are not rewritten. A verdict recorded against this fact stays in the history; only future runs stop checking it.

Idempotency-Key is required. Reuse it when retrying an attempt and the original response is replayed rather than a second delete being attempted. See Idempotency.