---
title: "Signature Places (Legacy)"
description: "Mark where each recipient signs with legacy [[key.signature]] placeholders, and convert them to signature place objects with page positions or placeholders."
canonical: "https://signatureapi.com/docs/api/resources/places/signature-legacy"
source: "https://signatureapi.com/docs/api/resources/places/signature-legacy.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T17:22:42Z"
---

# Signature Places (Legacy)

Mark where each recipient signs with legacy [[key.signature]] placeholders, and convert them to signature place objects with page positions or placeholders.

_Last verified against API version 1.18.0._

> **Deprecated:** If you call the API directly, use [places](https://signatureapi.com/docs/api/resources/places/object) instead: they are more flexible. Legacy signature places keep working and are still maintained.

Power Automate flows use the new places too, through the Add Place actions. See [places in Power Automate](https://signatureapi.com/docs/integrations/power-automate/places/place).

Each recipient has a key that identifies them within an envelope. In an employment contract, for example, the keys can be `manager` and `employee`.

SignatureAPI uses placeholders to identify where each signature should go in a document. It uses the recipient's key to find their signing place.

The format of a signature placeholder is like this `[[key.signature]]`, where **key** is the recipient's key.

For example, in an employment contract, the place where the manager signs is marked:

`[[manager.signature]]`

and where the employee signs, is marked:

`[[employee.signature]]`

In the document, placeholders will look like this:

![Signature block of an agreement with the placeholder manager.signature above the manager's signature line and employee.signature above the employee's](https://signatureapi.com/docs/images/template-placeholders.webp)

After signing, the document will look like this:

![The same signature block after signing: each signature is drawn over its placeholder text](https://signatureapi.com/docs/images/template-placeholders-signatures.webp)

We recommend changing the placeholder text color to white. This will make the placeholders invisible in the document:

![The signed signature block with white placeholder text: only the two signatures are visible above the signature lines](https://signatureapi.com/docs/images/template-white-placeholders-signatures.webp)

If you need help with your templates, reach out to support.

## Converting to signature places

A document can't mix both kinds: when it contains a legacy `[[key.signature]]` placeholder and the document also defines `places`, the API returns a [mixed-placeholders](https://signatureapi.com/docs/v1/errors/mixed-placeholders) error. Convert all legacy placeholders in a document at once. Legacy placeholders also work only when every recipient signs: an envelope with a preparer or an approver returns an [unsupported-recipient-type](https://signatureapi.com/docs/v1/errors/unsupported-recipient-type) error.

Replace each legacy placeholder in your document file with the new one, then add the places to the document object. Without `height`, a signature place is 60 points tall and 150 points wide.

**Interactive tool: Legacy signature place migrator.** Paste document text with legacy `[[key.signature]]` placeholders and get signature place objects plus the new placeholders to type into the document. Use it on [the docs page](https://signatureapi.com/docs/api/resources/places/signature-legacy).

Placeholders to replace in the document:

| Legacy placeholder | New placeholder |
|---|---|
| `[[manager.signature]]` | `[[manager_signature]]` |
| `[[employee.signature]]` | `[[employee_signature]]` |

Places for the document object:

```json
{
  "places": [
    {
      "key": "manager_signature",
      "type": "signature",
      "recipient_key": "manager"
    },
    {
      "key": "employee_signature",
      "type": "signature",
      "recipient_key": "employee"
    }
  ]
}
```

A document uses either legacy placeholders or places, never both. Power Automate supports only legacy signature places.
