We just pushed the official Python API Wrapper to Github. Using it you can do cool stuff with just a few lines of code:
import cloudconvert
api = cloudconvert.Api('your_api_key')
process = api.convert({
'inputformat': 'html',
'outputformat': 'pdf',
'input': 'upload',
'file': open('input.html', 'rb')
})
process.wait()
process.download("output.pdf")
As always, you can create ready to use code snippets using the API console.
When creating PDF files from DOCX or PPTX files CloudConvert can now dynamically change the content. This feature makes it more convenient to create invoices or mass letters dynamically. Technically you set up a DOCX template with placeholders (for example ${name}). While converting the DOCX file to PDF CloudConvert can replace these placeholders with custom values. This even works for tables with a variable amount of rows as the following example shows.
The shown PDF was created using the DOCX template file and these few lines of PHP code:
$api->convert([
"input" => "upload",
"inputformat" => "docx",
"outputformat" => "pdf",
"converteroptions" => [
"templating" => [
"name" => "John Smith",
"address" => "Smithstreet 1",
"city" => "Smithtown",
"zip" => "10101",
"country" => "US",
"comment" => "Thanks for your business!",
"date" => "2015-11-24",
"total" => "160",
"items" => [
["description" => "Nameless product", "price" => "10", "quantity" => "2", "total" => "20"],
["description" => "Other product", "price" => "100", "quantity" => "1", "total" => "100"],
["description" => "Stuff", "price" => "2", "quantity" => "20", "total" => "40"],
],
],
],
"file" => fopen('template.docx', 'r'),
])
Checkout the full Syntax for the placeholders of the new templating feature.
We think this feature is a great step to make CloudConvert even more powerful and we hope you like it!
The syntax is highly inspired by Mustache. The template is created in Microsoft Word/PowerPoint or any equivalent that saves to DOCX/PPTX. Also checkout this example of using the templating feature.
A typical DOCX template:
Hello {name} !
Given the following value for the templating JSON dictionary:
{ name:'Edgar'}
Will produce:
Hello Edgar !
Like Mustache, it has the loopopening {#} and loopclosing {/} brackets
The following template:
{#products} {name}, {price} € {/products}
Given the following JSON dictionary:
{ "products": [ {name:"Windows",price:100}, {name:"Mac OSX",price:200}, {name:"Ubuntu",price:0} ] }
will result in :
Windows, 100 € Mac OSX, 200 € Ubuntu, 0 €
The loop behaves in the following way:
Note: Because the loops work also with boolean values, you can also use them for conditions.
Sometimes, you would like to insert your custom XML (a complex table, a formula, ...)
With the RawXML syntax the variable is interpreted as XML and replaced in the formula
{@rawXML}
with this data:
{rawXml:'<w:p><w:pPr><w:rPr><w:color w:val="FF0000"/></w:rPr></w:pPr><w:r><w:rPr><w:color w:val="FF0000"/></w:rPr><w:t>My custom</w:t></w:r><w:r><w:rPr><w:color w:val="00FF00"/></w:rPr><w:t>XML</w:t></w:r></w:p>'}
This will loop over the first parent tag
An inverted section begins with a caret (hat) and ends with a slash. That is {^person} begins a "person" inverted section while {/person} ends it.
While sections can be used to render text one or more times based on the value of the key, inverted sections may render text once based on the inverse value of the key. That is, they will be rendered if the key doesn't exist, is false, or is an empty list.
Template:
{#repo} <b>{name}</b> {/repo} {^repo} No repos 🙁 {/repo}
Value for the templating JSON dictionary:
{ "repo": [] }
Output:
No repos :(
We think in times of cloud computing you cannot categorize payments in fixed packages. We do not want to force our customers in buying or subscribing for 1000, 5000, or 10000 conversion minutes. From now on our customers can completely customize their prepaid packages and subscriptions and scale them according to their needs. If you want to subscribe for monthly 2222 conversion minutes, you can do so! Checkout our pricing site with the new sliders for your personal customization.
We are happy to announce another awesome CloudConvert enhancement! CloudConvert Folder Monitoring is a powerful feature to make your workflow even more efficient. You can set up special folders in your Google Drive or Dropbox account as Triggers. Every time you add a file to this folder it is automatically converted to a chosen output format with your customized options.
There are uncountable cool use cases for this feature:
Folder Monitoring is available as Beta feature for our paying users (prepaid package or subscription), starting today!
There is a great simplification for our long-term customers, especially our API users: By buying a prepaid package, you can now select the new "Auto Refill" option. This option makes sure the package is automatically refilled, if your quota of conversion minutes is used up to 95%.
If you have set up this once, you won't need to worry any more about your account is running out of quota and your API implementations might stop working. We hope you like it!