Dataify YouTube Video By URL

Submit Dataify YouTube Video File by URL Builder tasks. Use when the user wants the YouTube video file collection tool, collect YouTube video files, scrape Y...

Submit YouTube video file collection jobs through Dataify Builder by URL. After a successful submission, give the user the task_id, the returned or inferred status, and tell them to visit Dataify to view results.

API TOKEN Handling

Use DATAIFY_API_TOKEN as the long-term saved token name.

• If the user provides a token in the request, use it for this run.
• If no token is provided, first check whether DATAIFY_API_TOKEN is already saved locally in the environment.
• If DATAIFY_API_TOKEN is saved locally, use it without asking the user to re-enter the token.
• If no token is available locally, tell the user they need to provide a Dataify API TOKEN.
• If the user does not have an API TOKEN, tell them they can register or log in at Dataify to get one.
• If the user already has an API TOKEN, tell them it is available in the top-right area of Dataify.
• After the user provides an API TOKEN and no local DATAIFY_API_TOKEN is saved, ask whether they want to save it locally as DATAIFY_API_TOKEN for future use.
• If the user wants to save it, give the appropriate command for their shell and ask them to run it; do not silently persist tokens without confirmation.
• Do not call the Builder endpoint without a token.
• Always call it API TOKEN in user-facing instructions. Prefer the environment variable name DATAIFY_API_TOKEN for saved local use.

PowerShell examples for saving the token for the current session:

powershell

$env:DATAIFY_API_TOKEN = "YOUR_DATAIFY_API_TOKEN"

For a persistent user-level variable on Windows:

powershell

[Environment]::SetEnvironmentVariable("DATAIFY_API_TOKEN", "YOUR_DATAIFY_API_TOKEN", "User")

Core Workflow

1. Before submitting, show the user the required values, shared values, optional values, and defaults listed in the Parameter Checklist.
2. For dropdown fields, show all allowed options as Markdown tables with both Label and Value columns. Use scripts/submit_dataify_youtube_video_by_url.py --list-options to print the full dropdown tables.
3. Ask whether the user wants to change any value before running the task.
4. Ask whether the user wants to collect multiple YouTube video files. If yes, ask for multiple url values.
5. Normalize the final url values into a list of spider_parameters objects.
6. Normalize resolution, video_codec, audio_format, bitrate, subtitles_language, and selected_only into one shared spider_universal object.
7. Resolve the Dataify token from explicit input or saved DATAIFY_API_TOKEN.
8. If no token is available, ask the user to enter their API TOKEN and ask whether to save it as DATAIFY_API_TOKEN.
9. Validate each URL, dropdown value, resolution direction, bitrate direction, and file name.
10. Submit a Builder request to create the task.
11. Read data.task_id from the Builder response and read data.status or status when present.
12. Stop after Builder succeeds.
13. Tell the user to visit Dataify to view or manage results.

Parameter Checklist

When the user invokes this skill, first tell them these values are used. Always display submitted parameters as a Markdown table; do not use a plain sentence or bullet list for the parameter confirmation.

Field	Required	Default	Location	Notes
url	Yes	https://www.youtube.com/watch?v=_SdpvpvVrLY	spider_parameters	YouTube video URL to collect.
resolution	No	360p with <=	spider_universal	Dropdown-style shared parameter. Ask whether it should be greater than or equal to, or less than or equal to, the selected value. Submit as <=360p by default.
video_codec	No	vp9	spider_universal	Dropdown-style shared parameter. Video codec.
audio_format	No	opus	spider_universal	Dropdown-style shared parameter. Audio format: opus or m4a.
bitrate	No	320 with <=	spider_universal	Dropdown-style shared parameter. Ask whether it should be greater than or equal to, or less than or equal to, the selected value. Submit as <=320 by default.
subtitles_language	No	ab	spider_universal	Dropdown-style shared parameter. Subtitle language.
selected_only	No	false	spider_universal	Dropdown-style shared parameter. Whether to use only selected specifications.
file_name	No	{{TasksID}}	Builder form field	Use the default when the user does not change it.

Then ask: "Do you want to change any of these values before I submit the task?"

Also ask: "Do you want to collect multiple YouTube video files? If yes, provide multiple url values."

For resolution and bitrate, ask whether the selected option should use <= or >=. Default to <= when the user does not specify a direction.

If the user has already provided some values, show those values in place of the defaults and only ask whether the remaining/defaulted values should be changed.

Dropdown Options

Before asking the user to choose dropdown values, show all allowed options as Markdown tables with both Label and Value columns.

Use this command to print the complete tables:

powershell

python3 ".\scripts\submit_dataify_youtube_video_by_url.py" --list-options

If python3 is not available, use the local Python 3 command for that machine, such as python.

The script prints:

• resolution options.
• resolution_direction options.
• video_codec options.
• audio_format options.
• bitrate options.
• bitrate_direction options.
• subtitles_language options, using the supplied cn value as Label and typeValue as Value.
• selected_only options.

Parameter Handling

