---
title: "Set signing order"
method: PUT
path: "/documents/{document}/signatories/order"
tags: ["Document Operations"]
---

# Set signing order

`PUT /documents/{document}/signatories/order`

<small>Requires an API token with the **Document Manager** role.</small>

Set the order in which signatures will be collected from the document's [signatories](/#signatories).

For this to have an effect, this request must be made before moving the document to the
[signing stage](/operations/v1.documents.stage-transitions.signing), and signing must be started with the
`sequential_signing` option enabled.

## Path parameters

- `document` string, required

## Request body

- SyncSigningOrderRequest
  - `signing_order` string[], required — The UUIDs of the document's signatories, in the order in which they should sign

## Response `200`

Array of `SignatoryResource`

- object
  - `data` SignatoryResource[], required
    - `uuid` string, required
    - `first_name` string, nullable, required
    - `last_name` string, nullable, required
    - `email` string, nullable, required
    - `mobile_phone` string, nullable, required — Mobile phone number, in E.164 format
    - `title` string, nullable, required
    - `profile_photo_url` string, nullable, required
    - `signing_order` integer, nullable, required — When sequential signing is enabled, signatories will sign in ascending order of their `signing_order`
    - `has_account_user` boolean, required — `true` if the signatory has a fynk user belonging to your account
    - `party_uuid` string, nullable, required — UUID of the party that the signatory signs for

## Other responses

- `401` — Unauthenticated
- `403` — Authorization error
- `404` — Not found
- `422` — Validation error

---

[API](https://skmtc.dev/fynk/apis/fynk-api-reference.md) · [All operations](https://skmtc.dev/fynk/apis/fynk-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/fynk/fynk-api-reference/revisions/9657a6757f59/schema)