One of the caller's showcase entries
One entry the authenticated creator owns, in any status. An entry owned by another account and an entry that does not exist answer with the same 404, so this route cannot be used to confirm that a guessed id is real.
One entry the authenticated creator owns, in any status. An entry owned by another account and an entry that does not exist answer with the same 404, so this route cannot be used to confirm that a guessed id is real.
Authorization
bearerAuth A bearer token. The Account routes accept a Privy access token; the MCP transport accepts an sk- API key issued by POST /account/api-keys.
In: header
Path Parameters
The entry's surrogate id, from POST /showcase or GET /showcase/entries. Not a public identity.
1 <= length <= 64Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/showcase/entries/string"{ "id": "string", "ownerId": "string", "slug": "string", "kit": "business", "title": "string", "summary": "string", "projectUrl": "string", "chain": "ethereum", "token": "string", "status": "draft", "templateOptIn": true, "remixCount": 0, "publishedAt": "string", "createdAt": "string", "updatedAt": "string"}Create a showcase entry POST
Create a showcase entry for the authenticated creator, as a **draft**. A draft is not public and is not listed. Call `POST /showcase/entries/{entryId}/publish` to opt in. Nothing about an entry is public until the creator says so (§6.3: "Showcase, badge, Spotlight — everyone who opts in, gate: none"), and that is why creation and publication are two calls rather than one. The `slug` is derived from the title and made unique with a numeric suffix when taken, so two creators can both make a "Coffee Shop". The slug is assigned once and never changes — including after a withdrawal — so a link that was shared can never silently resolve to a different project.
Edit one of the caller's showcase entries PATCH
Edit the copy on one entry the authenticated creator owns. `slug`, `kit`, `status`, and `remixCount` are not patchable and the request schema has no field for them: a published link cannot be repointed at a different Kit, publication is a deliberate opt-in, and a count is not a client-settable number. `templateOptIn` **is** patchable, and turning it off takes effect immediately — a remix that races the opt-out earns no credits. A foreign or missing entry id answers with the same 404 as a read.