Skip to main content
POST
/
streams
/
validate
Validate Stream
curl --request POST \
  --url https://trio.machinefi.com/api/streams/validate \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "stream_url": "<string>"
}
'
{
  "is_live": true,
  "platform": "<string>",
  "stream_id": "<string>",
  "title": "<string>",
  "channel": "<string>",
  "thumbnail_url": "<string>",
  "viewer_count": 123,
  "parsed_url": "<string>",
  "error_hint": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.machinefi.com/llms.txt

Use this file to discover all available pages before exploring further.

Checks whether a stream URL is valid and currently live, and returns stream metadata plus a parsed playback URL when available. Use this before starting expensive monitoring jobs when you want early feedback on bad URLs.

​
Typical flow

  1. Validate with POST /streams/validate.
  2. Use parsed_url from the response for frontend playback/preview if needed.
  3. Start Check Once, Live Monitor, or Live Digest.

​
Notes

  • Main monitoring endpoints can still validate internally.
  • Explicit validation is useful for better UX and pre-flight checks.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Request for stream validation.

​
stream_url
string
required

Stream URL to validate

Required string length: 1 - 500

Response

Successful Response

Rich response for stream validation.

​
is_live
boolean
required
​
platform
string | null
​
stream_id
string | null
​
title
string | null
​
channel
string | null
​
thumbnail_url
string | null
​
viewer_count
integer | null
​
parsed_url
string | null
​
error_hint
string | null