• url is required. If the user does not provide it, use the default https://www.youtube.com/watch?v=_SdpvpvVrLY only after showing it in the parameter confirmation table.
• Trim leading and trailing whitespace from url.
• url cannot be empty.
• url must start with https://www.youtube.com/.
• Multiple collection groups only repeat url inside spider_parameters.
• resolution, video_codec, audio_format, bitrate, subtitles_language, and selected_only are shared parameters. Send them in spider_universal, not inside each spider_parameters object.
• resolution defaults to 360p and resolution_direction defaults to <=; submit resolution as <=360p.
• bitrate defaults to 320 and bitrate_direction defaults to <=; submit bitrate as <=320.
• video_codec defaults to vp9.
• audio_format defaults to opus. Allowed values are opus and m4a.
• subtitles_language defaults to ab.
• selected_only defaults to false.
• file_name defaults to {{TasksID}}. If the user changes it, submit the user-provided value.
• file_name cannot be empty.

Single-group example:

json

spider_parameters=[{"url":"https://www.youtube.com/watch?v=_SdpvpvVrLY"}]
spider_universal={"resolution":"<=360p","video_codec":"vp9","audio_format":"opus","bitrate":"<=320","subtitles_language":"ab","selected_only":"false"}

Multi-group example:

json

spider_parameters=[{"url":"https://www.youtube.com/watch?v=_SdpvpvVrLY"},{"url":"https://www.youtube.com/watch?v=_SdpvpvVrLY"}]
spider_universal={"resolution":"<=360p","video_codec":"vp9","audio_format":"opus","bitrate":"<=320","subtitles_language":"ab","selected_only":"false"}

Dataify Builder Request

Use form fields rather than hand-built URL-encoded strings.

• URL: https://scraperapi.dataify.com/builder?platform=1
• Method: POST
• Authorization header: Bearer DATAIFY_API_TOKEN
• Content type: application/x-www-form-urlencoded
• Fixed fields:
  • spider_name=youtube.com
  • spider_id=youtube_video_by-url
  • spider_errors=true
• Default field:
  • file_name={{TasksID}}
• Dynamic fields:
  • spider_parameters must be a JSON string array of URL objects.
  • spider_universal must be a JSON string object containing shared video settings.

Script

For stable execution, prefer scripts/submit_dataify_youtube_video_by_url.py with Python 3.6 or newer instead of rewriting the Builder flow.

powershell

python3 ".\scripts\submit_dataify_youtube_video_by_url.py" --url "https://www.youtube.com/watch?v=_SdpvpvVrLY"

To override the saved environment token or default shared parameters for one run:

powershell

python3 ".\scripts\submit_dataify_youtube_video_by_url.py" --api-token "YOUR_DATAIFY_API_TOKEN" --url "https://www.youtube.com/watch?v=_SdpvpvVrLY" --resolution "360p" --resolution-direction "<=" --video-codec "vp9" --audio-format "opus" --bitrate "320" --bitrate-direction "<=" --subtitles-language "ab" --selected-only "false" --file-name "{{TasksID}}"

To submit multiple URLs:

powershell

python3 ".\scripts\submit_dataify_youtube_video_by_url.py" --params-json '[{"url":"https://www.youtube.com/watch?v=_SdpvpvVrLY"},{"url":"https://www.youtube.com/watch?v=_SdpvpvVrLY"}]'

The script prints a JSON summary with task_id, status, parameters, spider_universal, file_name, dashboard_url, and message.

Troubleshooting

Missing Dataify API TOKEN means no explicit token was passed and DATAIFY_API_TOKEN is not saved locally. Tell the user they need to provide their Dataify API TOKEN, ask whether they want to save it as DATAIFY_API_TOKEN, or tell them they can register or log in at Dataify to get one. If they already have a token, tell them it is in the top-right area of Dataify.

url cannot be empty means the required YouTube video URL is missing.

url must start with https://www.youtube.com/ means the URL is outside the allowed YouTube domain.

Unsupported resolution, Unsupported video_codec, Unsupported audio_format, Unsupported bitrate, Unsupported subtitles_language, or Unsupported selected_only means the value must be one of the allowed dropdown values.

Unsupported resolution_direction or Unsupported bitrate_direction means the value must be <= or >=.

File name cannot be empty means no usable file_name was provided.

Necessary parameters is empty! usually means the Builder request was not submitted as form fields, spider_parameters was not a JSON string array, spider_universal was not a JSON string object, or one spider_parameters object is missing url.

Missing task_id usually means the authorization header, token, spider_name, spider_id, spider_parameters, or spider_universal is wrong.

Guardrails

• Do not put resolution, video_codec, audio_format, bitrate, subtitles_language, or selected_only inside spider_parameters.
• Do not omit spider_universal.
• Do not poll for results after Builder succeeds.
• Use only API TOKEN and DATAIFY_API_TOKEN when referring to authentication.
• Do not hard-code local Python paths.
• Do not claim the Builder response contains YouTube video files.
• Do not invent result fields.
• Always direct the user to Dataify after successful task creation.