> For the complete documentation index, see [llms.txt](https://docs.emudhradigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emudhradigital.com/documentation/remote-signing-document-signer/integration-and-api.md).

# Integration and API

Applications integrate with Remote Signing through REST APIs over HTTPS, or through the eMudhra SDK (Java, .NET) which handles hashing, batching and signature embedding.

## Authentication

* API client credentials issued per application
* Mutual TLS (client certificate) recommended for production
* Source IP allow-listing

## Typical API operations

| Operation                  | Purpose                                                                                                  |
| -------------------------- | -------------------------------------------------------------------------------------------------------- |
| Sign hash(es)              | Submit up to 10 SHA-256 hashes with a signer profile; receive CMS/raw signatures and signer certificate. |
| Sign PDF                   | Submit a PDF with appearance parameters; receive the signed PDF.                                         |
| Get certificate            | Retrieve the signer certificate and chain for a profile.                                                 |
| Transaction status / audit | Look up a past signing transaction by reference.                                                         |

### Example — sign hashes (illustrative)

```http
POST /remotesign/v1/sign/hash
Content-Type: application/json
Authorization: Bearer <token>

{
  "signerProfile": "STATEMENTS-2026",
  "hashAlgorithm": "SHA256",
  "signatureType": "PKCS7PDF",
  "timestamp": true,
  "hashes": [
    { "id": "1", "value": "a3f5…9c", "reference": "STMT-0001" },
    { "id": "2", "value": "7b21…4e", "reference": "STMT-0002" }
  ]
}
```

```json
{
  "status": "SUCCESS",
  "transactionId": "RS-20261012-55821",
  "certificate": "MIIF…",
  "signatures": [
    { "id": "1", "value": "MIAG…", "status": "SUCCESS" },
    { "id": "2", "value": "MIAG…", "status": "SUCCESS" }
  ]
}
```

{% hint style="warning" %}
**Review before publishing:** endpoint paths, field names and auth scheme above are illustrative placeholders. Replace with the actual eMudhra Remote Signing API contract (or link the OpenAPI spec in the API Reference section).
{% endhint %}

## Integration checklist

1. Obtain UAT credentials and a test Document Signer certificate.
2. Prepare PDF signature placeholders (hash mode) or appearance templates (PDF mode).
3. Implement retries with idempotent `reference` values.
4. Validate output in Adobe Acrobat and with the [Validation Tool](file:///0255771/Signature-Validation/Validation%20Tool%20Overview.md).
5. Move to production credentials and certificate.