org
Plan configuration file changes (v2)
Compares a Configuration as Code (v2) YAML file with its app and lists every change applying it would make, without changing anything. The file's app.id picks the app; a file without one creates a new app in the organization. Pass the returned planId to applyConfigFile. A file that already matches its app returns a plan with status unchanged, which has nothing to apply. Requires an admin API key. See Configuration as Code for the file format.
post/org/{orgId}/config-file/plan
Request
- Base URLhttps://api.runway.team
- URLhttps://api.runway.team/org/{orgId}/config-file/plan
- AuthAPI key in header X-API-Key
Path parameters
orgIdstring required
The ID of the org.
Request body application/yaml
string binary required
Response
The plan, with status planned, or unchanged when 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.