POST /api/dailymotion/videos
Price: 1 credit
Get a Dailymotion video by ID or URL
Get a single Dailymotion video by its ID (e.g. 'xalhyqe') or full video URL. Returns title, description, duration, view_count, created_at, aspect_ratio, resolution, language, tags, hashtags, thumbnail image, geo-availability and the creator channel.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)video string required — Dailymotion video ID or URL (examples: "xalhyqe", "https://www.dailymotion.com/video/xalhyqe"; minLength: 1)@type string (default: "DailymotionVideo")id string requiredvideo_title string nullabledescription string nullableurl string requiredduration_seconds integer nullableview_count integer nullablecreated_at integer nullableupdated_at integer nullableaspect_ratio number nullablewidth integer nullableheight integer nullablelanguage string nullableaudience string nullablevisibility string nullablestatus string nullableis_360 boolean nullableis_exclusive boolean nullableis_ai_altered boolean nullableis_paid_partnership boolean nullableis_published boolean nullableimage string nullabletags array (default: [])hashtags array (default: [])geoblocked_allowed array (default: [])geoblocked_denied array (default: [])creator object nullable@type string (default: "DailymotionChannelBrief")id string requiredalias string nullablename string nullableurl string nullableimage string nullablefollower_count integer nullableis_artist boolean nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Video not found or unavailable. Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.