Skip to main content
ConfigView reads your Runway (AI video and image generation) organization through the Runway API (https://api.dev.runwayml.com), using an API key from the Runway developer portal. ConfigView sends only reads: GET requests, plus one POST to the usage report that only returns numbers. It never creates a generation and never changes anything in Runway. You will end up with 1 required secret (RUNWAY_API_KEY) and 1 optional secret (RUNWAY_ORGANIZATION_ID) in ConfigView when setup is complete.
What you get depends on your Runway plan.
  • Any plan with API access: credit balance, monthly spend cap, usage-tier limits and credits spent per model per day.
  • Enterprise plan, after the one-time account link (Step 3): workspace members with role, status and last active date, credits per person and project, and the audit log.
On any other plan the three Enterprise collectors finish cleanly with 0 rows. That is not an error.

What you need

  • A Runway developer portal account (https://dev.runway.com) that can create API keys
  • For the Enterprise data: an Enterprise Runway plan, an admin of the API project and an admin (or billing admin) of the Runway workspace (two people may be needed, see Step 3)

Step 1: Open the Runway page in ConfigView

Open ConfigView in a second browser tab and leave it open: https://{companyname}.configview.com/admin/integrations/runway

Step 2: Create the API key

  1. In the developer portal open your organization and choose API Keys, then Create key
  2. Name it (for example ConfigView) and copy it when shown
  3. In the ConfigView tab paste it into RUNWAY_API_KEY under Credentials and save
Runway does not offer a read-only or scoped key, so the key can also start generations (and spend credits). Store it only in ConfigView, give it its own name so you can find it, and revoke it in the portal to cut ConfigView off. The key does not expire and Runway does not rotate it.
Members, per-person usage and audit logs live in the Runway web app, not the developer portal. Runway asks you to link the two once. Skip this step if you are not on an Enterprise plan.
  1. Admin of the API project: in the developer portal open Manage > Connections and generate a one-time connection code. The code is short-lived, so hand it over soon after creating it.
  2. Admin or billing admin of the Runway workspace: in the Runway web app open the workspace (or organization) settings and paste the code.
  3. If the same person holds both roles they can do both steps.
Who the link covers: a code created by a person links every organization workspace where that person is an admin; a code created while acting as one workspace links only that workspace. The scope cannot be widened from the API afterwards. Once linked there is nothing to refresh or rotate. Until the link exists Runway answers “No workspace is linked to this API project” and ConfigView stores 0 rows for the Enterprise tables. If your API project is linked to more than one organization, set RUNWAY_ORGANIZATION_ID to the id of the one to report on.

Step 4: Connect and verify

  1. Click Connect. ConfigView creates its tables and schedules every collector at your default run time:
  1. Click Verify now. The health check reads the secret, reads the organization, then tries the members endpoint and tells you whether the Enterprise data is reachable. A “not available” answer for Enterprise is informational and does not fail the check.
If a check fails:
  • 401 on the organization. The API key is wrong or revoked.
  • Enterprise endpoints not available. Your plan is not Enterprise, or the account link in Step 3 has not been made.

Data Tables

Each table has a run_at column and keeps only the newest run.

Things worth knowing

Per-person usage is summed. Runway returns one row per generation. ConfigView adds them up per day, person, project and tool and keeps only the totals; the transaction and task ids are discarded. Roles. Runway’s roles are viewer, editor, admin and non-generating-admin. Status is active, invited or deactivated (with a reason: removed, invite ended or suspended). Credits. Amounts are Runway credits, not dollars. A day’s total can be negative when refunds exceed charges. Audit log detail. ConfigView stores the event list only. The per-event detail (metadata, resource, IP address, user agent) is never requested because metadata can name assets. Rate limit. The members, usage and audit endpoints allow 10 requests every 10 seconds per API project and then answer HTTP 429. ConfigView paces itself at 30 requests a minute, honors Retry-After, and reads 100 rows per page. The organization endpoints state no limit and use the same gentle pace. Known gaps and first-run checks. The organization and credit-usage field names come from Runway’s API specification and have not yet been run against a live account. Runway documents a 401 for non-Enterprise requests; ConfigView also treats 403 and a 400 “not linked” answer as “not available” and stores 0 rows. A 401 caused by a bad key is told apart by the health check, not by the collectors.

What isn’t collected

  • Prompts, generated images or videos, links to them, and task or transaction ids
  • Avatars, voices, documents, workflows and any other content objects
  • Audit event metadata and detail
  • The API key value or the connection code