> For the complete documentation index, see [llms.txt](https://docs.shadowcipher.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadowcipher.in/changelog/2026/2026-10-20-phase-2.md).

# Signing API, templates, e-Stamp merge and stock

20 October 2026

The biggest update yet: a public signing API for clients, templates, e-Stamp merging and counter-based stock.

### Signing API

* **OAuth 2.0 client credentials.** Clients get an access token with their Client ID and Client Secret.
* **Start a signing transaction** and get a signing link for the signer.
* **Encrypted, time-limited signing links.** Each link is tied to one transaction and checked on every open.
* **Signing sessions.** The signing page can only be reached through a valid signing link.
* **Client secrets are stored hashed.**
* **Encrypted requests.** Sensitive request data is encrypted between browser and server.

### Templates

* Sign from a template: the signer fills in the fields, the PDF is generated, then they sign.
* Ready-made **NDA** and **rent agreement** templates.
* Draft a template and save it as Word or PDF.

### Merge PDF with e-Stamp

* Merge the e-Stamp, franking or certificate page with the agreement into one PDF.

### Stock (counters)

* **Counter-based stock for each client.** Each allocation has a total, a used count and a validity period (valid from and valid to).
* Signing checks the client's available stock before it starts.

### Rate limits

* Requests are limited per IP address and per client, to protect the service.

### Improved

* Faster, simpler database access.
* API documentation page.

### Fixed

* Fixes to the simulator, templates and storage paths.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shadowcipher.in/changelog/2026/2026-10-20-phase-2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
