---
title: "Add a destination to an existing app's workflow from a configuration file"
method: POST
path: "/app/{appId}/destination/config"
tags: ["app"]
---

# Add a destination to an existing app's workflow from a configuration file

`POST /app/{appId}/destination/config`

## Request

- Base URL: `https://api.runway.team`
- URL: `https://api.runway.team/app/{appId}/destination/config`
- Auth: API key in header `X-API-Key`

Accepts the same YAML schema as `createAppFromConfig`, but instead of creating a new app, adds a new destination to the given app's existing workflow. The YAML's `name`/`icon` become the destination's name and icon; `integrations` are installed as new app integrations from existing org providers; `appSettings.branchSettings` are stored as a per-destination branch config; `stepGroups` are cloned into the workflow as new step configs. Other fields (appGroup, appUsers, appStoreReleaseSettings, buildDistro, tagSettings, featureAffiliations) are ignored.

## Path parameters

- `appId` string, required

## Request body `application/yaml`

- string, binary: The YAML file describing the new destination. Attach this either as raw text to the request body or as a binary file.

## Response `200`

The destination was successfully added

## Other responses

- `400`: Bad request response
- `404`: Resource not found response

---

[API](https://skmtc.dev/runway/apis/runway-rest-api.md) - [All operations](https://skmtc.dev/runway/apis/runway-rest-api/llms.txt) - [OpenAPI document](https://skmtc.dev/runway/apis/runway-rest-api/revisions/081109863a9a?raw)