Does a 401 or 403 mean I should grant Admin?

First verify the Runway selection and a complete, enabled developer-project key without Bearer, spaces or Cookies. Developer is a key-management role, not a balance-only key permission. Ask an existing administrator to check project access and the key; do not blindly grant Admin. Rotate only through the secure page.

Why is the API balance zero when my web app has Credits?

Web-app and developer API funds have separate accounting. Enterprise transfer features do not automatically merge workspace balances: verify that a transfer actually reached this API project. Zero is a valid balance result, not a test of every model's availability.

Why does the API say organization instead of project?

The endpoint remains /v1/organization, while the current developer portal calls its key-and-funds scope a project. Quota Monitor identifies it as api_project and lets the key select it. It is neither your Quota Monitor business project nor a total of every workspace in a Runway enterprise.

Should I subtract usage or a tier limit from Credits?

No. creditBalance already reports remaining Credits. The 100 Credits = $1 conversion only gives face value. tier.maxMonthlyCreditSpend is a purchase ceiling and usage describes activity; neither should be deducted from the balance. Do not sum the same project through multiple keys.

What if a purchase is missing, or I see 429 or an invalid response?

Confirm posting in Billing for the same project, then refresh after the cooldown. Do not repeatedly retry a 429. Missing fields or non-integer balances fail safely and preserve the older result and time, rather than becoming zero. Share only redacted error codes, timestamps and scope, never keys.

Can I use a Cookie or another provider's key for read-only access?

No. Only an official developer API key is supported, not web sessions, Cookies, Kie.ai or another host's key, or a custom endpoint. If you cannot accept a key capable of paid generation, use manual checking rather than expanding permissions.

Runway API Credits: Check Your Balance & Set Up a Key

Awaiting live-account verification

Guide updated 2026-10-12

Implemented from Runway's official OpenAPI, setup and role documentation. Live-account verification is pending: signed-in key creation, permissions and balance reconciliation have not been tested. Automated checks do not replace account verification.

Required credentials: Runway Dev API Key
Monitoring currency: USD · Credit face value
What is monitored: API Credits · USD value; GET https://api.dev.runwayml.com/v1/organization reads creditBalance using a Bearer key and X-Runway-Version: 2024-11-06. The API calls this scope organization; Runway Dev currently calls it a project. Its keys share Credits. We preserve Credits and show credits / 100 at 100 Credits = $1, not a wallet created by a Quota Monitor project.

Check Runway API Credits without sharing a key

Sign in at dev.runway.com and select the API project paying for your integration, not a web-app workspace.
Open the project's Billing section and read Credits. If dollars are also shown, compare at 100 Credits = $1.
Ask an existing Admin or Billing admin to handle any purchase in this project. Its keys share funds; do not combine them with web subscriptions or other API projects.

Open official Runway page

Connect Runway to Quota Monitor

Choose the developer project that pays for your API calls
Open Runway Dev at dev.runway.com, sign in and select the project used by your integration. If you have never set up an API project, create one in the developer portal first; do not create an empty replacement for an existing funded project.
Open that project's Billing section and note its name and Credits privately. Checkpoint: you are looking at developer API funds, not a Standard, Pro, Unlimited or other web-app subscription.
Open official Runway page(opens in a new tab)
Check who can create the monitoring key
Open API Keys in the selected project; newer navigation may group it under Manage. An existing Developer or Admin can create and disable keys. Billing admin can manage funds but cannot create keys.
If creation is unavailable, ask an existing project administrator to help with a dedicated key. Do not upgrade the monitoring user to Admin as a troubleshooting shortcut. User roles do not make a key read-only; use the manual check instructions if required by your security policy.
Open official Runway page(opens in a new tab)
Create and save a dedicated API key
In API Keys, use the new-key action and give it a recognizable name, such as Quota Monitor balance. Confirm the selected API project before creating it. Keep this separate from the key running your production generation jobs.
Save the complete value in a password manager when it is revealed; it is only shown once. If lost, create a replacement instead of extracting a web session. Checkpoint: you have the full API key, not its name, visible prefix or a browser Cookie.
Open official Runway page(opens in a new tab)
Add Runway inside your Quota Monitor project
Return to Quota Monitor, open the business project you want to monitor and add a provider connection. Choose Runway (API Credits · USD value) and use a name that identifies the upstream project, such as Runway · Video production.
Paste the complete key into the masked API Key field without Bearer or header text. There is one credential field, no upstream project ID, and the currency is USD. For MCP setup, enter the key through the secure setup link, never in the conversation.
Save and check the first successful sync
Review the connection name and provider, then save. Wait for the initial sync, or refresh after the cooldown ends. Checkpoint: the successful query time updates and both an amount and raw Credits appear, rather than a pending state.
Only the final four key characters appear in connection lists; credentials are encrypted on the backend. A 401, 403, 429 or malformed response is not zero Credits. On failure, check the last successful time and redacted error code; never send a key or raw response to support.
Reconcile against the same Runway API project
Return to Billing for the same Runway Dev project and compare raw Credits. For example, 2450 Credits should appear as $24.5 here. If the portal shows dollars, reconcile at 100 Credits = $1 rather than reverse-engineering model prices.
Do not deduct usage or treat tier.maxMonthlyCreditSpend as available funds. To monitor a different API project, create a separate connection with its own key. Multiple connections to the same API project do not represent separate wallets.
Open official Runway page(opens in a new tab)
Open Runway when funds need attention
Use Open provider on the card, sign in and confirm the API project before entering Billing. An existing Admin or Billing admin can complete any purchase on the official platform. Quota Monitor does not collect top-up payments or adjust autobilling.
After a purchase or an eligible Enterprise transfer has posted, refresh and compare that same project. Web-app subscription Credits do not establish the API balance. Refreshing cannot make an unposted payment settle faster.
Open official Runway page(opens in a new tab)
Rotate or disable the monitoring key
Create a replacement dedicated key under API Keys in the same API project. Update the connection through Quota Monitor's secure page, verify a successful sync, then disable the old key. If a leak is suspected, disable it at Runway immediately instead of waiting for a routine rotation.
Disabling a connection or removing its association with a Quota Monitor project does not revoke the upstream key. Runway keys belong to a project, not a person, so removing a member does not revoke them either. A Developer or Admin must disable the key separately.
Open official Runway page(opens in a new tab)

