Cancel a fill — completed chunks stay cached; nothing is rolled back
const url = 'http://localhost:11044/api/v1/admin/kg/fills/example';const options = {method: 'DELETE', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url http://localhost:11044/api/v1/admin/kg/fills/example \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The fill’s id (fill_ plus 12 characters), as start or list returned it, matched only among the acting user’s fills; an id that matches nothing is not refused and still answers CANCELLED
Query Parameters
Section titled “Query Parameters”Username to act as; when it resolves to a user it is used in preference to the authenticated principal. Omitted or blank, the authenticated principal acts; 401 when neither resolves
Responses
Section titled “Responses”The cancelled fill’s id and its new state
A cancelled fill: which one, and the state it is now in
object
The fill’s id, echoed back unchanged
Always CANCELLED. Completed chunks stay cached and nothing is rolled back, so this says the fill stopped rather than that its work was undone
Example
{ "state": "CANCELLED"}No authenticated principal and no resolvable username
A refusal carrying only a human-readable reason.
object
What went wrong, in the terms the caller can act on.
Example generated
{ "error": "example"}