Patch Supplier

Edit identity fields on the registry row.

Each field on the PATCH body is optional; omitted fields keep their current value, and explicit null clears a nullable field. name cannot be cleared (it's required).

Outcomes

The PATCH may take one of four code paths depending on how many organizations link to the supplier and whether the new identity collides with another row's fingerprint. Branch on meta.outcome:

outcomeWhenEffect
in_placeOnly your organization links to the supplier.The global row is updated. data.id is unchanged.
forkMultiple organizations link; the new fingerprint does NOT collide.A new global row is minted with the edited identity; your link is repointed; other orgs continue to see the original row. data.id is the new id.
fork_into_existingMultiple organizations link AND the new fingerprint collides with an existing global row.Your link repoints to the collider; no new row minted. data.id is the collider's id.
mergeOnly your organization links AND the new fingerprint collides.Your link repoints to the collider; the original row is soft-deleted. data.id is the collider's id.

Always trust data.id for "where your link points now" โ€” it may differ from the request's :id after a fork or merge.

Propagation to pending DDS records

Every pending DDS version of your organization that references this supplier is updated:

  • Its dds_record_version_shed.supplier_id is repointed when the outcome is fork / fork_into_existing / merge.
  • One supplier.propagated event is appended per affected version (with propagated_via: "live_link").
  • On fork / fork_into_existing a supplier.forked event is additionally appended; on merge, a supplier.merged event.

Affected version ids are listed in meta.affected_dds_version_ids.

Frozen DDS versions (already submitted, or older versions that have been frozen by a subsequent version cut) are not affected โ€” they keep their snapshot identity.

Errors

  • 400 โ€” invalid country code, oversize field, unknown key, or a duplicate external_id for your organization.
  • 404 โ€” supplier not linked to your organization.

Required scope: parties:write