Cloud Connector for Azure API Reference
API reference for direct PDF sealing and Blob Storage workflows through Cloud Connector for Azure.
- Direct mode up to 50 MB
- Blob Storage mode
- Power Automate compatible
Azure proof
Use Azure Functions and Blob workflows for fast integration with enterprise controls
The documented Azure pattern combines Azure Functions, direct and Blob Storage modes, and Microsoft-native security controls so teams can support application and Power Automate workflows inside their own subscription.
50 MB
speed path
Direct mode supports request-body PDF sealing for documents up to 50 MB when teams want a simple application call path.
Blob
scale model
Blob Storage mode supports larger files and reusable storage-based workflows, including Power Automate-driven handoff.
AAD
security controls
The docs cover Key Vault, Azure AD, API Management, IP restrictions, and network controls for production rollout.
Digest
data boundary
The Function computes the digest locally and only the signing digest leaves your Azure environment.
API Reference
Overview
Cloud Connector for Azure provides businesses with a scalable, cost-effective API in their own infrastructure to seal even the most sensitive documents. By deploying the connector in their own Azure subscription, customers have assurance that none of the information in the documents can be intercepted or modified.
The Azure connector is deployed as an Azure Function. Customers send a PDF to sign with an API key and some parameters, and the function returns a sealed PDF.
Direct Mode and Storage Mode
Cloud Connector for Azure provides two modes of operation:
- Direct Mode: Send PDF content directly in the request (up to 50MB)
- Storage Mode: Process large files via Azure Blob Storage (unlimited size)
Architecture Overview
Process Flow - Direct Mode
Process Flow - Storage Mode
Authentication
All requests require valid Trusted Signatures API credentials:
- API Key: Hex-encoded string from https://secure.trusted-signatures.com
- API Key ID: Your unique key identifier
Endpoints
POST /api/seal-pdf
Seals a PDF document with a digital signature.
Direct Mode Request
| |
Storage Mode Request
| |
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
pdf | string | Conditional | Base64-encoded PDF (required for direct mode) |
sourceContainer | string | Conditional | Azure Blob container name (required for storage mode) |
sourceBlob | string | Conditional | Azure Blob name (required for storage mode) |
destinationContainer | string | Optional | Output container (defaults to sourceContainer) |
destinationBlob | string | Optional | Output blob name (defaults to “sealed-{sourceBlob}”) |
apiKey | string | Yes | Hex-encoded API key |
apiKeyId | string | Yes | API key identifier |
endpoint | string | No | API endpoint (default: https://api.trusted-signatures.com) |
tsaTimestamp | boolean | No | Include timestamp (default: false) |
includeLtv | boolean | No | Include long-term validation data (default: false) |
limitChanges | string | No | Document modification permissions |
limitChanges Values
no-changes: No modifications allowedallow-forms: Allow form filling onlyallow-comments: Allow form filling and annotations
Direct Mode Response
Success (200):
| |
Storage Mode Response
Success (200):
| |
Error Response
Error (400/500):
| |
GET /api/health
Health check endpoint for monitoring.
Response (200):
| |
Size Limits
- Direct Mode: 50MB maximum PDF size
- Storage Mode: No size limit (limited by Azure Blob Storage)
Error Codes
| Status | Description |
|---|---|
| 200 | Success |
| 400 | Bad Request (validation error, invalid PDF, etc.) |
| 401 | Unauthorized (invalid API key) |
| 413 | Payload Too Large (>50MB in direct mode) |
| 500 | Internal Server Error |
Rate Limits
Rate limits are enforced by the Trusted Signatures API service. Contact support for current limits.
Code Examples
Python - Direct Mode
| |
Python - Storage Mode
| |
TypeScript - Direct Mode
| |
TypeScript - Storage Mode
| |
Bash - Direct Mode
| |
Bash - Storage Mode
| |
PowerShell - Direct Mode
| |
PowerShell - Storage Mode
| |
Security Considerations
- Store API keys in Azure Key Vault, not in code
- Use managed identities for Azure resource access
- Rotate API keys annually (maximum lifetime: 1 year)
- Restrict network access using Azure networking features
- Monitor API usage through Application Insights
- Use HTTPS only (enforced by default)
Need architectural review?
Book a technical walkthrough
For enterprise rollout, we can review trust model, controls, and integration patterns with your team.