- Does not require FFmpeg, because the "Backend" software only performs download URL extraction and YouTube.com search scraping!
- This data is exposed via API endpoints that can only be consumed via a custom, intermediary script on the same server/IP (to expose API data publicly)
- Direct access to "Backend" APIs is protected by only permitting access to the current IP
- The "video info" endpoint (e.g., https://backend.yoursite.com/api/{Self-generated API key}/{YouTube Video ID}) returns ALL available YouTube "direct" download links for a given video, in a single request, in JSON format, i.e.:
- non-DASH video (composite, generally low-quality video + audio)
- DASH audio (audio-only formats, excluding MP3)
- DASH video (video-only formats)
- Also returns video title, duration, and format/extension for each available download link
- The "search" endpoint (e.g., https://backend.yoursite.com/search/{Self-generated API key}/{Search Term}) returns video search results, in JSON format, like the following:
- FFmpeg is only used in the application that consumes the "Backend" software. E.g., the MP3 Converter Pro, our recommended "consuming application", does require FFmpeg.
- This data is exposed via API endpoints that can only be consumed via a custom, intermediary script on the same server/IP (to expose API data publicly)
- Employs a system of self-generated API keys that enables different websites to use different API keys
- Each API key can further be restricted to a specific IP or IPs
- Bypasses YouTube reCAPTCHAs to effectively circumvent HTTP 429 responses and temporary IP bans (via our proprietary code solution).
- In a multi-server, cluster configuration, the "Backend" software only needs to be installed on one server.
- 4 Users Found This Useful
