Compare visible Tvheadend stream profiles with the configured inventory

The useful distinctions

• profile/list returns available profile names and identifiers.
• The all parameter lets an administrator inspect disabled or otherwise inaccessible profiles.
• htsp=1 restricts the list to HTSP profiles.
• The corresponding UI is Configuration, Stream, Stream Profiles.

Compare the same visibility scope

An administrator’s configuration screen and another user’s available choices need not describe the same set of profiles. Begin with the ordinary list in the relevant authorized context. Keep the requesting role and profile type in your note so a difference can be interpreted correctly. A missing entry should not immediately lead to recreating the profile or copying a configuration from another installation.

Use discovery before configuration

The original request examples are read-only. They show how to compare the ordinary list with the broader administrator inventory without including credentials or invented persistent identifiers. Use the actual server response to identify a profile and preserve its existing settings while investigating. The API documentation is version-sensitive, so check your installed build if an endpoint or parameter behaves differently from the rolling reference.

State the result precisely

The useful outcome is a statement about visibility: present for this account, visible only in the administrator inventory, or excluded by a type filter. That is different from proving that the profile’s media output will play on a client. Once visibility is understood, evaluate any output-format issue as a separate request with its own evidence. This keeps access scope and media processing from being confused in a single report.

A focused way to proceed

1. Use an existing authorized API session to request the ordinary profile list.
2. Compare the result with the Stream Profiles view.
3. If authorized as administrator, inspect the all list separately.
4. Record whether the missing profile is disabled, restricted or outside the requested profile type.

Worked example · synthetic

Read-only requests through an already authorized API client:
GET https://example.test/api/profile/list
Administrator comparison only: GET https://example.test/api/profile/list?all=1
HTSP-only inventory: GET https://example.test/api/profile/list?htsp=1

Read the comparison

An administrator-only inventory entry is not proof that another account can select or use that profile.

When to stop or ask for help

If the lists contradict saved configuration, report the build, authorization role and minimal read-only request.