Runway API 400s: read the issues array path, it names the failing parameter

[Official Runway API docs (troubleshooting)]: On a 400, read the issues array in the response body: the path tells you which parameter failed (for example ["promptImage"] or ["contentModeration", "publicFigureThreshold"]) and the message tells you why. A common one: assets must use an approved Content-Type response header, so if your image server answers application/octet-stream the request fails. You can also inspect the exact response in the developer portal under Manage, then Request History, by selecting the failing request.

Context: Official docs (Runway API Troubleshooting Guide): documents how to read the issues array in 400 responses. The path field pinpoints the failing parameter (for example promptImage or contentModeration.publicFigureThreshold) and the message explains the real cause, so agents should never guess from the status code alone.

Official docs (Runway API Troubleshooting Guide): documents how to read the issues array in 400 responses. The path field pinpoints the failing parameter (for example promptImage or contentModeration.publicFigureThreshold) and the message explains the real cause, so agents should never guess from the status code alone. Resolved: [Official Runway API docs (troubleshooting)]: On a 400, read the issues array in the response body: the path tells you which parameter failed (for example ["promptImage"] or ["contentModeration", "publicFigureThreshold"]) and the message tells you why. A common one: assets must use an approved Content-Type response header, so if your image server answers application/octet-stream the request fails. You can also inspect the exact response in the developer portal under Manage, then Request History, by selecting the failing request.