---
title: "Add party"
method: POST
path: "/documents/{document}/parties"
tags: ["Document Operations"]
---

# Add party

`POST /documents/{document}/parties`

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

Adds a [party](/#parties) to a [document](/#documents).

## Adding an internal party

To add one of your account's internal parties to the document, send the `account_party_uuid` and `reference`
fields. The rest of the party data will be copied from the respective "account party".

## Adding an external party

To add an external party to the document, send these fields:

- `reference`
- `entity_name`
- `address`
- `scope`

> **Note:** When adding a party that is linked to an account party, only `reference` can be provided. Attempting
> to set the other fields will cause the request to be rejected with a validation error.

## Path parameters

- `document` string, required

## Request body

- StorePartyRequest
  - `reference` string, required — A generic reference for the party
  - `account_party_uuid` string, uuid — UUID of a party from Settings > My Parties. When this is provided, `reference` is the only other field that can be sent.
  - `entity_name` string — The actual name of the party. i.e. name of the company or person. Must be non-null in order for the document to [proceed to the signing stage](/operations/v1.documents.stage-transitions.signing)
  - `address` string, nullable — The party's address
  - `scope` 'internal' | 'internal_and_external'

## Response `200`

`DocumentPartyResource`

- object
  - `data` DocumentPartyResource, required
    - `uuid` string, required
    - `ref_uuid` string, required — If the document containing this party was created from a template, this identifier will be the same as the `ref_uuid` of the corresponding party in the source template.
    - `reference` string, nullable, required — A generic reference for the party
    - `entity_name` string, nullable, required — The actual name of the party. May be null if the party was created via a Template's "set later" option
    - `address` string, nullable, required
    - `scope` 'internal' | 'internal_and_external', required
    - `is_internal_party` boolean, required — Indicates whether this party is linked to an account party (internal) or is standalone (external)
    - `is_ready_for_signing` boolean, required — `true` indicates that an external party has indicated they are ready to sign
    - `ready_for_signing_at` string, date-time, nullable, required
    - `created_at` string, date-time, nullable, required
    - `updated_at` string, date-time, nullable, required
    - `signatories` SignatorySnippetResource[] — These are the users who will sign on behalf of this party during the `signing` stage
      - `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

## Other responses

- `401` — Unauthenticated
- `403` — Authorization error
- `404` — Not found
- `409` — The resource's current state prevents the requested change
- `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)