list-presentations

List Presentations

Wraps the prezento-app listMyPresentationsPublic Cloud Function. Returns up to 100 of the user's most recently created shared presentations.

Prerequisites

• PREZENTO_API_KEY in ~/.codika/.env (run setup-prezento if you don't have one)
• Scope presentations:read (or presentations:write which implicitly grants read)

Steps

source ~/.codika/.env
curl -sS \
  -H "X-Process-Manager-Key: $PREZENTO_API_KEY" \
  "https://europe-west1-prezento-app.cloudfunctions.net/listMyPresentationsPublic"

Expected response

{
  "presentations": [
    {
      "id": "01a3b…",
      "title": "Q4 board deck",
      "version": 3,
      "createdAt": "2026-04-18T12:34:56.000Z",
      "updatedAt": "2026-04-18T15:00:00.000Z",
      "archived": false,
      "totalViews": 12,
      "lastViewedAt": "2026-04-19T08:00:00.000Z",
      "shareUrl": "https://europe-west1-prezento-app.cloudfunctions.net/getSharedPresentation/01a3b…?token=…"
    }
  ]
}

Sorted by createdAt descending. shareUrl is null for archived presentations or those with no active token.

Presenting results to the user

• If empty: "You haven't shared any presentations yet. Generate one with generate-presentation and share it with share-presentation."
• If non-empty: render a compact list with title, version (v3), totalViews (12 views), and the share URL. Markdown table works well.
• If the user asked for a specific presentation by name, filter the results client-side and surface the match's shareId so they can pass it to update-presentation or get-presentation.

Pitfalls

• No results despite having uploaded → check that the API key belongs to the same user/org as the upload (each user owns their own presentations; cross-user listing isn't supported)
• Pagination → capped at 100. v1 has no cursor parameter. If a power user has more, they'll only see the latest 100.
• Wrong scope → 403. Re-run setup-prezento and grant presentations:read (or presentations:write).

Output checklist

• API key resolved
• List returned 200
• Results presented in a scannable format
• If the user asked for a specific deck, the matching shareId is highlighted so they can act on it