Month: November 2018

Continuing with our mission to bring accurate, reliable and easy to use Doc Conversion API, and provide a single stop location for all your document operations, we have now released our new electronic signature feature.

This new Electronic Signature feature enables end users to electronically sign your PDF documents, allowing you to fully digitalize and automate your business process, and eliminate unnecessary time and costs. Electronic Signature also enhances the security of the entire business process and improves user experience and satisfaction.

At Doc Conversion API, we want to make all conversions and document operations as easy as possible, so we decided to save you the worry of having to have specific storage configuration, as you can use local files, or files stored on the cloud.

As we’ve explained how to use cloud storage files in previous blogs, this time we’re going to focus on using a local file in your conversion, so you can use your own files that are stored on your local computer.

Using the REST API Calls to Convert Local Files

This method is most suitable for backend conversion and processing of documents, if you have a recurring conversion type or want to convert a large number of files, and would like to automate your conversion process.

As explained in previous blog posts, you can use files stored on the cloud, or files with direct download URL, but in this example, we’re going to use a file that is stored on your local disk.

Since our servers will not have direct access to local storage, we need to send an array of bytes that contains all the information about the file to the end-point.

The first step would be to locate the file you would like to use, and get the full path of the file. For simplicity, we’re going to be a word document file called “sample” and stored in the documents folder, but you can use any file and store it anywhere you would like, as long as you’re able to specify the correct path. So the path for our file will be:/Users/MacBookPro/Documents/sample.doc

The file looks like this:

Now we have the file path, we can go ahead and use it in our code, below is a sample PHP code that will perform a simple doc to HTML conversion, create an HTML file, and return, “operation completed successfully” when the conversion is done.

Make sure to replace the path with the valid path to your file, and update your Application ID and Secret Key (you can get those from your Doc Conversion API dashboard).

After executing this code, you should now have a converted HTML file on your local disk. Our output for this example looks like this:

You can, of course, customize the code sample enough to fit your needs. More code examples can be found on our documentation page, and specific conversion examples can be found on our blog.
If you need any further help, please contact us at [email protected].

At Doc Conversion API, we want to make all conversions and document operations as easy as possible, so we decided to save you the worry of having to have specific storage configuration, as you can use a local file, or any files stored on the cloud.

As we’ve explained how to use cloud storage files in previous blogs, this time we’re going to focus on using a local file in your conversion, so you can use your own files that are stored on your local computer.

Using the Web App to Convert Local Files

If you’re looking to use an intuitive interface for a quick conversion, without the need to write code or test connections etc, then this is the right method for you, it’s quick, easy, and requires no configuration.

Login to your Doc Conversion API dashboard and click on Files.

From the Files, window click on File Import.

Select the file you’d like to convert and click on choose.

This will upload the file to your dashboard and add it to the file list.

To convert the file, click on the PDF icon under the convert tab.

This will create a new PDF file and add it to your file list.

You can now download the converted PDF file or use the HTML viewer to view or embed this file in your web page.