Video Download API documentation

EasyDown REST API platform guide

Kuaishou / Kwai Download API

Share links are resolved to a photo ID when possible, then normalized video, cover, dimension, and duration fields are returned without provider-specific response objects.

Parse public Kuaishou and Kwai single-video pages, share links, and supported Gifshow posts with the EasyDown REST API.

Kuaishou video download API · Kwai download API

Production REST endpoint

POST https://api.easydown.org/api/v1/parse

Supported public URL formats

kuaishou.com/short-video/{photoId}kwai.com/@user/video/{photoId}kuaishou.com/f/{token}v.kuaishou.com/{token}gifshow.com/fw/photo/{photoId}chenzhongtech.com/fw/photo/{photoId}gifshow.com or chenzhongtech.com /photo/{photoId}Kuaishou/Kwai URL with photoId or photo_idShare text containing a Kuaishou/Kwai URL

Real request example

https://www.kuaishou.com/short-video/3x2cvn2u7fq8k8s

curl -X POST https://api.easydown.org/api/v1/parse \
  -H "Authorization: Bearer ed_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.kuaishou.com/short-video/3x2cvn2u7fq8k8s"}'

Platform response example

The shared envelope stays stable while this platform determines which media arrays and attributes are populated.

Media behavior

Every available public video URL and content cover is returned, with dimensions and duration when the source exposes them.

{
  "status": 200,
  "data": {
    "platform": "kuaishou",
    "title": "Example kuaishou public post",
    "thumbnail": "https://cdn.example.com/thumbnail.jpg",
    "duration": 24,
    "images": [],
    "videos": [
      {
        "url": "https://cdn.example.com/video.mp4",
        "quality": "HD",
        "mimeType": "video/mp4",
        "width": 1080,
        "height": 1920,
        "hasAudio": true,
        "source": "direct"
      }
    ],
    "audios": []
  },
  "msg": "success"
}

Download and proxy rules

Use Referer: https://www.kuaishou.com/, a browser User-Agent, and forwarded Range headers. Proxy large video files as streams rather than loading them fully into server memory.

Recommended backend request headers

User-Agent: Mozilla/5.0 Referer: https://www.kuaishou.com/ Range: bytes=0-

Unsupported or unavailable content

Profiles, live rooms, search pages, collections, private works, deleted works, expired share tokens, and region-unavailable videos are unsupported.

Only process public media you have the right to use. EasyDown does not bypass privacy controls, DRM, deleted content, or platform access restrictions.

Platform-specific troubleshooting

Submit the share text or full URL when a short token is used.

Stream large videos and forward Range for resume support.

Re-parse when a resolved photo URL expires.

REST integration workflow

  1. 1

    Create a private API token and allow this platform in its permissions.

  2. 2

    POST one complete public post URL to the shared endpoint.

  3. 3

    Select and proxy the required items from images, videos, and audios.

Download API questions

Which Kuaishou / Kwai URLs does the download API support?

Supported public single-post formats include kuaishou.com/short-video/{photoId}, kwai.com/@user/video/{photoId}, kuaishou.com/f/{token}, v.kuaishou.com/{token}, gifshow.com/fw/photo/{photoId}, chenzhongtech.com/fw/photo/{photoId}, gifshow.com or chenzhongtech.com /photo/{photoId}, Kuaishou/Kwai URL with photoId or photo_id, Share text containing a Kuaishou/Kwai URL. Profiles, live rooms, search pages, collections, private works, deleted works, expired share tokens, and region-unavailable videos are unsupported.

What media does the Kuaishou / Kwai Download API return?

Every available public video URL and content cover is returned, with dimensions and duration when the source exposes them.

How should my application download returned Kuaishou / Kwai media URLs?

Use Referer: https://www.kuaishou.com/, a browser User-Agent, and forwarded Range headers. Proxy large video files as streams rather than loading them fully into server memory.

How is a successful Kuaishou / Kwai API request billed?

A response containing at least one image, video, or audio URL costs 1 credit. Failed, unsupported, authentication, and empty-media results do not consume credits.