> For the complete documentation index, see [llms.txt](https://2sign-co-il.gitbook.io/2sign.co.il-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://2sign-co-il.gitbook.io/2sign.co.il-docs/getting-started/key-tips-and-differences.md).

# Key Tips & Differences

Use this page to choose the right task flow and field strategy.

* Use a **Single Task** for one signer.
* Use a **Signature Routine** for multiple signers.
* Use a **Template** when the document layout repeats.

***

### Single Task vs. Signature Routine

#### Single Task

Use a single task when one recipient signs the document.

You can send it to:

* an existing client by `ClientId`
* a one-time recipient by `ClientPhones` or `ClientEmails`

See [Create a single Task](/2sign.co.il-docs/tasks/create-a-single-task.md).

#### Signature Routine

Use a signature routine when multiple recipients sign the same document.

The flow supports both modes:

* `SignatureRoutineAsync: false` - sequential signing
* `SignatureRoutineAsync: true` - parallel signing

You can create a routine:

* with a predefined group and signer `ClientId` values
* without a group by sending signer phone or email values directly

See [Create a Signature Routine](/2sign.co.il-docs/signature-routine-tasks/create-a-signature-routine.md) and [Create a Signature Routine Without a Group](/2sign.co.il-docs/signature-routine-tasks/create-a-signature-routine-without-a-group.md).

{% hint style="info" %}
Use sequential mode when signer order matters. Use parallel mode when all signers can receive the document at the same time.
{% endhint %}

***

### Working with templates

Use a template when the document structure stays the same across tasks.

Templates help when:

* the same document is sent often
* fields should already exist on the document
* sender-side values should be pre-filled before sending

To reuse template field positions:

1. Call a template lookup endpoint from [Single task tamplates](/2sign.co.il-docs/templates/get-tamplates-info.md)
2. Copy the `SignaturePositions` array
3. Update `PositionTextContent` where needed
4. Send that array in the task creation request

{% hint style="info" %}
This is the fastest way to get accurate field positions. It avoids manual X/Y calculation.
{% endhint %}

#### Pre-fill sender-side fields

To render a value on the document before the signer opens it:

* set `SignaturePositionStageTypeId` to `1`
* set the field value in `PositionTextContent`

For the full field model, see [Defining Signature Fields](/2sign.co.il-docs/tasks/defining-signature-fields.md).

***

### Place fields with hidden characters

Use hidden characters when you want the system to place fields from markers embedded in the PDF.

#### One marker for signature fields

`SearchWordForMarkingSignature` places a signature field everywhere the marker appears.

```json
{
  "SearchWordForMarkingSignature": "§"
}
```

This method supports signature fields only.

#### Multiple markers for multiple field types

`SearchWordForMarkingFieldsJson` maps each marker to a field type.

```json
{
  "SearchWordForMarkingFieldsJson": "[{ \"fieldSignaturePositionType\": \"1\", \"fieldSearchChar\": \"&\" }, { \"fieldSignaturePositionType\": \"6\", \"fieldSearchChar\": \"$\" }]"
}
```

In this example:

* `&` creates a signature field
* `$` creates a full-name field

| Field                        | Description                         |
| ---------------------------- | ----------------------------------- |
| `fieldSignaturePositionType` | Field type ID                       |
| `fieldSearchChar`            | The marker embedded in the document |

{% hint style="warning" %}
Use rare characters like `§`, `¤`, or `¬`. Avoid common characters like `@`, `!`, and `%`.
{% endhint %}

For more field-placement options, see [Defining Signature Fields](/2sign.co.il-docs/tasks/defining-signature-fields.md).

***

### Notifications and signing link

Use these parameters to control delivery:

* `IsSendOnCreation`
* `IsSendEmailOnCreation`
* `IsSendSmsOnCreation`

Use `EmailText` to customize the email body.

SMS is sent to the recipient's `ClientPhones` value or stored mobile number.

You can also build a direct signing link from the returned `taskGuid`:

```
https://app.2sign.co.il/he/Clients/DocSignature?guid=<taskGuid>
```

You can send that link through email, WhatsApp, or another channel.

***

### Callbacks

Set a permanent callback URL to receive task status updates.

Configure it in **Subscription → Settings → Account Settings → Advanced Settings → Additional API Settings**.

Enter the full `https://` URL and save it.

The system sends a `POST` request whenever the task status changes.

***

### Create the document Signing URL

After creating a task via the API, the response includes a unique `TaskGuid`.

To generate the document signing URL, append the `TaskGuid` to the following URL:

```
https://app.2sign.co.il/he/Clients/DocSignature?guid={TaskGuid}
```

**Example:**

```
https://app.2sign.co.il/he/Clients/DocSignature?guid=c788c46d-7f64-48d9-94a0-7d0c3ee56301
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://2sign-co-il.gitbook.io/2sign.co.il-docs/getting-started/key-tips-and-differences.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.