![\"Raymond](\"https:\/\/miro.medium.com\/v2\/resize:fill:88:88\/1*ldF-FsLonNyTUOmQ7cIV_g.jpeg\")
<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/a><\/p>\n <\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n Over the past few months, we\u2019ve been working to improve and expand the power of our SDKs and with the most recent update to our .NET SDK, we\u2019ve now completed the overhaul of all our supported platforms. These 4.x versions offer improved support for our REST APIs<\/a> and will be much more flexible than earlier versions. Let\u2019s cover the updates.<\/p>\n At a high level, the new SDKs offer better support for the asynchronous nature of our APIs. Previously, SDK methods \u2018hid\u2019 the async nature behind the scenes, which while perhaps simpler, meant that developers had less control over the process. Now SDK users can choose how they want to handle this aspect of their development.<\/p>\n Next, our Python SDK now has full support for all our released APIs. Previously, Python only supported a subset of the features.<\/p>\n Finally, asset deletion is now supported via the SDK. When your code uploads a document, for example, a Word doc that will be converted to PDF, Adobe keeps this file in a secure temporary storage system. While no one had access to this asset, it\u2019s understandable that you may wish to remove this asset as soon as the conversion is done. The REST API has supported this for some time, but now the SDKs do as well.<\/p>\n Let\u2019s take a look at how these new SDKs work. If you want to try these examples yourself, be sure to grab your own free credentials<\/a>.<\/p>\n We\u2019ll start with the simplest example, converting a Word document to PDF. For this demo, we\u2019ll make use of the Node SDK which can be installed via Ok, now let\u2019s look at the code. First, our imports:<\/p>\n The SDK has specific types based on the operation being used and you can see that above with Next, we set up our credentials by reading our values from the environment. These credentials are then passed to an instance of the Now we define our operation. In this simple case, we don\u2019t have to tweak any of the parameters, just supply the input. This is done using Finally, you can poll for the result, and if successful, stream down the bits:<\/p>\n All in all, fairly short and sweet for a simple use case. Here\u2019s the entire script, with a bit more logging in that provides additional feedback while it runs:<\/p>\n One of the largest benefits of the SDKs is that they enable greater performance by enabling you to chain one command after another. Imagine you wanted to convert the Word doc into a PDF and<\/em> add a password. Previously this would have required the SDK to:<\/p>\n Now the SDKs can simply refer to the output of a previous action by using the resulting asset as input for the next operation. Let\u2019s look at what\u2019s necessary for that.<\/p>\n First, we add in the required support for our password-protect action. This (and the following updates) all came from our docs which include updated instructions for the new SDKs: Protect PDF<\/a><\/p>\n In the code snippet above, we\u2019ve added: Now, let\u2019s begin our modification. The line that waited for the result of the Create PDF operation was:<\/p>\n Everything that follows is after that line. First, we\u2019ll specify the params for the operation, in this case, a hard coded password:<\/p>\n Next, we make our job, using the result asset from the CreatePDF job:<\/p>\n The remainder of the code is as before \u2014 poll the job, and when done, get the asset and stream it (note that we\u2019ve modified the file name):<\/p>\n And that\u2019s it. In theory, there is no limit to what you could chain. You could:<\/p>\n Here\u2019s the complete version of this script:<\/p>\n To get started, sign up for free credentials<\/a> and give the SDKs a try. If you\u2019re using a language not supported by the SDKs, or simply would rather use the APIs, peruse the API docs<\/a> for more information.<\/p>\n<\/div>\n![\"Adobe](\"https:\/\/miro.medium.com\/v2\/resize:fill:48:48\/1*riyFijvwTfGcWNf1guRNtg.png\")
<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n![\"\"](\"https:\/\/miro.medium.com\/v2\/resize:fit:640\/format:webp\/1*uFAYOoxdz4AN5cHcOnOCdw.png)
npm<\/code>:<\/p>\nCreatePDFJob<\/code> and CreatePDFResult<\/code>. FYI, the SDKs have full documentation as well of course. You can find the Node SDK docs here: https:\/\/opensource.adobe.com\/pdfservices-node-sdk-samples\/apidocs\/latest\/index.html<\/a><\/p>\nPDFServices<\/code> object.<\/p>\nfs<\/code> streams and defining our mime type. If you’ve ever found yourself Googling for the precise mime type of Office docs, you’ll appreciate having them baked into the SDK itself. We create the job and use submit<\/code> to get it running.<\/p>\n\n
ProtectPDFParams<\/code>, EncryptionAlgorithm<\/code>, ProtectPDFJob<\/code>, ProtectPDFResult<\/code>.<\/p>\n\n