Delete a conversion

DELETE/api/cache/{id}

Removes one conversion. What gets removed depends on who asks:

- Admin, or anyone when sign-in is off: the shared cache row, for every user, along with its share link (scope: global). - Regular user: only the entry in your own history. The shared row and its share link keep working (scope: user).

With DISABLE_PUBLIC_HISTORY on, a caller who isn't signed in gets 403. With sign-in off, that means nobody can delete.

Authorizations

Authorizationstringheader

Needed only when the instance has sign-in enabled (PULLMD_AUTH_MODE is single-admin or multi-user). Send Bearer pmd_<key> with an API key created at /settings. In single-admin mode, the legacy PULLMD_AUTH_TOKEN is also accepted as a bearer token. OAuth access tokens work only on /mcp. Browser sessions use the pullmd_session cookie instead.

Path parameters

idintegerrequired

The numeric id from /api/history or /api/archive. Conversion responses carry only the share id. To delete a conversion you made, list /api/history and take the id of the item whose share_id matches. Don't pass a share id here. The id is read up to its first non-digit, so a share id that starts with digits (such as 676e61c8…) is taken as id 676.

Example: 42

Response

200 · application/json

The entry was removed.

okboolean

Always true.

idinteger

The id that was removed.

scopestring

global: the entry was deleted from the cache for everyone (admin, or sign-in off). user: it was removed from your own history only; the cached page stays for others.

Available options: globaluser

cURLcURLPythonJavaScript

curl --request DELETE \
  --url 'http://localhost:3000/api/cache/{id}' \
  --header 'Authorization: Bearer <token>'

{
  "ok": true,
  "id": 42,
  "scope": "global"
}