org
Apply a configuration file plan (v2)
Applies a plan from planConfigFileChanges, making exactly the changes it listed. Send the same file you planned. Applying runs in the background: the response is the plan with status queued, so get it with getConfigFilePlan until its status is applied or failed. The apply is refused if the file or the app changed since the plan; plan again to review the new changes. A failed plan can be applied again, and continues from where it stopped. Requires an admin API key.
post/org/{orgId}/config-file/apply
Request
- Base URLhttps://api.runway.team
- URLhttps://api.runway.team/org/{orgId}/config-file/apply
- AuthAPI key in header X-API-Key
Path parameters
orgIdstring required
The ID of the org.
Query parameters
planIdstring required
The planId returned by planConfigFileChanges for this file.
Request body application/yaml
string binary required
Response
The plan has nothing to apply, since the file matches its app.
Example response
{
"planId": "8f3c1e2a-5b7d-4c1e-9a2f-0d6e4b3c2a1f",
"orgId": "acme",
"appId": "acme-ios",
"status": "planned",
"createdBy": "key_123",
"createdAt": "2026-10-19T14:02:11Z",
"summary": {
"flightpath": {
"update": 1
}
},
"changes": [
{
"path": "flightpath.steps.$release.settings.appStoreSettings.phasedRelease",
"action": "update",
"from": false,
"to": true,
"line": 212
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.