Delete a private catalog item
Deletes one of the caller's own private items, its versions, and every project's record of installing it. An item owned by another user answers with the same 404 as an item that does not exist, so the route cannot be used to confirm that someone else's item exists.
Deletes one of the caller's own private items, its versions, and every project's record of installing it. An item owned by another user answers with the same 404 as an item that does not exist, so the route cannot be used to confirm that someone else's item exists.
Path Parameters
The item to delete.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/catalog/items/string"{ "ok": true}Read a catalog item GET
Returns one item with every published version. A private item owned by another user answers with the same 404 as an item that does not exist, so the response never confirms the existence of someone else's item.
Set up a putty pool POST
Mines a CREATE2 salt so the hook's address carries its permission bits, then builds the three transactions that stand the pool up: deploy the hook, initialise the pool, add liquidity. The server does not sign and does not send. The order matters — the pool records the hook address, and liquidity cannot exist in a pool that does not — so the transactions are returned in sequence and must be signed in order. Every pool putty sets up charges putty's fee on each swap, so this route refuses while `PUTTY_TREASURY_ADDRESS` is the zero address on a non-fork chain. The fee is fixed at construction: there is no function anywhere that can raise it or redirect the treasury, so a pool's terms are settled the moment it exists.