Base URL
europe-west1. There is no API versioning in v1 — the URL above is the only stable one.
Authentication
Every endpoint (exceptgetSharedPresentation, which is token-based) requires the X-Process-Manager-Key header:
| Prefix | Type | When to use |
|---|---|---|
cko_ | Organization API key | Almost always |
cka_ | Admin API key | Internal platform tooling only |
Error format
Errors return a JSON body witherror (human-readable) and code (machine-readable):
verifyApiKey endpoint uses a slightly different shape ({ success, error: { message }, requestId }) — see its reference page.
Status codes
| Status | Meaning |
|---|---|
200 | Success |
400 | Bad request — missing or invalid arguments |
401 | Missing or invalid API key |
403 | Authenticated but not allowed (wrong owner, revoked token, missing scope) |
404 | Resource not found, or generically returned to prevent enumeration of share IDs |
405 | Wrong HTTP method |
410 | Gone — share expired or presentation archived |
413 | Payload too large (> 10 MB on upload/update) |
500 | Internal error — retry with backoff |
Endpoint index
| Endpoint | Method | Auth | Purpose |
|---|---|---|---|
/uploadSharedPresentation | POST | API key | Create a new presentation |
/updateSharedPresentation | POST | API key | Replace HTML at an existing share (URL preserved) |
/listMyPresentationsPublic | GET | API key | List your presentations (cap: 100) |
/getSharedPresentationInfoPublic/{shareId} | GET | API key | Full metadata + token list for one presentation |
/getSharedPresentation/{shareId} | GET | Token in URL | Public — returns the raw HTML; increments view counts |
/verifyApiKey | POST | API key | Validate a key, return its metadata |
Limits
| Limit | Value |
|---|---|
| Upload / update HTML size | 10 MB per request |
| List response cap | 100 presentations (no cursor pagination in v1) |
| Per-key rate limit | None enforced in v1 |
| API keys per organization | 20 |
CORS
All HTTP endpoints setcors: true — they accept browser requests from any origin. The auth header (X-Process-Manager-Key) is allowed.
Idempotency
uploadSharedPresentation is not idempotent — every call creates a new presentation with a new shareId. To re-publish to the same URL, use updateSharedPresentation instead.
Next
- Authentication — How the
X-Process-Manager-Keyheader works. - Upload a presentation — The most common endpoint, with examples in curl, Node, and Python.