---
title: "Mixed Placeholders"
description: "A document mixes legacy signature placeholders with places. Use generic placeholders with places, or use only legacy signature placeholders."
canonical: "https://signatureapi.com/docs/v1/errors/mixed-placeholders"
source: "https://signatureapi.com/docs/v1/errors/mixed-placeholders.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T11:41:57Z"
---

# Mixed Placeholders

A document mixes legacy signature placeholders with places. Use generic placeholders with places, or use only legacy signature placeholders.

_Last verified against API version 1.18.0._

## What Happened

The document mixes legacy signature placeholders with the newer places system. A document must use one positioning approach or the other, not both.

![Left, rejected: a document with a legacy signature placeholder (client.signature) and a places list. Right, accepted: a document whose placeholder client\_signs\_here matches a place in the places list.](https://signatureapi.com/docs/v1/errors/images/mixed-placeholders.svg)

## Example response

```json 422 Unprocessable Content (application/problem+json)
{
  "type": "https://signatureapi.com/docs/v1/errors/mixed-placeholders",
  "title": "Mixed Placeholders",
  "status": 422,
  "detail": "Mixing signature placeholders and places is not allowed. Please convert your signature placeholders to generic placeholders or prevent the use of places with the current document."
}
```

## How to Fix

- Convert legacy signature placeholders (`[[key.signature]]`) to generic placeholders (`[[key]]`) and define each one as a place.
- Alternatively, remove the places from the document and use only legacy signature placeholders.
- See the [Placeholders](https://signatureapi.com/docs/api/resources/places/positioning#placeholders) documentation for details on the current placeholder format.

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