Where do examples run?

Use p.savenow.to for public API examples unless your dashboard shows a custom account hostname.

Open the dashboard, create a top-up payment, or redeem a coupon. Balance changes are shown in the account history.

Are old endpoints still supported?

Yes. The .php compatibility endpoints remain active for existing integrations and embedded clients.

Video info API for title and thumbnail metadata

Read title and thumbnail metadata from Download v2 responses while keeping the same API key, pricing, and direct download workflow.

First request

Replace YOUR_API_KEY, run the command, then poll progress with the returned id.

curl --location "https://p.savenow.to/ajax/download.php?format=mp3&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DK1Pu75yJUOE&apikey=YOUR_API_KEY&add_info=1"

Create the metadata request

Send the normal authenticated download request with a URL-encoded video URL, a format, your dashboard apikey, and add_info=1. This is not a separate metadata-only or free endpoint: it creates the usual download job and follows the existing API-key billing rules.

Read title and thumbnail

The accepted response includes success=true and an id. The info object is present only when add_info=1; map info.title to the content title and info.image to its thumbnail URL.

Poll the accepted job

Pass the returned id to https://p.savenow.to/ajax/progress.php?id=DOWNLOAD_ID. Progress polling uses the job id rather than the API key; progress below 1000 is pending. At 1000, use download_url only when success is 1 or true and the URL is non-empty.

Authentication and billing

Use the dashboard API key in the apikey query parameter when creating the request, and keep it server-side. Metadata retrieval remains subject to the selected format, wallet balance, and applicable duration pricing rules.

Handle errors

Correct missing or invalid parameters, including a missing or rejected key, before retrying. Treat HTTP 400 as a documented invalid-request response and HTTP 500 as a server error. Progress below 1000 is pending regardless of success. At 1000, stop and surface text or message, or a generic failure message if neither is present, unless success is 1 or true and download_url is non-empty.