type: integration

title: PDF Signing API

integration_name: PDF Signing API

kind: api

summary: Quickstart-first API guide for Adobe-trusted PDF sealing with HMAC authentication and CMS/PKCS 7 responses.

auth_model: HMAC header authentication

commands_or_endpoints: const res = await fetch("https://api.trusted-signatures.com/v1/sign", {

error_handling:
400: invalid body or headers
401: auth failure
403: request blocked
413: payload too large
500: server error

source_section: PDF Signing API

extracted_from: content

confidence: high


title: Trusted Signatures Publisher CLI

integration_name: Trusted Signatures Publisher CLI

kind: cli

summary: Quickstart-first CLI guide for sealing PDFs with Adobe-trusted signatures from CI/CD and scripts.

source_section: Trusted Signatures Publisher CLI


title: AWS Cloud Connector API Reference

integration_name: AWS Cloud Connector API Reference

summary: Endpoints, request shape, and process flow for sealing PDFs through the Trusted Signatures AWS Cloud Connector.

auth_model: API key ID plus API key

commands_or_endpoints: aws s3 cp document.pdf s3://your-source-bucket/uploads/document.pdf

commands_or_endpoints: aws s3 cp s3://your-destination-bucket/sealed/sealed-document.pdf sealed-document.pdf

commands_or_endpoints: aws s3 rm s3://your-source-bucket/uploads/document.pdf

commands_or_endpoints: aws s3 rm s3://your-destination-bucket/sealed/sealed-document.pdf

error_handling:
Invalid API key or credentials
Malformed PDF document
Network connectivity issues
Trusted Signatures API unavailable
S3 service errors

constraints: You are responsible for securing the API endpoint that fronts the AWS Cloud Connector.

source_section: AWS Cloud Connector API Reference


title: AWS Cloud Connector Deployment Guide

integration_name: AWS Cloud Connector Deployment Guide

summary: Deploy the Trusted Signatures AWS Cloud Connector as a Lambda-based sealing gateway in your own AWS account.

input_requirements: AWS Account with Lambda, S3, and API Gateway permissions

input_requirements: S3 buckets for PDF storage (source and destination)

input_requirements: Valid Trusted Signatures Container Gateway license

error_handling: Critical: Lambda processes PDFs in memory

error_handling: Allocate memory based on PDF size: PDF size × 4 = minimum Lambda memory

error_handling: Monitor CloudWatch metrics for memory usage

error_handling: Verify function returns proper JSON response

constraints: You are responsible for securing the AWS Cloud Connector.

source_section: AWS Cloud Connector Deployment Guide


title: AWS Cloud Connector

integration_name: AWS Cloud Connector

summary: Deploy the Trusted Signatures AWS Cloud Connector in your own account so PDFs stay in S3 while Lambda handles digesting, sealing, and sealed-PDF output.

source_section: AWS Cloud Connector


title: AWS Cloud Connector S3 Setup

integration_name: AWS Cloud Connector S3 Setup

summary: Configure S3 buckets, IAM permissions, and lifecycle controls for the Trusted Signatures AWS Cloud Connector.

commands_or_endpoints:
aws s3 mb s3://your-pdf-source-bucket
aws s3 mb s3://your-pdf-sealed-bucket
aws s3api put-bucket-encryption \
aws s3api put-bucket-logging \

error_handling: Verify Lambda execution role has correct S3 permissions

error_handling: Check bucket policies don't block Lambda access

error_handling: Increase Lambda timeout (max 15 minutes)

error_handling: Consider Lambda memory allocation for large files

error_handling: Set up lifecycle policies to delete temporary files

error_handling: Consider S3 Transfer Acceleration for large uploads

source_section: AWS Cloud Connector S3 Setup


title: AWS Secrets Manager Setup

integration_name: AWS Secrets Manager Setup

summary: Store Trusted Signatures API credentials securely in AWS Secrets Manager for applications that invoke the AWS Cloud Connector.

commands_or_endpoints:
aws secretsmanager create-secret \
aws cloudwatch put-metric-alarm \
aws cloudtrail lookup-events \
aws logs filter-log-events \

error_handling: Verify Lambda execution role has secretsmanager:GetSecretValue permission

error_handling: Check secret resource ARN matches policy

error_handling: Ensure secret exists in the correct region

error_handling: Confirm region matches Lambda function region

error_handling: Verify secret contains correct apiKey and apiKeyId

error_handling: Test credentials directly with Trusted Signatures API

source_section: AWS Secrets Manager Setup


title: Cloud Connector for Azure API Reference

integration_name: Cloud Connector for Azure API Reference

summary: API reference for direct PDF sealing and Blob Storage workflows through Cloud Connector for Azure.

source_section: Cloud Connector for Azure API Reference


title: Power Automate Guide for Cloud Connector for Azure

summary: End-to-end Power Automate setup for Cloud Connector for Azure, including account setup, Azure deployment, custom connector configuration, and OneDrive workflow sealing.

commands_or_endpoints: func azure functionapp publish ts-gateway-func


title: Cloud Connector for Azure Deployment Guide

summary: Deploy the Trusted Signatures Azure Function in your own subscription for direct PDF requests or Blob Storage-based sealing workflows.

commands_or_endpoints: curl -X POST https://.azurewebsites.net/api/seal-pdf \

constraints: IMPORTANT: You are responsible for securing the gateway in your environment.

constraints: The Function is deployed with anonymous HTTP access to work with Power Automate, but you should restrict access to only your authorized users.


title: Cloud Connector for Azure

integration_name: Cloud Connector for Azure

summary: Deploy the Trusted Signatures Azure Function in your own Azure subscription for direct PDF sealing, Blob Storage workflows, and Power Automate integration.

source_section: Cloud Connector for Azure


title: Cloud Connector for Azure Security Guide

summary: Security guidance for operating Cloud Connector for Azure with Key Vault, network controls, authentication, monitoring, and incident response.

commands_or_endpoints: az functionapp config access-restriction add \

commands_or_endpoints: az monitor app-insights component create \

commands_or_endpoints: az functionapp stop --name"your-function-app"--resource-group"your-rg"


title: GCP Cloud Connector API Reference

integration_name: GCP Cloud Connector API Reference

summary: API reference for direct PDF sealing and Cloud Storage workflows through the Trusted Signatures Cloud Function on GCP.

commands_or_endpoints: curl -X POST https://REGION-PROJECT_ID.cloudfunctions.net/pdf-sealer-gateway/seal \

commands_or_endpoints: gcloud functions logs read pdf-sealer-gateway \

error_handling: Solution: Verify request format and use appropriate mode for your PDF size.

error_handling: Solution: Verify Cloud Function service account has required Cloud Storage IAM roles.

error_handling: Solution: Verify the source bucket and key exist and are accessible.

error_handling: Solution: Check Cloud Logging for detailed error information.

error_handling: Solution: Retry the request with exponential backoff.

source_section: GCP Cloud Connector API Reference


title: GCP Cloud Connector Cloud Storage Setup

integration_name: GCP Cloud Connector Cloud Storage Setup

summary: Configure Google Cloud Storage, IAM, lifecycle rules, and service account access for the GCP Cloud Connector storage mode.

input_requirements: Google Cloud Project with billing enabled

commands_or_endpoints: gcloud iam service-accounts create pdf-sealer-function \

commands_or_endpoints: gcloud projects add-iam-policy-binding PROJECT_ID \

commands_or_endpoints: gcloud functions deploy pdf-sealer-gateway \

commands_or_endpoints: gcloud functions add-iam-policy-binding pdf-sealer-gateway \

commands_or_endpoints: gcloud logging sinks create storage-audit-sink \

commands_or_endpoints: gcloud alpha monitoring dashboards create --config-from-file=dashboard.json

source_section: GCP Cloud Connector Cloud Storage Setup


title: GCP Cloud Connector Deployment Guide

integration_name: GCP Cloud Connector Deployment Guide

summary: Deploy the Trusted Signatures Cloud Function on Google Cloud Platform with console, gcloud, Terraform, or Deployment Manager workflows.

input_requirements: Cloud Storage API enabled (for Storage Mode)

input_requirements: Built gcf-package.zip file (run npm run build)

commands_or_endpoints: gcloud functions describe pdf-sealer-gateway \

commands_or_endpoints: gcloud deployment-manager deployments create pdf-sealer-deployment \

commands_or_endpoints: gcloud functions remove-iam-policy-binding pdf-sealer-gateway \

error_handling: Ensure gcf-package.zip is properly built

error_handling: Increase timeout setting (max 540 seconds for 2nd gen)

error_handling: Check network connectivity to Trusted Signatures API

error_handling: For large PDFs, consider using Storage Mode

error_handling: Increase memory allocation (especially for Direct Mode)

error_handling: Monitor memory usage in Cloud Monitoring

error_handling: For Storage Mode: verify service account has Cloud Storage permissions

error_handling: Verify service account has storage.objectViewer and storage.objectCreator roles

error_handling: Check bucket names and file paths are correct

error_handling: Verify function is deployed with correct service account

error_handling: Check request format (cannot specify both modes)

error_handling: For Direct Mode: check PDF size limit (~32MB)

prerequisites: Google Cloud Project with billing enabled

source_section: GCP Cloud Connector Deployment Guide


title: GCP Cloud Connector

integration_name: GCP Cloud Connector

summary: Deploy the Trusted Signatures Cloud Function on Google Cloud Platform for direct PDF sealing or Cloud Storage-based document workflows.

source_section: GCP Cloud Connector


title: GCP Cloud Connector Security Guide

integration_name: GCP Cloud Connector Security Guide

summary: Security guidance for operating the GCP Cloud Connector with authenticated invocation, least-privilege IAM, secret handling, Cloud Storage controls, and monitoring.

source_section: GCP Cloud Connector Security Guide


title: Cloud Connector Docs

integration_name: Cloud Connector Docs

summary: Deployment and integration guides for customer-managed cloud connectors that keep PDF handling inside your infrastructure.

source_section: Cloud Connector Docs


title: Kubernetes Cloud Connector

integration_name: Kubernetes Cloud Connector

summary: Deploy the Trusted Signatures container gateway in Kubernetes or Docker for internal HTTP-based PDF sealing with health checks, scaling, and cluster-managed ingress.

source_section: Kubernetes Cloud Connector


title: Kubernetes Cloud Connector User Guide

integration_name: Kubernetes Cloud Connector User Guide

summary: User guide for running the Trusted Signatures container gateway locally with Docker or in Kubernetes, including API usage, health checks, and example manifests.

commands_or_endpoints: docker run -p 8080:8080 trustedsignatures/container-gateway:latest

commands_or_endpoints: const response = await fetch("http://localhost:8080/seal", {

commands_or_endpoints: response = requests.post('http://localhost:8080/seal', json={

commands_or_endpoints: curl -X POST http://localhost:8080/seal \

source_section: Kubernetes Cloud Connector User Guide


title: Documenso Integration

integration_name: Documenso Integration

kind: documenso

summary: Deploy the Trusted Signatures fork of Documenso with Adobe-trusted PDF sealing. Technical guide for developers.

input_requirements: Valid API key from your Trusted Signatures dashboard

error_handling: "Signing failed": Verify API key format (hexadecimal) and key ID are correct

error_handling: No seal applied: Check NEXT_PRIVATE_SIGNING_TRANSPORT=trusted-signatures is set

error_handling: Database errors: Ensure Documenso's standard database requirements are met

related_products:
Publisher Identity
Documenso Integration

source_section: Documenso Integration


title: Web sealing

integration_name: Web sealing

kind: integration

summary: Seal PDFs directly in your browser without uploading documents to Trusted Signatures servers. Use a test certificate, the Trusted Signatures certificate, or your organization certificate based on your subscription.

source_section: Web sealing


title: PDF Signing With Zapier

integration_name: PDF Signing With Zapier

summary: Automate PDF digital signing with Zapier integration. No-code workflows for Google Drive, Dropbox, forms. Get Adobe Acrobat blue seal.

input_requirements: Trusted Signatures account with API access

input_requirements: Basic Zapier knowledge (creating Zaps, connecting apps)

input_requirements: PDF source (Google Drive, form uploads, etc.)

error_handling: Verify signed PDF has blue seal in Adobe Acrobat

error_handling: Confirm output destination receives file

error_handling: Verify API Key ID and API Key are correct

error_handling: Ensure PDF file field is mapped correctly

source_section: PDF Signing With Zapier


title: Cloud Connector for Power Automate

integration_name: Cloud Connector for Power Automate

summary: Run sealing actions from Power Automate while PDFs stay inside your Azure cloud through your Cloud Connector for Azure deployment.

constraints: The Power Automate action sends the PDF and parameters to your Cloud Connector for Azure, so the document remains inside your cloud boundary.

related_products:
Cloud Connector for Power Automate
Publisher Identity

source_section: Cloud Connector for Power Automate