1. API
2. Regenerate pictures

GET

cURL example

curl --include \
'https://send.now/api/file/regen_screenlist?key=1ltghrilhllgrx2b2&file_code=jfru5kl9dhrt'
          

Response

{
  "msg": "OK",
  "result": {
    "kind": "screenlist",
    "queued": 1,
    "files": [
      {
        "file_code": "jfru5kl9dhrt",
        "status": "queued"
      },
      {
        "file_code": "zz3k8m1q5w2e",
        "status": "skipped",
        "reason": "it is not a video"
      }
    ]
  },
  "status": 200,
  "server_time": "2024-08-26 12:19:28"
}
          

Notice

	The pictures are not made during the call. The call only puts them in the queue and answers queued; the file server of the video makes the picture a little later (usually within a few minutes, when the site's background job runs). Ask File info for the addresses: a picture that was made again has a new address (?v= at the end) and the old one can stay in caches for a while.
	file/regen_slider makes the time slider again (the small frames the player shows under the mouse while you seek), file/regen_screenlist the screenlist (one image with a grid of frames and an information header), file/regen_poster the poster and the thumbnail. /api/regen/slider, /api/regen/screenlist and /api/regen/poster are the same calls under other names.
	Each file of the list gets an entry: queued, or skipped with the reason: the file is not yours (no such file), is not a video, is a copy of another file (the pictures belong to the original upload), is end-to-end encrypted, is in the trash, has a password, a price or Premium only (the slider and the screenlist only: they are public files), or its poster is a picture its owner uploaded (never replaced). The screenlist also needs the permission of your account to make screenlists.
	A picture that is already in the queue stays there; a picture that was made is made again; one that is being made right now is left alone.
	The kind of picture has to be switched on by the site (time slider, screenlist or better screenshots), else the reply is 403. Up to 40 files per hour and account are accepted (shared with the poster picker of My Files), then the reply is 429. A file that is skipped (see above) does not count. Admins are not limited and may ask for any file.
	Errors: 400 invalid or missing file code, more than 20 codes; 403 the feature is off or nothing could be queued (the reason is in msg); 404 none of the files is yours; 429 too many requests.

Status code

200	Everything is OK. Request succeeded
400	Bad request (e.g. invalid file code, more than 20 codes)
403	Permission denied (the feature is off, or nothing could be queued: see msg)
404	File not found
429	Too many requests