Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase Crashlytics
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Create an API key
  • Revoke an API key
  • Interact with the API

Was this helpful?

  1. REST API

Overview

PreviousOutgoing webhooksNextMarkdown Badge API

Last updated 1 month ago

Was this helpful?

This feature is limited to certain plans. Please visit our to learn more.

Runway’s REST API (available for Enterprise teams and above) offers more flexibility in how your team can take advantage of Runway’s core features. By using the Runway API to interact with entities within Runway (like ‘releases’), you can create powerful workflows that leverage Runway’s functionality in concert with your team’s existing toolchain and processes.

To get started, create an API key from the organization settings of your Runway dashboard.

Create an API key

Admin permissions are required to create API keys.

Navigate to your organization settings page, where you’ll find the API keys section. Then, create a new API key – you'll be prompted to fill in the following details about your new key:

  • API key name – The key's name. We recommend a descriptive name to help you remember what the key will be used for.

  • Group scopes – The user groups whose allowed user actions the API key should be granted.

  • App scopes – The apps that the API key should be granted access to.

  • Admin scope – If selected, the API key will be given admin scope, which will grant it access to perform all actions across all apps in the organization.

To configure an API key with org-wide read-only scope, leave the Group scopes and App scopes fields empty, and keep the Admin scope field unchecked. To configure read-only access for only a subset of apps in the organization, select the apps from in the App scopes field, but leave Group scopes empty.

Be sure to copy your new API key immediately, as it will not be available again once you complete the creation flow. Remember to store your API key in a safe place.

Revoke an API key

To revoke access to an API key, delete it from the list of keys in your organization. This will immediately revoke the key’s access to the API, and remove it from the list of active keys for your organization.

Interact with the API

Once you’ve created an API key, you’re ready to start calling endpoints on the Runway API. For detailed instructions on how to authenticate requests to the API, and to learn more about the endpoints available, please visit our .

📡
pricing page
🔗
API reference documentation