Authentication

Requests to /download and /stream are authenticated with an API key passed as a normal parameter. There are no headers or OAuth flows involved.

Getting a key

Keys are issued by the @free_accoa_bot Telegram bot. Start a chat with the bot and it will generate a key for your account.

Sending your key

Where the key goes depends on the request method:

GET requests

Pass it as the api_key query parameter, alongside the other parameters.

https://yt-dow.co08.art/download?url=VIDEO_URL&type=audio&api_key=YOUR_API_KEY

POST requests

Include it as a field in the JSON request body.

{
  "url": "VIDEO_URL",
  "type": "audio",
  "api_key": "YOUR_API_KEY"
}

Key lifecycle

• New keys come with a daily request quota. Once you use it up for the day, requests return 429 Daily quota exhausted until the quota resets.
• Keys expire some weeks after they're created. An expired key returns 403 API key has expired — message the bot to get a new one.
• If you need a higher daily limit, reach out through the bot.

Invalid or missing keys

Keep your key out of client-side code you ship to end users — anyone who has it can spend your daily quota. Call the API from your own backend or bot instead.