The parts of a web content item that are reachable from code: JavaScript injection, request headers and authentication, and the fields the dashboard does not expose.
A web content item is a URL plus a set of fields that shape how the player fetches and renders it. Most of those fields have a control in the dashboard. Some do not, and JavaScript injection is the main one: it exists only through the API, the CLI, and the MCP server.
The end-user side of web pages, what the settings mean and when to reach for each, is in Content. This section is the same feature set seen from a script.
Attach a script to a web content item and the player runs it after the page loads: dismissing banners, hiding chrome, or completing a login form.
Getting a player past a login from code: request headers for basic and bearer auth, client certificates, and where each one leaves the credential.
The fields on a web content item you can set over the API, what each one accepts, and which ones only exist in v4.1.