Automatically apply an electronic seal

The PDF Electronic SEAL API applies to tamper evident electronic seal to PDFs at scale using a cloud based third party digital certificate. An electronic seal is like an organization’s rubber stamp on paper, but its more secure electronic seals help verify the identity and integrity of official documents such as invoices and financial statements, thereby reducing risk in your organization by proving that the documents have not been tampered with. They also help ensure documents are legally compliant for various regulatory and legal workflows. There are many options for how the PDF Electronic SEAL API can be invoked, such as using a programing language with the rest API, or in our example here, we’re going to use power Automate Microsoft’s Low Code Automation solution to start, let’s create a new flow and power. Automate will select automated cloud flow and create a name. Your flow can be triggered by many different events, but for an easy example, let’s create a flow that is triggered by a new document being added to a SharePoint folder. The parameters highlighted here in red are the parameters that need to be customized in creating a workflow. Our flow here is triggered by a new document being added to a SharePoint folder. This is our source PDF that we want to apply the electronic seal to the process of calling the E seal from Power Automate is three steps. The first step is to make an HTP call to the TSP or the trust services provider to get an access token. So we’ll add an HTP action and the URI method and body should be populated from the information provided by your TSP header should also be set as shown here. Now the second step is to parse the returning JSON value using the parse JSON action here, the content variables should be populated with the output of the previous get access token step. The schema value should be set as shown here as well. Now the third step is to add an e fill PDF action. Here you’ll specify the input file name either from the file name from the trigger or a name of your choosing. The TSP credential ID and PIN will be provided by your TSP. The authorization token is populated from the access token variable output from the Pass Access Token action. The field name is the name of the digital signature field in the document to be easily the template file content is populated from the output or the trigger. When a file is created in a folder, then the last action takes our easy PDF and outputs it to another SharePoint folder. Let’s take a look at our input PDF before we run the flow. Here you can see that it looks like a standard PDF. However, how do you verify the source of this document and the authenticity of the content? By uploading this document to SharePoint, it triggers my flow. Now let’s take a look at the output document from the other SharePoint folder. Here you’ll see a new seal that has been applied to the document. It has a customizable logo as well as a timestamp, and when you open it in Acrobat, you can see the blue ribbon that signifies that this document has not been modified or tampered with since it was first sealed. So you can see how the PDF Electronic SEAL API can help verify the identity of the organization and demonstrate authenticity of content by making PDFs tamper evident at scale.