Bolrach Stream

Upload, encode and deliver video. Broadcast live. Run interactive rooms. Base URL https://api.bolrach.com — every endpoint lives under /v1/stream.

Authentication

Send your API key as a bearer token on every request. Keys are per application, so revoking one does not affect the rest of your estate.

curl https://api.bolrach.com/v1/stream/live/channels \
  -H "Authorization: Bearer <your api key>"

Uploading

Your file never passes through this API. You ask for an upload session, get signed URLs, and send the bytes straight to storage. That is why upload size is bounded by your plan rather than by any request timeout, and why a dropped connection resumes instead of restarting.

// 1. start a session — bytes decides the part size
const s = await post('/v1/stream/uploads', {
  bytes: file.size, filename: file.name, title: 'Lecture 1',
  idempotencyKey: 'lecture-1-v1',        // a retry returns THIS session, not a second one
});

// 2. send each part directly to storage
for (let n = 1; n <= s.partsExpected; n++) {
  const { parts } = await post(`/v1/stream/uploads/${s.uploadId}/parts/sign`, { partNumbers: [n] });
  const start = (n - 1) * s.partSizeBytes;
  await fetch(parts[0].url, { method: 'PUT', body: file.slice(start, start + s.partSizeBytes) });
}

// 3. finish — this starts probing and encoding
await post(`/v1/stream/uploads/${s.uploadId}/complete`, {});

Playback

Mint a short-lived token per viewer, then hand them the HLS or embed URL.

const p = await post(`/v1/stream/assets/${assetId}/playback-sessions`, {
  host: 'media.bolrach.video',
  expiresInSeconds: 3600,
  viewerId: 'user_1042',
});
// p.embedUrl  -> drop in an iframe
// p.hlsUrl    -> feed your own player

Live

const ch = await post('/v1/stream/live/channels', { name: 'Main Stage', record: true });
// ch.ingest.rtmp.url + ch.ingest.rtmp.streamKey  -> point your encoder here
// ch.ingest.backup.streamKey                     -> failover
// ch.playback.hls                                -> viewers

Stream keys are shown once; only hashes are stored, so a lost key is rotated rather than recovered. A channel already carrying a primary publisher refuses a second one — use the backup key to take over, which makes failover deliberate instead of accidental. Set record: true and each broadcast becomes an ordinary on-demand asset when it ends, through the same processing every upload goes through.

Live is currently passthrough: viewers receive your source quality with no adaptive ladder.

Interactive rooms

Multi-party real-time sessions. Create a room, then issue one token per participant. role is enforced rather than advisory — a viewer token cannot publish media. A room can also be broadcast to one of your live channels, where it gets the same recording, metering and playback as any other broadcast.

Errors and limits

Errors are JSON with a stable error code and a human message. 401 means the key is missing or wrong, 403 means the key is valid but not permitted, 429 means slow down. Plan limits (storage, concurrent encodes, live channels, rooms, custom domains) return 400 with a code naming the limit and the current usage, so you can show the user something true.

API reference

Machine-readable: OpenAPI 3.1 · endpoint-by-endpoint: API reference · console: stream.bolrach.com/console.

Health

Uploads

Analytics

Assets

Playback

Live

Rooms

Custom domains