---
title: "Recipient routing"
description: "Choose sequential routing to have recipients act one at a time in order, or parallel routing to notify every signer at once."
canonical: "https://signatureapi.com/docs/api/resources/envelopes/routing"
source: "https://signatureapi.com/docs/api/resources/envelopes/routing.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T12:07:52Z"
---

# Recipient routing

Choose sequential routing to have recipients act one at a time in order, or parallel routing to notify every signer at once.

_Last verified against API version 1.18.0._

The `routing` property controls the order in which recipients receive and act on the envelope. Two options are available: `sequential` and `parallel`. The default is `sequential`.

**Diagram: sequential and parallel routing.** The route an envelope takes, step by step: your app sends the envelope, it is `processing` and then `in_progress`, each recipient gets the request and completes, and the envelope is `completed`. The page lets you play each step.

`"routing": "sequential"` with Sam Patel (`preparer`), Alex Chen (`approver`), Jane Doe (`signer`). One recipient at a time, in `recipients` order. Each one must complete before the next is notified.

Route: your app sends the envelope; Sam Patel, Alex Chen and Jane Doe act in turn; the envelope completes.

1. **Envelope created.** It is `processing` while SignatureAPI processes the documents. No recipient has the request yet. Events: `envelope.created`. Envelope `processing`; Sam Patel `pending`, Alex Chen `pending`, Jane Doe `pending`.
2. **Envelope started.** It is `in_progress`. Sam Patel gets the request first; Alex Chen and Jane Doe wait in `awaiting`. Events: `envelope.started`, `recipient.released` (Sam Patel), `recipient.sent` (Sam Patel). Envelope `in_progress`; Sam Patel `sent`, Alex Chen `awaiting`, Jane Doe `awaiting`.
3. **Sam Patel prepared.** Alex Chen gets the request next. Events: `recipient.completed` (Sam Patel), `recipient.released` (Alex Chen), `recipient.sent` (Alex Chen). Envelope `in_progress`; Sam Patel `completed`, Alex Chen `sent`, Jane Doe `awaiting`.
4. **Alex Chen approved.** Jane Doe gets the request next. Events: `recipient.completed` (Alex Chen), `recipient.released` (Jane Doe), `recipient.sent` (Jane Doe). Envelope `in_progress`; Sam Patel `completed`, Alex Chen `completed`, Jane Doe `sent`.
5. **Jane Doe signed.** Every recipient completed, so the envelope is `completed`. Events: `recipient.completed` (Jane Doe), `envelope.completed`. Envelope `completed`; Sam Patel `completed`, Alex Chen `completed`, Jane Doe `completed`.

`"routing": "parallel"` with Jane Doe (`signer`), John Smith (`signer`), Maria Garcia (`signer`). Every signer gets the request at once and signs in any order. Parallel accepts `signer` and `automatic_signer` only, so this example has three signers.

Route: your app sends the envelope; Jane Doe, John Smith and Maria Garcia act all at once, in any order; the envelope completes.

1. **Envelope created.** It is `processing` while SignatureAPI processes the documents. No recipient has the request yet. Events: `envelope.created`. Envelope `processing`; Jane Doe `pending`, John Smith `pending`, Maria Garcia `pending`.
2. **Envelope started.** It is `in_progress`. Jane Doe, John Smith and Maria Garcia get the request at the same time. Events: `envelope.started`, `recipient.released` (Jane Doe), `recipient.sent` (Jane Doe), `recipient.released` (John Smith), `recipient.sent` (John Smith), `recipient.released` (Maria Garcia), `recipient.sent` (Maria Garcia). Envelope `in_progress`; Jane Doe `sent`, John Smith `sent`, Maria Garcia `sent`.
3. **Jane Doe signed.** John Smith and Maria Garcia can still sign, in any order. Events: `recipient.completed` (Jane Doe). Envelope `in_progress`; Jane Doe `completed`, John Smith `sent`, Maria Garcia `sent`.
4. **John Smith signed.** Maria Garcia can still sign. Events: `recipient.completed` (John Smith). Envelope `in_progress`; Jane Doe `completed`, John Smith `completed`, Maria Garcia `sent`.
5. **Maria Garcia signed.** Every recipient completed, so the envelope is `completed`. Events: `recipient.completed` (Maria Garcia), `envelope.completed`. Envelope `completed`; Jane Doe `completed`, John Smith `completed`, Maria Garcia `completed`.

Every invitation here goes by email. A recipient whose ceremony your app creates also moves to `sent`, with `recipient.sent`, once the ceremony is created; until then it stays `pending`.

## Sequential routing

With sequential routing, the envelope is delivered to one recipient at a time, in the order listed in the `recipients` array. Each recipient must complete their part before the next one is notified.

- Recipients act in the order defined in the `recipients` array.
- Each recipient must complete before the next one is notified.
- Recipients acting later can see signatures and data entered by those who acted before them.
- Recipients waiting for a previous recipient will have a status of `awaiting`.
- Use this when the order of signatures matters.

## Parallel routing

With parallel routing, all recipients receive the envelope at the same time and can act in any order.

- All recipients are notified simultaneously.
- Recipients can act in any order.
- Use this when signing order does not matter.

> **Warning:** Parallel routing accepts the recipient types `signer` and `automatic_signer` only ([qualified signers](https://signatureapi.com/docs/qualified-signatures/envelope-rules) need sequential routing too). It also rejects input places (`text_input`, `boxed_text_input`, `checkbox`, `dropdown` and `radio_group`), even when the envelope has a single recipient. An envelope with an [approver](https://signatureapi.com/docs/api/resources/recipients/approver), a [preparer](https://signatureapi.com/docs/api/resources/recipients/preparer) or an input place needs sequential routing; otherwise the request fails with a [validation error](https://signatureapi.com/docs/v1/errors/validation-error).

## Setting routing on an envelope

Set the `routing` property when creating an envelope. If omitted, sequential routing is used.

```http {8}
POST /v1/envelopes HTTP/1.1
Host: api.signatureapi.com
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
  "title": "Service Agreement",
  "routing": "parallel",
  "documents": [
    {
      "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/acme-service-agreement.pdf",
      "places": [
        { "key": "client_signs_here", "type": "signature", "recipient_key": "client" },
        { "key": "provider_signs_here", "type": "signature", "recipient_key": "provider" }
      ]
    }
  ],
  "recipients": [
    { "type": "signer", "key": "client", "name": "Jane Doe", "email": "jane.doe@example.com" },
    { "type": "signer", "key": "provider", "name": "John Smith", "email": "john.smith@example.com" }
  ]
}
```
