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
  • API Endpoint
  • Parameters
  • Embedding in Markdown

Was this helpful?

  1. REST API

Markdown Badge API

PreviousOverviewNextApp configuration files

Last updated 1 year ago

Was this helpful?

The Markdown Badge API provided by Runway enables teams to display badges on their repositories, showcasing either the number of completed releases (release_count) or the live release version (live_release) of their app. These badges offer a dynamic way to present project status directly on markdown files, such as READMEs, and automatically link back to Runway for additional insights.

API Endpoint

To access the Markdown Badge API, use the following URL format:

https://app.runway.team/api/markdownBadge?app_id={APP_ID}&style={STYLE}&badge_type={TYPE}

Parameters

  • app_id (required): The unique identifier of your team’s app in Runway. You can find your app’s app_id by going to App settings > General > App identifier on the Runway dashboard

  • style: Defines the appearance of the badge. Options include:

    • flat (default)

  • flat-square

  • plastic

  • for-the-badge

  • social

  • badge_type: Specifies the type of information the badge displays. Options are:

    • release_count (default): Shows the number of completed releases on Runway

    • live_release: Displays the live release version number

Usage Example

To create a badge displaying the latest release version of your app in a flat style, your URL might look like this:

https://app.runway.team/api/markdownBadge?app_id=12345&style=flat&badge_type=live_release

This URL can be embedded in markdown files to display the badge.

Embedding in Markdown

To embed the badge in your markdown file, use the following syntax:

![Badge](https://app.runway.team/api/markdownBadge?app_id={APP_ID}&style={STYLE}&badge_type={TYPE})

Replace {APP_ID}, {STYLE}, and {TYPE} with your app's details.

📡