Bring RiotPix into
your next discovery.

Read only

Find a film to rent

The existing lookup matches a film name and optional year. It returns a rental page link and availability. It does not return a price or reserve stock.

curl --get 'https://riotpix.com/api/v1/lookup/title' \
  --data-urlencode 'name=Example Film' \
  --data-urlencode 'year=1999'

Illustrative response only; this is not a live title or price:

{
  "query": {"name": "Example Film", "year": 1999},
  "matches": [{"title": "Example Film", "year": 1999,
    "available": true,
    "rentalUrl": "https://riotpix.com/titles/example-film-1999-dvd"}]
}

GET /api/v1/rental-prices?name=Example%20Film&year=1999 is a separate, disabled price preview. Prices must identify the physical format and currency and represent the base rental charge. Shipping is order-level; customer credits and the final checkout total are separate. Physical rental availability is not streaming availability. Always link customers back to the returned RiotPix rental page.

Read only • disabled preview

Discover creators

GET /api/v1/creators?page=0&size=20 and GET /api/v1/creators/{handle} return an explicit selection of public profile details and listed offerings, with links to RiotPix profiles. Approved status alone does not establish permission for syndication: the initial eligible-handle allowlist is empty.

No emails, payout identifiers, private contacts, account records, moderation notes, drafts, or private membership content belong in the public response. Unreviewed photos are excluded. Directory discovery does not grant access to paid content or initiate a purchase.

Authenticated - disabled preview

Publish a free creator video

The local publishing workflow supports public, free videos from approved creators. Sign in with your creator account, create a draft and confirm your rights, upload the declared file, then wait for processing. Upload completion keeps the video private.

1. POST /api/v1/creator/videos creates an owned draft. Supply an Idempotency-Key, title, optional description, and rightsConfirmed: true.
2. Request /{id}/upload-ticket with filename and exact sizeBytes. PUT that exact file to the returned staging URL, then POST its key to /{id}/upload-complete. The server creates a separate sealed copy for screening.
3. Poll GET /api/v1/creator/videos/{id}. Only a READY video can be submitted with POST /{id}/publish and {"mode":"PUBLIC_FREE"}. HTTP 202 means it is waiting for administrator review.
4. After approval, the response contains a RiotPix public watch-page link. Unpublish through /{id}/unpublish. Administrators can reject submissions or take published videos down.

Paid, member-only, private and unlisted publication modes are unsupported and rejected. Personalized order videos use a separate workflow. Screening failures or unavailable moderation remain held; they do not become public automatically. Public pages and playback recheck publication status and the creator's approved, active account on every request.

Authentication uses your existing session and CSRF token on every POST. No API keys or OAuth grants are provided. Never share session cookies, CSRF tokens or upload URLs. Draft and stored-object quotas include cleanup reservations; unavailable cleanup may temporarily prevent new drafts.

The local implementation includes a protected administrator review queue at /admin/creator-videos. Production activation still requires schema, private-storage, upload-signature, media-processing, timeout, retention and public-access review. See the OpenAPI contract for request bodies, error codes, limits and examples.

Read only • disabled preview

Explore the RiotPix TV guide

GET /api/v1/public/tv reads the webapp's cached public schedule. It returns the channel name, public watch-page URL, guide freshness, and a bounded page of programme titles, block names, and known start/end times. It never returns raw streams, signed tokens, encoder paths, private origins or subscriber data.

curl 'https://riotpix.com/api/v1/public/tv?offset=0&limit=20'

This preview returns guide_available only for a valid schedule generated within five minutes. Missing, future or stale timestamps produce unknown with an empty guide. Guide availability is not proof that a stream is live or playable. The response uses Cache-Control: no-store.

Bounds: offset 0–1,000; limit 1–50 (default 20). A conservative per-instance global cap of 60 requests per minute returns HTTP 429 with Retry-After: 60. This initial shared cap needs deployment review before directory promotion. Invalid bounds return HTTP 400; disabled routes are unavailable.

Read only • disabled preview

Find upcoming live events

RiotPix already has creator scheduling, event pages, tickets, tips, membership access, and cancellation. The new directory adds discovery without changing those workflows.

curl 'https://riotpix.com/api/v1/public/events?page=0&size=20'

Only explicitly approved event IDs from approved enabled creators are eligible. This first release excludes ticketed, member-only, canceled, and ended events. It returns public title/description, UTC start and end instants, display time zone, creator handle/name, event-page link, and upcoming or ongoing schedule status. It exposes no stream URLs, attendee lists, ingest credentials, or private account data. Schedule status is not a claim that a broadcast is playing.

Optional from and until accept ISO-8601 timestamps with offsets. The default window is 30 days, the maximum window is 31 days, and the horizon is 366 days. Already-ended events remain excluded. Page 0–1,000; size 1–50 (default 20). HTTP 400 indicates invalid filters; HTTP 429 includes Retry-After. Responses use no-store. Rights and public eligibility must be reviewed before populating the initially empty event allowlist.

Contracts and integration examples

OpenAPI contract and HTTP examples and a sanitized Postman collection describe the implemented previews and limitations. Treat only tested, explicitly enabled operations as available. Review endpoint-specific limits, errors and authentication before use.

HTTP-compatible tools can call an enabled endpoint using its documented contract. That does not imply a verified native Zapier, Make, n8n or Postman integration. No third-party accounts or paid services are required by this preview.