---
title: "Send Engagement Letters With Approver Review"
description: "Have a partner approve an engagement letter before the client initials the fee clause and signs, and name the signed package after the matter."
canonical: "https://signatureapi.com/docs/use-cases/law-firm-engagement"
source: "https://signatureapi.com/docs/use-cases/law-firm-engagement.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T17:35:55Z"
---

# Send Engagement Letters With Approver Review

Have a partner approve an engagement letter before the client initials the fee clause and signs, and name the signed package after the matter.

_Last verified against API version 1.18.0._

A firm wants a partner to review every engagement letter before it reaches the client. Add the partner as an approver. The client only receives the letter after the partner approves it, then initials the fee clause and signs.

## Envelope shape

- **One PDF document.** The client has an `initials` place on the fee clause and a `signature` place. See [Initials](https://signatureapi.com/docs/api/resources/places/initials).
- **An approver and a signer.** The partner is an `approver` and has no places. The client is a `signer`. An approver can approve or reject. See [Approver](https://signatureapi.com/docs/api/resources/recipients/approver).
- **Named deliverable.** `deliverable.name` labels the signed package, so you can find it in your matter system. See [Standard deliverable](https://signatureapi.com/docs/api/resources/deliverables/standard).
- **Metadata and topics.** `metadata.matter_id` links the envelope to the matter. The `legal` and `engagement` topics group these envelopes. Keep client names and fee details out of `metadata`.

## Routing

The envelope uses `sequential` routing, which approvers need. The partner is first in the `recipients` array, so the client is notified only after the partner approves. See [Send to an approver](https://signatureapi.com/docs/api/guides/how-to/send-to-approver) and [Sequential signing](https://signatureapi.com/docs/api/guides/how-to/sequential-signing).

## Webhooks to listen for

- [`recipient.completed`](https://signatureapi.com/docs/api/resources/events/recipient-events): fires when the partner approves and again when the client signs. Use `recipient_key` and `envelope_metadata.matter_id` to update the matter.
- [`recipient.rejected`](https://signatureapi.com/docs/api/resources/events/recipient-events): the partner rejected the letter. Notify the responsible lawyer so they can revise it and send a new envelope.
- [`envelope.completed`](https://signatureapi.com/docs/api/resources/events/envelope-events): the client signed. Open the engagement in your matter system.
- [`deliverable.generated`](https://signatureapi.com/docs/api/resources/events/deliverable-events): the package named `engagement_letter_signed` is ready to download and file.

Set up the endpoint as shown in [Set up webhooks](https://signatureapi.com/docs/api/guides/how-to/set-up-webhooks).

## Compliance notes

This is general information, not legal advice. Professional conduct rules and the validity of electronic signatures on engagement letters vary by jurisdiction, so have your counsel or ethics advisers review your template and process. Webhook payloads include `metadata`, so use matter numbers and not confidential details.

### Example: Default

Engagement Letter (sample).

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

{
  "title": "Engagement Letter (sample)",
  "message": "Please review the engagement letter, initial the fee clause and sign.",
  "routing": "sequential",
  "metadata": {
    "matter_id": "mat_2209"
  },
  "topics": [
    "legal",
    "engagement"
  ],
  "deliverable": {
    "type": "standard",
    "name": "engagement_letter_signed"
  },
  "documents": [
    {
      "key": "engagement_letter",
      "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
      "format": "pdf",
      "fixed_positions": [
        {
          "place_key": "fee_clause_initials",
          "page": 1,
          "top": 250,
          "left": 72
        },
        {
          "place_key": "client_signature",
          "page": 1,
          "top": 172,
          "left": 210
        }
      ],
      "places": [
        {
          "key": "fee_clause_initials",
          "type": "initials",
          "recipient_key": "client",
          "height": 30
        },
        {
          "key": "client_signature",
          "type": "signature",
          "recipient_key": "client"
        }
      ]
    }
  ],
  "recipients": [
    {
      "type": "approver",
      "key": "partner",
      "name": "Alex Chen",
      "email": "alex.chen@example.com"
    },
    {
      "type": "signer",
      "key": "client",
      "name": "Jane Doe",
      "email": "jane.doe@example.com"
    }
  ]
}
```

Response 201 Created:

```json
{
  "id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
  "title": "Engagement Letter (sample)",
  "label": null,
  "message": "Please review the engagement letter, initial the fee clause and sign.",
  "status": "processing",
  "attestation": "none",
  "language": "en",
  "mode": "test",
  "routing": "sequential",
  "timezone": "UTC",
  "timestamp_format": "MM/DD/YYYY HH:mm:ss",
  "snapshot_url": null,
  "branding": {
    "logo": null,
    "accent_color": "#2463EB",
    "email": {
      "footer": null,
      "logo_position": "left",
      "from": "noreply@signatureapi.com"
    }
  },
  "deliverable": {
    "id": "del_HVl3Nj7XzTzX7jN3lVH5vn",
    "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
    "name": "engagement_letter_signed",
    "status": "pending",
    "type": "standard",
    "url": null,
    "password": null,
    "created_at": "2026-11-02T14:03:11.000Z",
    "generated_at": null,
    "timezone": "UTC",
    "language": "en",
    "timestamp_format": "MM/DD/YYYY HH:mm:ss",
    "included_documents": [
      "engagement_letter"
    ]
  },
  "metadata": {
    "matter_id": "mat_2209"
  },
  "sender": {
    "name": "Acme Corp Legal",
    "email": "legal@acme.example",
    "organization": "Acme Corp"
  },
  "captures": {},
  "documents": [
    {
      "id": "doc_HVl3Nj7XzTzX7jN3lVH5vn",
      "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
      "key": "engagement_letter",
      "title": null,
      "page_count": 1,
      "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
      "format": "pdf",
      "fixed_positions": [
        {
          "page": 1,
          "top": 250,
          "left": 72,
          "place_key": "fee_clause_initials"
        },
        {
          "page": 1,
          "top": 172,
          "left": 210,
          "place_key": "client_signature"
        }
      ],
      "places": [
        {
          "key": "fee_clause_initials",
          "type": "initials",
          "recipient_key": "client",
          "height": 30
        },
        {
          "key": "client_signature",
          "type": "signature",
          "recipient_key": "client",
          "height": 60
        }
      ]
    }
  ],
  "recipients": [
    {
      "id": "re_HVl3Nj7XzTzX7jN3lVH5vn",
      "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
      "type": "approver",
      "key": "partner",
      "email": "alex.chen@example.com",
      "name": "Alex Chen",
      "ceremony": {
        "authentication": [
          {
            "type": "email_link",
            "subject_override": null,
            "message_override": null
          }
        ],
        "embeddable_in": [],
        "redirect_url": null,
        "redirect_delay": 3,
        "url": null,
        "url_variant": "standard"
      },
      "ceremony_creation": "automatic",
      "delivery_type": "none",
      "status": "pending",
      "status_updated_at": "2026-11-02T14:03:11.000Z",
      "completed_at": null
    },
    {
      "id": "re_OcsAUqEe6a6eEqUAscOC2u",
      "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
      "type": "signer",
      "key": "client",
      "email": "jane.doe@example.com",
      "name": "Jane Doe",
      "ceremony": {
        "authentication": [
          {
            "type": "email_link",
            "subject_override": null,
            "message_override": null
          }
        ],
        "embeddable_in": [],
        "redirect_url": null,
        "redirect_delay": 3,
        "url": null,
        "url_variant": "standard"
      },
      "ceremony_creation": "automatic",
      "delivery_type": "email",
      "signature_options": [
        "typed",
        "drawn"
      ],
      "status": "awaiting",
      "status_updated_at": "2026-11-02T14:03:11.000Z",
      "completed_at": null
    }
  ],
  "topics": [
    "legal",
    "engagement"
  ],
  "created_at": "2026-11-02T14:03:11.000Z",
  "completed_at": null
}
```

Response 422 Unprocessable Content:

```json
{
  "type": "https://signatureapi.com/docs/v1/errors/validation-error",
  "title": "Validation Error",
  "status": 422,
  "detail": "The request body contains validation errors.",
  "errors": [
    "recipients[0].email must be a valid email address"
  ]
}
```

Errors that any request can return (authentication, rate limits, server errors) are on the [Errors](https://signatureapi.com/docs/api/errors) and [Authentication](https://signatureapi.com/docs/api/authentication) pages.
