Spaces method and path for this operation:
post /s/{space_id}/api/fleet/managed_integrations/_upgrade/dryrun
Refer to Spaces for more information.
Preview upgrading multiple managed integrations without applying any change. Targets the installed package version by default; pass pkgVersion to preview a specific (for example, not-yet-installed) version. Each result returns the current/proposed version and any migration errors, plus — only on a clean dry-run (hasErrors: false) — the migrated proposedPolicy. proposedPolicy is for the edit-and-upgrade flow (edit it, then save via the update (PUT) endpoint); to apply an upgrade as-is, use _upgrade.
Responses
-
Indicates a successful response. Each clean item (
hasErrors: false) previews the migrated policy as a consumable managed integration (proposedPolicy); a missing id, an id that is not a managed integration, or a migration error, is reported as a per-item failure (hasErrors: true, withproposedPolicyomitted) without failing the batch. Inspect every item. -
Bad Request
POST
/api/fleet/managed_integrations/_upgrade/dryrun
curl \
--request POST 'https://localhost:5601/api/fleet/managed_integrations/_upgrade/dryrun' \
--header "Authorization: $API_KEY" \
--header "Content-Type: application/json" \
--header "kbn-xsrf: true" \
--data '"{\n \"policyIds\": [\n \"d52a7812-5736-4fdc-aed8-72152afa1ffa\"\n ]\n}"'
Request examples
Upgrade managed integrations dry run request example
Preview the upgrade of managed integrations to their installed package version
{
"policyIds": [
"d52a7812-5736-4fdc-aed8-72152afa1ffa"
]
}
Preview the upgrade against an explicit target package version (for example, before installing the new version). Defaults to the installed package version when omitted.
{
"pkgVersion": "1.6.0",
"policyIds": [
"d52a7812-5736-4fdc-aed8-72152afa1ffa"
]
}
Response examples (200)
Upgrade managed integrations dry run migration errors example
Example dry-run response where migrating the config to the new version produced errors. `hasErrors` is true and `errors` explains why; do not feed the (partial) proposed config into the update endpoint without resolving them.
[
{
"currentVersion": "1.5.0",
"errors": [
{
"message": "Variable \"organization_id\" is required"
}
],
"hasErrors": true,
"id": "d52a7812-5736-4fdc-aed8-72152afa1ffa",
"name": "ess_billing-1",
"proposedVersion": "1.6.0"
}
]
Example dry-run response for a mixed batch: one managed integration previews cleanly while two ids are missing or not managed integrations. Ids that are missing or not managed integrations are surfaced as per-item failures (`hasErrors: true` + `statusCode`) without failing the batch, and results stay in request order.
[
{
"currentVersion": "0.5.0",
"hasErrors": false,
"id": "2e426392-f856-4ab2-bc31-92d4dbb8d134",
"name": "agentless_hello_world-16",
"proposedPolicy": {
"cloud_connector": null,
"created_at": "2026-07-01T15:59:08.299Z",
"created_by": "admin",
"description": "",
"id": "2e426392-f856-4ab2-bc31-92d4dbb8d134",
"inputs": {
"agentless_hello_world-cel": {
"enabled": true,
"streams": {
"agentless_hello_world.generic": {
"enabled": true,
"vars": {
"url": "https://epr.elastic.co"
}
},
"agentless_hello_world.mock_counter": {
"enabled": false,
"vars": {
"events_per_second": 10,
"mode": "constant",
"spike_events": 100,
"spike_every_seconds": 60
}
}
}
},
"agentless_hello_world-httpjson": {
"enabled": false,
"streams": {
"agentless_hello_world.generic": {
"enabled": false,
"vars": {
"url": "https://epr.elastic.co"
}
}
}
}
},
"name": "agentless_hello_world-16",
"namespace": "default",
"package": {
"name": "agentless_hello_world",
"title": "Agentless Hello World",
"version": "0.5.0"
},
"updated_at": "2026-07-01T16:02:14.067Z",
"updated_by": "admin"
},
"proposedVersion": "0.5.0"
},
{
"body": {
"message": "Agentless policy 9300464c-6cfc-4566-850d-e9e7927457fe not found"
},
"hasErrors": true,
"id": "9300464c-6cfc-4566-850d-e9e7927457fe",
"statusCode": 404
},
{
"body": {
"message": "Agentless policy 5b8763e9-791a-4038-be29-b384d578200e not found"
},
"hasErrors": true,
"id": "5b8763e9-791a-4038-be29-b384d578200e",
"statusCode": 404
}
]
Example clean dry-run response (`hasErrors: false`) with the proposed (migrated) policy. `proposedPolicy` is intended for the edit-and-upgrade flow: edit it and submit the edited payload to the update (PUT) endpoint. To apply without edits, use the `_upgrade` endpoint instead.
[
{
"currentVersion": "1.5.0",
"hasErrors": false,
"id": "d52a7812-5736-4fdc-aed8-72152afa1ffa",
"name": "ess_billing-1",
"proposedPolicy": {
"created_at": "2025-11-06T18:27:43.541Z",
"created_by": "test_user",
"description": "test",
"id": "d52a7812-5736-4fdc-aed8-72152afa1ffa",
"inputs": {
"ESS Billing-cel": {
"enabled": true,
"vars": {
"organization_id": "1234"
}
}
},
"name": "ess_billing-1",
"namespace": "default",
"package": {
"name": "ess_billing",
"title": "Elasticsearch Service Billing",
"version": "1.6.0"
},
"updated_at": "2025-11-06T18:27:43.541Z",
"updated_by": "test_user"
},
"proposedVersion": "1.6.0"
}
]
Response examples (400)
Example of a generic error response
{
"error": "Bad Request",
"message": "An error message describing what went wrong",
"statusCode": 400
}