Read a catalog item
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.
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.
Path Parameters
The item to read.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/catalog/items/string"{ "id": "string", "kind": "template", "status": "official", "title": "string", "description": "string", "tags": [ "string" ], "installs": 0, "ownerId": "string", "version": "string", "usage": "string", "compatibleTemplates": [ "string" ], "dependencies": [ "string" ], "registryDependencies": [ "string" ], "files": [ { "path": "string", "content": "string" } ], "reviewNote": "string", "createdAt": "string", "updatedAt": "string", "versions": [ { "version": "string", "manifest": null, "registry": null, "reviewNote": "string", "createdAt": "string" } ]}Save a private catalog item POST
Saves a file set as a private catalog item owned by the caller — the "My snippets" path. The item is immediately usable in any of the caller's own projects with no review, and invisible to every other user: it is not merely hidden from the list, it is not readable, installable, or deletable by anyone else. The status is always `private`; publishing is a separate review flow and this route deliberately does not offer it.
Delete a private catalog item DELETE
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.