What Quota Monitor reads from Runway

This connector reads the Runway developer API project's balance, not web-app subscriptions or other hosts. Eligible Enterprise organizations may transfer Credits between API projects and web workspaces; only funds held by this API project are read, not an enterprise-wide total.
Both raw Credits and exact USD face value are shown. Face value is not withdrawable cash, the tax-inclusive purchase price or a per-key allowance. Never subtract usage again or add duplicate project balances. tier.maxMonthlyCreditSpend is a purchase ceiling, not remaining funds.
The official creditBalance contract requires a non-negative integer. Missing, negative, fractional or malformed values and failed requests retain the last successful snapshot and time; they never become a guessed zero. Query time is not settlement time, and positive Credits do not guarantee generation availability.
Only api.dev.runwayml.com is used, with no custom endpoint or separate project ID. This connector does not read generated content, generate media, pay, top up or change autobilling. No compatible balance-only key permission is confirmed.
The dashboard shows the latest successful snapshot. Manual refresh queries the provider again but cannot eliminate upstream billing delays. An old balance is not a new result after a failed query.

Runway FAQ and troubleshooting

Does a 401 or 403 mean I should grant Admin?: First verify the Runway selection and a complete, enabled developer-project key without Bearer, spaces or Cookies. Developer is a key-management role, not a balance-only key permission. Ask an existing administrator to check project access and the key; do not blindly grant Admin. Rotate only through the secure page.
Why is the API balance zero when my web app has Credits?: Web-app and developer API funds have separate accounting. Enterprise transfer features do not automatically merge workspace balances: verify that a transfer actually reached this API project. Zero is a valid balance result, not a test of every model's availability.
Why does the API say organization instead of project?: The endpoint remains /v1/organization, while the current developer portal calls its key-and-funds scope a project. Quota Monitor identifies it as api_project and lets the key select it. It is neither your Quota Monitor business project nor a total of every workspace in a Runway enterprise.
Should I subtract usage or a tier limit from Credits?: No. creditBalance already reports remaining Credits. The 100 Credits = $1 conversion only gives face value. tier.maxMonthlyCreditSpend is a purchase ceiling and usage describes activity; neither should be deducted from the balance. Do not sum the same project through multiple keys.
What if a purchase is missing, or I see 429 or an invalid response?: Confirm posting in Billing for the same project, then refresh after the cooldown. Do not repeatedly retry a 429. Missing fields or non-integer balances fail safely and preserve the older result and time, rather than becoming zero. Share only redacted error codes, timestamps and scope, never keys.
Can I use a Cookie or another provider's key for read-only access?: No. Only an official developer API key is supported, not web sessions, Cookies, Kie.ai or another host's key, or a custom endpoint. If you cannot accept a key capable of paid generation, use manual checking rather than expanding permissions.

Official Runway references

Prepared by Quota Monitor, not an official provider tutorial. Interfaces and permissions may change; check official pages. Verification is limited to the scope stated here.