Switch managed cleanup on or off for many relation types

put

https://api.test.bluestonepim.com/rules-engine/relations/settings

The bulk write for the Rules Engine settings page, which saves every changed row with one Save button. Only the listed relation types change; a relation type that is not listed keeps its value. Every check (body, ids, values, duplicates, PIM, activeRuleCount) runs before the first write, so a 400, 404, 502 or read-fault 500 saves nothing. The writes are not atomic: a write fault stops at that item, the items before it stay saved, and the response is 500 - load the settings again with POST /relations/settings. Sending the same request again is safe. A history event is written for each relation type whose value changes. This does not start a run. Requires write permission.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

Language

Credentials

OAuth2

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200OK. One entry per relation type sent, in the order sent.

403Forbidden. Nothing was saved. At least one item is true and managed cleanup is not enabled for this organization. A request that only sends false is allowed. A caller with no write permission also gets 403, with a different message.

404Not Found. Nothing was saved. PIM does not know one of the relation types. The message names the first one.

500Internal Server Error. The activeRuleCount read failed (nothing was saved), or a write failed (the items before it are saved). The switch values are unknown, not off - load them again. Sending the same request again is safe.

502Bad Gateway. The PIM check failed: PIM could not be reached, or answered with an error (for example 401). Nothing was saved. The switch values are unknown, not off - retry. Unlike the single PUT, the Rules Engine sends this body itself.