Runway Best Practices

1. Handling Retry Logic

Whether a task is successfully submitted can be determined by checking if the returned code is 200. If successful, msg will display success information.

If there are errors, msg will show the specific error reason.

2. Task Callbacks

The most stable way to handle task callbacks is through a Webhook callback URL. When the video generation status changes (progress update/failure/success), the generation result will be sent to this Webhook URL via POST.

Pass your own webhook in the callback_url parameter when submitting a task request.

Your webhook will receive a POST request like this:

{
  "task_id": "d51c94db-f7fa-4ad3-a083-b8918686c478",
  "status": "3",
  "prompt": "a cat",
  "prompt_en": "a little kitten.",
  "video_url": "https://runwaycdn.cometapi.com/attachments/video/runway/20241011/8af2304880d6b32bfff5f0ea33007566.mp4",
  "poster": "https://runwaycdn.cometapi.com/attachments/video/runway/20241011/6771c68bf540b62a96e7c4a5b2b375a7.png",
  "last_frame": "https://runwaycdn.cometapi.com/attachments/video/runway/20241011/8af7cc2b46fc7ad5d1e0efedd0bd0893.png",
  "msg": null,
  "point": "320",
  "refund": "0",
  "create_time": "1728622596",
  "update_time": "1728622955"
}

1. Handling Retry Logic#

2. Task Callbacks#

1. Handling Retry Logic

2. Task Callbacks