Create or update several dataset substitutions atomically

Validates the whole replacement graph — including constraints that span the mappings in the request, such as a field substitute parented by an entity this same batch remaps — and then commits every mapping or none. Each response reports an outcome per mapping, so a rejected batch tells the caller everything that is wrong in one round-trip.

A mapping whose original already has a substitute repoints it, releasing the substitute it used to hold, so a request may hand that substitute to a different original in the same batch. The graph is judged on the state the request would leave behind, not on the rows stored when it arrived.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

The ID of the dataset

Body Params
substitutions
array of objects
required
length between 1 and 100

The mappings to apply together. Order is irrelevant: a field substitute may be parented by an entity that another mapping in the same request remaps, regardless of their positions. Each original may appear at most once. The upper bound exists because every mapping costs catalog reads; it is enforced by the service as well, so it holds for any caller.

substitutions*
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json