Skip to main content

​
What a presentation is

A presentation is a Slideless record that wraps:
  • A single HTML file (≤ 10 MB) stored in private cloud storage
  • One or more share tokens (see Share tokens)
  • Metadata: title, version, owner, timestamps, view counters
You create a presentation by uploading HTML through the uploadSharedPresentation endpoint or by creating one in the dashboard.

​
Anatomy

FieldTypeDescription
idUUIDv7 stringThe shareId — appears in every share URL
ownerIdstringThe Slideless user who created it
organizationIdstringThe org context (in v1, every user has one personal org)
apiKeyIdstring | nullWhich API key created it (null if uploaded via dashboard)
titlestringDisplay title — visible in the dashboard, not in the share URL
versionnumberStarts at 1, auto-bumps on every successful update
createdAt, updatedAt, expiresAttimestampsexpiresAt is null in v1
archivedbooleanSoft-delete flag — archived presentations 404 to viewers
archivedAt, archivedBytimestamp / userIdSet when archived
tokensmapKeyed by tokenId — see Share tokens
totalViewsnumberSum across all tokens (denormalized for fast list rendering)
lastViewedAttimestampMost recent view across any token

​
Lifecycle

created (version=1, totalViews=0)
  ↓
updated×N (version=2, 3, …; HTML replaced; URL unchanged; totalViews preserved)
  ↓
archived (viewers see 404; can still inspect from the dashboard for audit)
TransitionHow
CreatePOST /uploadSharedPresentation (API) or “New presentation” in the dashboard
UpdatePOST /updateSharedPresentation (API) or “Update” in the dashboard
Archive”Archive” in the dashboard — soft-delete, all share links stop resolving
Once archived, a presentation cannot be updated. There is no un-archive in v1.

​
Storage

The HTML lives in a private GCS bucket (slideless-ai-storage) at the path: 
shared_presentations/{shareId}/document.html
You never deal with this path directly — Slideless serves the HTML through the getSharedPresentation endpoint after token validation.

​
Size limits

ResourceLimitWhat happens if exceeded
Single HTML file10 MB413 payload-too-large from upload/update
Presentations per orgNo hard cap in v1—
API keys per org20New key creation fails

​
What gets versioned

When you update, the HTML is replaced in place — the previous version is overwritten. Slideless doesn’t keep history in v1. The version counter increments so you can tell which iteration recipients are looking at, but you can’t roll back to an older version through the API. If you need history, save your HTML in your own version control (git) and re-upload as needed.

​
What stays stable across updates

  • The shareId (and therefore every share URL)
  • All existing share tokens
  • The view counters (totalViews and per-token accessCount)
  • The owner and organization

​
What changes across updates

  • The HTML content
  • version (auto-increments)
  • updatedAt
  • title (only if you pass a new one)