---
title: "Force-apply metadata cascade policy to folder"
method: POST
path: "/metadata_cascade_policies/{metadata_cascade_policy_id}/apply"
tags: ["Metadata cascade policies"]
---

# Force-apply metadata cascade policy to folder

`POST /metadata_cascade_policies/{metadata_cascade_policy_id}/apply`

Force the metadata on a folder with a metadata cascade policy to be applied to
all of its children. This can be used after creating a new cascade policy to
enforce the metadata to be cascaded down to all existing files within that
folder.

## Path parameters

- `metadata_cascade_policy_id` string, required

## Request body

- object
  - `conflict_resolution` 'none' | 'overwrite', required — Describes the desired behavior when dealing with the conflict where a metadata template already has an instance applied to a child. * `none` will preserve the existing value on the file * `overwrite` will force-apply the templates values over any existing values.

## Response `202`

Returns an empty response when the API call was successful. The metadata
cascade operation will be performed asynchronously.

The API call will return directly, before the cascade operation
is complete. There is currently no API to check for the status of this
operation.

## Other responses

- `404` — Returns an error when the policy can not be found or the user does not have access to the folder. * `instance_not_found` - The policy could not be found * `not_found` - The folder could not be found or the user does not have access to the folder.
- `default` — An unexpected client error.

---

[API](https://skmtc.dev/box/apis/platform-api.md) · [All operations](https://skmtc.dev/box/apis/platform-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/box/platform-api/revisions/ba8f087e1a4d/schema)