---
title: "Unsupported Recipient Type"
description: "Legacy signature placeholders only work for signers, but the envelope has another recipient type. Make that recipient a signer or use generic placeholders."
canonical: "https://signatureapi.com/docs/v1/errors/unsupported-recipient-type"
source: "https://signatureapi.com/docs/v1/errors/unsupported-recipient-type.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T11:41:57Z"
---

# Unsupported Recipient Type

Legacy signature placeholders only work for signers, but the envelope has another recipient type. Make that recipient a signer or use generic placeholders.

_Last verified against API version 1.18.0._

## What Happened

Legacy signature placeholders only work with recipients of type `signer`. The document uses legacy signature placeholders, but the envelope has a recipient of a different type.

> **Tip:** The response includes a `detail` property with more information about this error.

## Example response

```json 422 Unprocessable Content (application/problem+json)
{
  "type": "https://signatureapi.com/docs/v1/errors/unsupported-recipient-type",
  "title": "Unsupported Recipient Type",
  "status": 422,
  "detail": "Legacy signature placeholders are only supported for recipients of type 'signer'. Please update the recipient type or upgrade your signature placeholders to generic placeholders. Read more at https://signatureapi.com/docs/api/resources/places/positioning#placeholders."
}
```

## How to Fix

- Update the recipient type to `signer` if they need to sign using legacy placeholders.
- Alternatively, upgrade to generic [placeholders](https://signatureapi.com/docs/api/resources/places/positioning#placeholders), which support all recipient types.

Still stuck? [Contact support](https://signatureapi.com/support).
