--- title: "Managing Signature Placeholders" slug: "managing-signature-placeholders" updated: 2026-11-05T19:41:27Z published: 2026-11-05T19:41:27Z canonical: "docs.onespan.com/managing-signature-placeholders" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Managing Signature Placeholders [Java SDK](/v1/docs/managing-signature-placeholders#java-sdk) [.NET SDK](/v1/docs/managing-signature-placeholders#net-sdk) [REST API](/v1/docs/managing-signature-placeholders#rest-api) [APEX SDK](/v1/docs/managing-signature-placeholders#apex-sdk) ## Java SDK To download the full code sample see our [Code Share](https://community.onespan.com/documentation/onespan-sign/codeshare/placeholders-management-java-sdk/) site. A signature placeholder is useful if the identity of a signer will be determined at a later time. For example, when building a template. A placeholder can be assigned to a signature field just as if you were assigning a regular signer. However, all placeholders must be replaced by real signers before the transaction is distributed for signing. Because a signature placeholder has no email address, they are identified by an ID. You can assign an authentication method to a placeholder. The method applies wherever the placeholder is used, so every transaction built from it gets the same identity checks without extra setup. Senders can still override the method for a specific recipient when needed. Placeholder authentication can be configured from the web UI, the API, and the SDKs. **NOTE:** To use SDKs you must [upgrade to the latest available](/v1/docs/downloading-sdks#downloading-the-latest-sdk-11-version) version. To enable this feature, contact our [Support Team](https://www.onespan.com/support). - Bulk Send: A new transaction-level setting, Enforce bulk send authentication, controls how placeholder authentication applies during [Bulk Send](/v1/docs/bulk-sending). To enable it, contact our [Support Team](https://www.onespan.com/support). - Not enforced (default): The authentication details in the Bulk Send CSV take priority over the method defined on the placeholder. - Enforced: The authentication method in the CSV must match the method defined on the placeholder. If it doesn't match, an error appears when you upload the CSV, and you must correct the file before you can continue. Authentication details in the CSV, such as phone numbers or question-and-answer values, are still used. - Limitations: Identity Verification isn't supported as a placeholder authentication method. [Fast Track](/v1/docs/fast-track) ignores placeholder authentication. When a template is used through Fast Track, authentication for placeholder recipients is reset to None. ### Adding a Signature Placeholder to a Template To add a signature placeholder to a template, you must first create the Placeholder object. The following code will create a Placeholder object: ```java Placeholder placeholder = new Placeholder("Manager"); ``` Once the Placeholder object has been created, use the OneSpan Sign TemplateService to add your signature placeholder to your template and pass the templateId and placeholder as parameters. The following code will do this: ```java Placeholder addedPlaceholder = eslClient.getTemplateService().addPlaceholder(templateId, placeholder); ``` ### Updating a Signature Placeholder To update an existing signature placeholder use the following code: ```java addedPlaceholder.setName("Client"); Placeholder updatedPlaceholder = eslClient.getTemplateService().updatePlaceholder(templateId, addedPlaceholder); ``` ### Deleting a Signature Placeholder Finally, deleting a signature placeholder is done using the PackageService. You will need to pass the templateId object, and placeholder id String as parameters. ```java eslClient.getPackageService().removePLACEHOLDER(templateId, addedPlaceholder.getId()); ``` ## .NET SDK To download the full code sample see our [Code Share](https://community.onespan.com/documentation/onespan-sign/codeshare/placeholders-management-net-sdk/) site. A signature placeholder is useful if the identity of a signer will be determined at a later time. For example, when building a template. A placeholder can be assigned to a signature field just as if you were assigning a regular signer. However, all placeholders must be replaced by real signers before the transaction is distributed for signing. Because a signature placeholder has no email address, they are identified by an ID. You can assign an authentication method to a placeholder. The method applies wherever the placeholder is used, so every transaction built from it gets the same identity checks without extra setup. Senders can still override the method for a specific recipient when needed. Placeholder authentication can be configured from the web UI, the API, and the SDKs. **NOTE:** To use SDKs you must [upgrade to the latest available](/v1/docs/downloading-sdks#downloading-the-latest-sdk-11-version) version. To enable this feature, contact our [Support Team](https://www.onespan.com/support). - Bulk Send: A new transaction-level setting, Enforce bulk send authentication, controls how placeholder authentication applies during [Bulk Send](/v1/docs/bulk-sending). To enable it, contact our [Support Team](https://www.onespan.com/support). - Not enforced (default): The authentication details in the Bulk Send CSV take priority over the method defined on the placeholder. - Enforced: The authentication method in the CSV must match the method defined on the placeholder. If it doesn't match, an error appears when you upload the CSV, and you must correct the file before you can continue. Authentication details in the CSV, such as phone numbers or question-and-answer values, are still used. - Limitations: Identity Verification isn't supported as a placeholder authentication method. [Fast Track](/v1/docs/fast-track) ignores placeholder authentication. When a template is used through Fast Track, authentication for placeholder recipients is reset to None. ### Adding a Signature Placeholder to a Template To add a signature placeholder to a template, you must first create the Placeholder object. The following code will create a Placeholder object: ```csharp Placeholder placeholder = new Placeholder("Manager"); ``` Once the Placeholder object has been created, use the OneSpan Sign TemplateService to add your signature placeholder to your template and pass the templateId and placeholder as parameters. The following code will do this: ```csharp Placeholder addedPlaceholder = eslClient.TemplateService.AddPlaceholder(templateId, placeholder); ``` ### Updating a Signature Placeholder To update an existing signature placeholder use the following code: ```csharp addedPlaceholder.Name = "Client"; Placeholder updatedPlaceholder = eslClient.TemplateService.UpdatePlaceholder(templateId, addedPlaceholder); ``` ### Deleting a Signature Placeholder Finally, deleting a signature placeholder is done using the PackageService. You will need to pass the templateId object, and placeholder id String as parameters. ```csharp eslClient.PackageService.RemovePLACEHOLDER(templateId, addedPlaceholder.Id); ``` ## REST API To download the full code sample see our [Code Share](https://community.onespan.com/documentation/onespan-sign/codeshare/placeholders-management-rest-api/) site. A signature placeholder is useful if the identity of a signer will be determined at a later time. For example, when building a template. A placeholder can be assigned to a signature field just as if you were assigning a regular signer. However, all placeholders must be replaced by real signers before the transaction is distributed for signing. Because a signature placeholder has no email address, they are identified by an ID. You can assign an authentication method to a placeholder. The method applies wherever the placeholder is used, so every transaction built from it gets the same identity checks without extra setup. Senders can still override the method for a specific recipient when needed. Placeholder authentication can be configured from the web UI, the API, and the SDKs. **NOTE:** To use SDKs you must [upgrade to the latest available](/v1/docs/downloading-sdks#downloading-the-latest-sdk-11-version) version. To enable this feature, contact our [Support Team](https://www.onespan.com/support). - Bulk Send: A new transaction-level setting, Enforce bulk send authentication, controls how placeholder authentication applies during [Bulk Send](/v1/docs/bulk-sending). To enable it, contact our [Support Team](https://www.onespan.com/support). - Not enforced (default): The authentication details in the Bulk Send CSV take priority over the method defined on the placeholder. - Enforced: The authentication method in the CSV must match the method defined on the placeholder. If it doesn't match, an error appears when you upload the CSV, and you must correct the file before you can continue. Authentication details in the CSV, such as phone numbers or question-and-answer values, are still used. - Limitations: Identity Verification isn't supported as a placeholder authentication method. [Fast Track](/v1/docs/fast-track) ignores placeholder authentication. When a template is used through Fast Track, authentication for placeholder recipients is reset to None. ### Adding a Placeholder to a Template To add a signature placeholder to a template, use the following code: #### HTTP Request ```http POST /api/packages/{templateId}/roles ``` #### HTTP Headers ```http Accept: application/json   Content-Type: application/json   Authorization: Basic api_key ``` #### Request Payload ```json {   "id": "Manager",   "type": "PLACEHOLDER",   "index": 0,   "name": "Manager"   } ``` For a complete description of each field, see the Request Payload table below. #### Response Payload ```json {    "id": "Manager",    "type": "PLACEHOLDER",    "index": 0,    "name": "Manager" } ``` ### Updating a Signature Placeholder Updating a placeholder is also done in a similar fashion. You will need to build the JSON with the updates you wish to make: #### HTTP Request ```http PUT /api/packages/{templateId}/roles/[roleId} ``` #### HTTP Headers ```http Accept: application/json   Content-Type: application/json   Authorization: Basic api_key ``` #### Request Payload ```http {    "id": "Manager",    "type": "PLACEHOLDER",    "index": 0,    "name": "Manager" } ``` #### Response Payload ```http {    "id": "Manager",    "data": null,    "emailMessage": null,    "attachmentRequirements": [],    "locked": false,    "reassign": false,    "specialTypes": [],    "type": "PLACEHOLDER",    "index": 0,    "PLACEHOLDER": [],    "name": "Manager" } ``` ### Deleting a Signature Placeholder Finally, to delete a placeholder: #### HTTP Request ```http DELETE /api/packages/{templateId}/roles/{roleId} ``` #### HTTP Headers ```http Accept: application/json   Content-Type: application/json   Authorization: Basic api_key ``` ### Request Payload Table | Property | Type | Editable | Required | Default | Sample Values | | --- | --- | --- | --- | --- | --- | | name | string | Yes | No | n/a | Manager | | id | string | Yes | No | n/a | Manager | | type | stringer | Yes | No | PLACEHOLDER | PLACEHOLDER/ SENDER | | name | string | Yes | No | n/a | Manager | ## APEX SDK To download the full code sample see our [Code Share](https://community.onespan.com/documentation/onespan-sign/codeshare/placeholders-management-apex-sdk/) site. A signature placeholder is useful if the identity of a signer will be determined at a later time. For example, when building a template. A placeholder can be assigned to a signature field just as if you were assigning a regular signer. However, all placeholders must be replaced by real signers before the transaction is distributed for signing. Because a signature placeholder has no email address, they are identified by an ID. You can assign an authentication method to a placeholder. The method applies wherever the placeholder is used, so every transaction built from it gets the same identity checks without extra setup. Senders can still override the method for a specific recipient when needed. Placeholder authentication can be configured from the web UI, the API, and the SDKs. **NOTE:** To use SDKs you must [upgrade to the latest available](/v1/docs/downloading-sdks#downloading-the-latest-sdk-11-version) version. To enable this feature, contact our [Support Team](https://www.onespan.com/support). - Bulk Send: A new transaction-level setting, Enforce bulk send authentication, controls how placeholder authentication applies during [Bulk Send](/v1/docs/bulk-sending). To enable it, contact our [Support Team](https://www.onespan.com/support). - Not enforced (default): The authentication details in the Bulk Send CSV take priority over the method defined on the placeholder. - Enforced: The authentication method in the CSV must match the method defined on the placeholder. If it doesn't match, an error appears when you upload the CSV, and you must correct the file before you can continue. Authentication details in the CSV, such as phone numbers or question-and-answer values, are still used. - Limitations: Identity Verification isn't supported as a placeholder authentication method. [Fast Track](/v1/docs/fast-track) ignores placeholder authentication. When a template is used through Fast Track, authentication for placeholder recipients is reset to None. ### Adding a Signature Placeholder to a Template To add a placeholder in a template, you will first need to create your Role object. The following code will do this: ```plaintext String placeholderId = 'placeholder1'; ESignLiveAPIObjects.Role placeholder1 = new ESignLiveAPIObjects.Role(); placeholder1.id = placeholderId; placeholder1.name = placeholderId; ``` Once you have built your Placeholder object, use the sdk.helper to add your signature placeholder to your template and pass the templateId and placeholder as parameters. The following code will do this: ```plaintext sdk.helper.createRole('E-_tmDsICwCkM2vqFuzVxF7NVQQ=', placeholder1); ``` ### Updating a Signature Placeholder To update an existing signature placeholder use the following code: ```plaintext sdk.helper.updateRole('E-_tmDsICwCkM2vqFuzVxF7NVQQ=','Manager', placeholder1); ``` ### Deleting a Signature Placeholder Finally, deleting a signature placeholder is also done using the sdk.helper. You will need to pass the templateId object, and placeholder id String as parameters. ```plaintext sdk.helper.deleteRole('E-_tmDsICwCkM2vqFuzVxF7NVQQ=','Manager'); ```