Skip to content

Delete a brush pack

DELETE
/brush-packs/{packId}

Permanently removes one of your packs and its stamp manifest rows.

You need to be signed in with a session or API token. This handler returns 404 when you aren’t signed in, when the pack doesn’t exist and when someone else owns it; there’s no administrator override. An invalid UUID can get 400 before the handler runs. The schema lists a shared 401 response, but this handler uses 404 for a missing identity.

A successful deletion returns 204 with no body. The database deletes the pack and cascades to its stamp rows in one statement. There’s no trash or restore. Deleting the same pack again normally gets 404, and two concurrent deletions of an existing pack can produce one 204 and one 404.

The endpoint doesn’t delete bitmap bytes, release storage pins or schedule cleanup. Brush imports write straight to the storage backend without registering their bytes or pins in the normal storage tables. No implemented garbage collector removes these leftover bitmaps; an integrity scan can report unregistered bytes but doesn’t delete them.

After the rows are gone, new stamp requests normally fail the ownership lookup. A stream authorized before the deletion may still finish, and deleting a pack doesn’t recall images or tinted copies a browser already holds.

packId
required
string format: uuid

Pack UUID from an import or a catalogue read. Ownership is checked against the current account, and the same 404 covers a missing pack and another account’s pack. A malformed UUID gets 400 before the operation handler runs.

The pack and stamp rows were deleted; no response body. Stored bitmaps and existing client copies are not removed.

Authentication required, missing, or invalid

object
error
required

Human-readable error summary

string
Example
the request could not be completed
Example
{
"error": "authentication required: sign in and retry with a valid session or API token"
}

Resource not found

object
error
required

Human-readable error summary

string
Example
the request could not be completed