An http api wrapper for yt-dlp/ejs.
You can use the public instance without a password at https://cipher.kikkia.dev/api/.
I do my best to keep it up and running and decently fast, but I don't garuntee 100% uptime. Feel free to host it yourself or use the public API.
WARNING: Ratelimit of 10 requests/sec (should be fine up to 1000+ active players). If you have more than 1k players you probably want to host it yourself.
The easiest way to host this service is with Docker
git clone https://github.com/kikkia/yt-cipher.git
cd yt-cipher
docker-compose build
docker-compose upIf you have Deno installed, you can run the service directly.
Clone the repository and patch the ejs dependency:
git clone https://github.com/kikkia/yt-cipher.git
cd yt-cipher
git clone https://github.com/yt-dlp/ejs.git
cd ejs
git checkout 689764f8cea694e99609a41f1630d2e7e8e8668a
cd ..
deno run --allow-read --allow-write ./scripts/patch-ejs.tsdeno run --allow-net --allow-read --allow-write --allow-env server.tsYou can optionally set the API_TOKEN environment variable in your docker-compose.yml file to require a password to access the service.
Requests without a valid Authorization: <your_token> header will be rejected if you have a token set.
Environment Variables:
MAX_THREADS- max # of workers that can handle requests. Default is 1 per thread on the machine or 1 if it can't determine that for some reason.API_TOKEN- A required password to access this servicePORT- Port to run the api on, default:8001HOST- Sets the hostname for the deno server, default:0.0.0.0PREPROCESSED_CACHE_SIZE- Max size of processed player script cache. Lower to consume less memory. default:150
To run the server with IPv6, you need to configure the HOST environment variable.
- Set
HOSTto[::]to bind to all available IPv6 and IPv4 addresses on most modern operating systems.
When accessing the service over IPv6, make sure to use the correct address format. For example, to access the service running on localhost, you would use http://[::1]:8001/.
If you are using this with the youtube-source plugin, please reference the setup steps.
If you ever have issues with read timeout errors, you can try upping the http timeouts in your lavalink config
lavalink:
server:
timeouts:
connectTimeoutMs: 10000
connectionRequestTimeoutMs: 10000
socketTimeoutMs: 10000Request Body:
{
"encrypted_signature": "...",
"n_param": "...",
"player_url": "..."
}encrypted_signature(string): The encrypted signature from the video stream.n_param(string): Thenparameter value.player_url(string): The URL to the JavaScript player file that contains the decryption logic.
Successful Response:
{
"decrypted_signature": "...",
"decrypted_n_sig": "..."
}Example curl request:
curl -X POST http://localhost:8001/decrypt_signature \
-H "Content-Type: application/json" \
-H "Authorization: your_secret_token" \
-d '{
"encrypted_signature": "...",
"n_param": "...",
"player_url": "https://..."
}'Extracts the signature timestamp (sts) from a player script.
Request Body:
{
"player_url": "..."
}player_url(string): The URL to the JavaScript player file.
Successful Response:
{
"sts": "some_timestamp"
}Example curl request:
curl -X POST http://localhost:8001/get_sts \
-H "Content-Type: application/json" \
-H "Authorization: your_secret_token" \
-d '{
"player_url": "https://..."
}'