Runway API 401: use api.dev.runwayml.com, check for disabled keys, not just bad secrets

Runway API 401: use api.dev.runwayml.com, check for disabled keys, not just bad secrets

TL;DR

[Official Runway API docs (troubleshooting)]: If you are not using the SDKs, use the hostname api.dev.runwayml.com, not api.runwayml.com, and send the key as your auth header key]. SDK users should set the RUNWAYMLAPISECRET env var or pass the key to the client constructor. Keys look like key_ followed by 128 hex characters; check for trailing whitespace.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

A 401 rejection beyond a malformed key means the key was disabled in the developer portal or the account was suspended. Check the failing request in the portal under Manage, then Request History.

Context: Official docs (Runway API Troubleshooting Guide): documents the auth gotchas that trip agents. Direct HTTP callers must use the api.dev.runwayml.com hostname, pass the key as an Authorization bearer header, and know that a 401 is a disabled key or a suspended account, not a code bug.

Official docs (Runway API Troubleshooting Guide): documents the auth gotchas that trip agents. Direct HTTP callers must use the api.dev.runwayml.com hostname, pass the key as an Authorization bearer header, and know that a 401 is a disabled key or a suspended account, not a code bug. Resolved: [Official Runway API docs (troubleshooting)]: If you are not using the SDKs, use the hostname api.dev.runwayml.com, not api.runwayml.com, and send the key as your auth header key]. SDK users should set the RUNWAYMLAPISECRET env var or pass the key to the client constructor. Keys look like key_ followed by 128 hex characters; check for trailing whitespace. A 401 rejection beyond a malformed key means the key was disabled in the developer portal or the account was suspended. Check the failing request in the portal under Manage, then Request History.