Search FAQs

Yes. Filmot offers a public, self-service API for searching its index and retrieving video and channel metadata, with subtitles where available.

To get access, sign in, open API Keys, accept the Terms of Service and create a key. Each account can have up to five active keys. Every account receives a monthly API credit allowance, and Patreon supporters receive larger allowances according to their tier.

The API documentation describes the endpoints, parameters, response fields and usage limits. Use the API for automated queries rather than loading the website's search pages with scripts.

API access does not include a full database download or bulk data feed. There is also no API endpoint for requesting that a video or channel be re-indexed. Supporters who want better channel coverage can add the channel to Prioritized Channels through the website.

API requests consume credits according to the endpoint and its documented cost. Your allowance applies to a monthly billing period, and unused credits do not roll over. Patreon supporters receive larger allowances according to tier.

• API Keys shows credits used, credits remaining and the reset time.
• Successful responses include headers with the request cost, usage, remaining credits and allowance reset time.
• A request that would exceed the remaining allowance is rejected with 429 Too Many Requests until the next billing period.

See the API documentation for current endpoint costs and limits. A Markdown version for scripts and AI agents is available at /api-documentation-md.

Yes. Filmot's API documentation is based on an OpenAPI specification available at /openapi.json. You can load the JSON into compatible API tools or client generators. A Markdown version for scripts and AI agents is available at /api-documentation-md.

Companion reference pages cover:

• /api-documentation/search-syntax: subtitle and title expressions. Query strings must be URL-encoded.
• /api-documentation/reference-values: accepted country IDs and subtitle language codes.

API calls require a key. Sign in and create one on API Keys.

Use the values listed on Filmot's API Reference Values page. The API's country IDs and subtitle language codes should be taken from those tables rather than inferred from a country's name or a standard code list.

Countries use numeric IDs. For example, the reference lists the United States as 217, the United Kingdom as 153 and Brazil as 14; do not substitute US, GB or BR in a parameter that expects a country ID.

Subtitle languages use the codes in the language table, such as en for English, de for German and pt for Portuguese. Some values can be unexpected: Hebrew is listed as iw, while Chinese and Cantonese appear separately as zh and yue.

Check the API documentation or the OpenAPI specification for the parameter name, data type and representation the endpoint you are calling expects. The reference tables identify the accepted values; they do not replace the endpoint's request format or guarantee that every language has matching indexed videos.

If a filtered request returns no matches, verify the code or ID and try removing that filter before concluding that the underlying videos are missing.

Yes. The getvideos endpoint returns stored video metadata for one YouTube video ID or a comma-delimited list of IDs. Each record includes the video ID, upload date, duration, title, channel ID and channel name. Use the columns parameter to request additional fields, such as the stored description, view count, like count, category and subtitle, caption or transcript tracks. IDs that Filmot does not know are omitted from the response.

A request can contain up to 200 video IDs, or up to 10 when raw subtitles are requested. The related getchannelvideos endpoint returns recent videos for up to 10 channels identified by their UC channel IDs, with the same selectable fields.

Sign in and create an API key on API Keys after accepting the Terms of Service. See the API documentation for the complete parameters, limits and response format.

Yes. The getchannelvideos API endpoint returns recent videos for up to 10 channels per request, identified by their UC channel IDs. Each video record includes its ID, title, upload date, duration, channel ID and channel name. You can request additional fields, such as the stored description, view count and like count.

The response contains video IDs rather than ready-made YouTube URLs. To build a link, append the ID to https://www.youtube.com/watch?v=.

A request returns at most 200 videos across the requested channels, reduced to 10 when raw subtitles are included. Use the page parameter to request further pages for each channel.

Create an API key on API Keys and consult the API documentation for the complete parameters and response format.

Filmot's full metadata and subtitle dataset is not available as a bulk download.

You can retrieve specific search results in two ways:

• Website exports: run a subtitle or metadata search and export the matching videos. Without patron benefits, the limits are 60 rows from subtitle search or 100 rows from metadata search. With patron benefits, an export can contain up to 10,000 rows, or 2,500 when full subtitles are included.
• Public API: use the documented endpoints to search and retrieve video details and available captions programmatically, within your API allowance. Sign in and create a key on API Keys.

Exports and API requests are intended for retrieving search results and selected records, rather than copying the entire database. See the API documentation for programmatic access.

No installation is required to use filmot.com in a desktop or mobile browser. You can search subtitles and metadata, apply filters and open matching timestamps directly on the website.

Some optional tools require additional software. Title Restorer, for example, is a userscript that needs a browser userscript manager such as Tampermonkey. Review the extension's permissions before installing it. The tool is not required for ordinary Filmot searches.

Independently developed clients or integrations have their own setup and documentation. To build an integration, see the public API documentation and create a key on API Keys.