---
title: "Update a signatory"
method: PUT
path: "/v1/companies/{company_uuid}/signatories/{signatory_uuid}"
tags: ["Signatories"]
---

# Update a signatory

`PUT /v1/companies/{company_uuid}/signatories/{signatory_uuid}`

## Request

- Base URL: `https://api.gusto-demo.com`
- URL: `https://api.gusto-demo.com/v1/companies/{company_uuid}/signatories/{signatory_uuid}`
- Auth: HTTP bearer

Updates a signatory that has been either invited or created. If the signatory has been created with minimal information through the [Invite a signatory](ref:post-v1-companies-company_uuid-signatories-invite) endpoint, then the first update must contain all attributes specified in the request body in order to start the identity verification process.

## Related guides
- [Signatory Events](doc:signatory-events)

scope: `signatories:write`

## Path parameters

- `company_uuid` string, required
- `signatory_uuid` string, required

## Headers

- `X-Gusto-API-Version` '2026-06-15'

## Request body

- SignatoryUpdateRequest: Request body for updating a signatory. Email cannot be updated.
  - `version` string, required: Current version of the signatory (required for optimistic concurrency).
  - `first_name` string
  - `middle_initial` string
  - `last_name` string
  - `title` string
  - `phone` string
  - `birthday` string, date
  - `ssn` string: The signatory's SSN.
  - `home_address` object
    - `street_1` string
    - `street_2` string
    - `city` string
    - `state` string
    - `zip` string
    - `country` string

## Response `200`

Successful

- Signatory: The representation of a company's signatory
  - `uuid` string, required
  - `first_name` string, nullable
  - `last_name` string, nullable
  - `title` string, nullable
  - `phone` string, nullable
  - `email` string
  - `birthday` string, nullable
  - `is_admin` boolean: Whether or not the signatory is also the payroll admin of the company.
  - `has_ssn` boolean: Indicates whether the signatory has an SSN in Gusto.
  - `version` string: The current version of the signatory. See the [versioning guide](https://docs.gusto.com/embedded-payroll/docs/idempotency) for information on how to use this field.
  - `identity_verification_status` 'Pass' | 'Fail' | 'Skipped', nullable: | | | |---|---| |__Status__| __Description__ | | Pass | Signatory can sign all forms | | Fail | Signatory cannot sign forms | | Skipped | Signatory cannot sign Form 8655 until the form is manually uploaded as wet-signed | | null | Identity verification process has not been completed |
  - `home_address` object, nullable
    - `street_1` string
    - `street_2` string
    - `city` string
    - `state` string
    - `zip` string
    - `country` string

## Other responses

- `404`: Not Found The requested resource does not exist. Make sure the provided UUID is valid.
- `409`: Conflict
- `422`: Unprocessable Entity This may happen when the body of your request contains errors such as `invalid_attribute_value`, or the request fails due to an `invalid_operation`. See the [Errors Categories](https://docs.gusto.com/embedded-payroll/docs/error-categories) guide for more details.

---

[API](https://skmtc.dev/gusto/apis/gusto-api.md) - [All operations](https://skmtc.dev/gusto/apis/gusto-api/llms.txt) - [OpenAPI document](https://skmtc.dev/gusto/apis/gusto-api/revisions/f98575fa2a5e?raw)