Reorder Rule Blocks
POST/api/v1/ingest/rules/order
Set the order one field's rule blocks run in.
If-Match is required, and a stale one answers 412 with the current ETag.
The pinned default keeps its place last. A rules-only change is one the
receiver reloads where it stands, so reload answers hot.
Request
Responses
- 200
- 401
- 403
- 409
- 422
- 503
- default
Successful Response
No valid session: the credentials are missing, invalid or expired, or the account behind them is disabled or blocked
Refused: the session lacks the action this route checks, or its account must replace an issued password first. A SCIM route answers a refused action in the RFC 7644 error envelope
The list names other blocks than the field has now, because a source or a binding changed since it was read (code order_conflict, the current list in blocks), or the deploy repo kept moving (code conflict)
Refused, nothing written: a block named twice or a pinned block (code invalid_order), or a binding the receiver could not compile (code invalid_binding)
No deploy repo, where the ingest rules live
Problem details (RFC 9457)