Runway Call Best Practices

1. Handling Retry Logic

The success of the task submission can be determined by whether the code returned by the API is 200. If successful, msg will display a success message.

If there is an error, msg will display the specific error cause.

2. Task Callback

The most stable task callback method is to use a webhook callback URL. When the video generation status (progress/failure/success) changes, the generation results will be POSTed to this webhook URL.

When sending a task submission request, pass your own webhook in the callback_url parameter.

Your webhook will receive a POST request like this:

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

Runway Call Best Practices

1. Handling Retry Logic#

2. Task Callback#

1. Handling Retry Logic

2. Task Callback