# Update a recipient on a draft, or correct one on a pending document

On a draft, the usual full edit (name, email, role, order, access code). On a pending document, only name and email may be corrected, and only for a recipient who hasn't signed yet — role, order, access code, and isGroup are structural, draft-only settings. Correcting email invalidates that recipient's current signing link (only theirs; every other recipient's token lives on their own row) and emails them a fresh one. Every correction is recorded in the document's audit trail with what changed. A correction can change a name but never blank it (a group slot always needs one too; only a draft individual may be nameless), and on a pending document cannot move a recipient onto an address another individual recipient already has, and once a payment has started on the slot the email cannot change at all (409 email_blocked_payment), because the charge belongs to the person who started it. Re-casing a recipient's own address is not a correction: it changes nothing and issues no new link. Names refuse control characters and invisible formatting characters (bidi overrides, zero-width space). Draft-only, isGroup true additionally converts an individual slot that has no email yet into a signer group (name becomes its label) — one-way, and only while the slot is still unaddressed; a group can't be converted back.

Canonical: https://easerix.com/docs/developers/api/sign/documents/updateRecipient

{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}

export default function Layout(props) {
  const { APIPage, OpenAPIPage } = props.components ?? {};
  // "APIPage" is the old name from v10, this allows both for backward compatibility
  const Comp = OpenAPIPage ?? APIPage;
  return (
    <>
      {props.children}
      <Comp document="sign" operations={[{"path":"/v1/documents/{id}/recipients/{rid}","method":"patch"}]} />
    </>
  );
}