Read a brush stamp image
GET /brush-packs/stamps/{stampId}
Streams the stored PNG for a stamp in one of your packs.
You need to be signed in with a session or API token. This handler returns 404 when you aren’t signed in or when no stamp with that ID belongs to your account, including a stamp someone else owns. No permission or administrator override widens that ownership check. An invalid UUID can get 400 before the handler runs; the schema’s shared 401 isn’t the missing-identity response used here.
The database checks that the stamp belongs to one of your packs before storage is opened. A concurrent deletion after that check doesn’t necessarily stop the stream. If the manifest row exists but the stored bytes are missing or unreadable, the storage error fails the request as a server error, not the manifest-not-found 404.
The response has Content-Type: image/png and streams the current stored bytes with no conversion, PNG re-decode or checksum comparison. The handler doesn’t set Content-Length and adds no cache validators, Cache-Control policy, conditional 304 handling or byte-range support. It closes the opened reader after streaming. Each request returns one full image; there’s no pagination or multi-stamp response.
The web client starts fetching stamp images when it registers a pack, using the session cookie, then keeps the decoded images and tinted copies in memory. Removing the pack or losing access doesn’t erase copies a client already has.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Stamp UUID from a pack’s manifest. It’s the database stamp ID, not the ABR sample ID or the storage hash. A malformed UUID gets 400 before the operation handler runs; a missing or unowned stamp gets 404.
Responses
Section titled “ Responses ”The full stored stamp image, sent as image/png without a handler-supplied Content-Length.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Resource not found
object
Human-readable error summary
Example
the request could not be completed