The request was not valid
The API received a body it could not accept.
What it means
A required field was missing, or a value fell outside the accepted range, so validation rejected the body before any fetch or analysis was attempted.
Why it matters
The request was rejected before any work was done, so nothing was fetched and nothing was analysed. This is a client-side mistake rather than a fault in the stream being tested.
How to fix it
- Check the request body against the /api/v1 shape: a kind, and either a url or content.
- If you are using the site rather than the API, this usually means a field was left blank.
Check your own stream
The free stream tester runs this check on every analysis and links each finding straight back here.
Open the stream tester →Frequently asked questions
- What does "The request was not valid" mean?
- A required field was missing, or a value fell outside the accepted range, so validation rejected the body before any fetch or analysis was attempted.
- Why does it matter?
- The request was rejected before any work was done, so nothing was fetched and nothing was analysed. This is a client-side mistake rather than a fault in the stream being tested.
- How do I fix it?
- 1. Check the request body against the /api/v1 shape: a kind, and either a url or content. 2. If you are using the site rather than the API, this usually means a field was left blank.
- How can I detect this automatically?
- Paste your stream delivery URL into StreamTest's free stream tester. It runs this check on every analysis, flags the finding, and links straight back to this page — no sign-up required.
Related Fetching and delivery checks
- The browser blocked the request (CORS)Your browser refused to read the response because the origin did not send an Access-Control-Allow-Origin header.
- The origin returned an error statusThe server answered with a 4xx or 5xx status instead of the manifest, so there was nothing to analyze.
- That address cannot be reached from our serversThe URL resolves to a private or reserved address, so we will not connect to it from the server. Local mode tests it from your own browser instead.
- That is not a valid URLThe address could not be parsed, so no request was attempted.
- That URL scheme is not supportedOnly http and https can be fetched; schemes such as rtmp, rtsp and file cannot.
- The URL redirected too many timesWe follow up to three redirects; this URL exceeded that.