Improved Aspose.Words Cloud V4 is Here!

Share on FacebookTweet about this on TwitterShare on LinkedIn

We’re excited to release new version of Aspose.Words Cloud REST API. Aspose.Words Cloud 19.4 includes lots of improvements related to features already supported by the API along with some breaking changes. Read on to see what’s new.

The major change in this release is introduction of V4 API version, it has more improved and optimized architecture. According to HTTP/1.1 specifications, we have changed PUT methods to POST and vice versa in this release. Now, all idempotent methods are PUT and non-idempotent methods are POST. In this release, we have included storage APIs in Aspose.Words Cloud REST API. Now you can perform different storage related operations directly, without using a separate Cloud API for the purpose. Learn more.

Breaking Changes

  • Introduced API version V4
  • Changed PUT to POST (and vice versa): from now on, all idempotent methods are PUT and non-idempotent ones are POST
  • “destFileName” parameter: now it contains absolute (instead of relative) path to save result file
  • Fixed serialization of “SourceFormat” property in “Document” response
  • “nodepath” parameter is always “path” type now
  • Removed “envelop” from all responses

New Features and Improvements

  • Storage APIs from now on are included in Aspose.Words Cloud REST API for a better user experience and unification
    • File API – Methods for upload, download, copy, move, delete files: input documents and rendering results, in the cloud storage
    • Folder API – Methods for create, copy, move, delete folders in the cloud storage
  • Improved recognition for multi-line headers and footers in PDF to Word Conversion API
  • Fixed an error in PDF to Word Conversion API while several documents are processed in parallel

How it Works

Here we demonstrate how easily you can convert a PDF document to DOCX using newest release. We will exhibit changes between V4 and V1 in this example for clear understanding by following these steps:

  • Get Access token for authentication
  • Upload Source PDF document to Storage
  • Convert PDF to DOCX

We are using cURL for consuming REST APIs in the example. You can use available SDKs to use the API directly in your favorite platform with ease.

Aspose.Words Cloud V1.1

Aspose.Words Cloud V4

Please note now V4 version only supports JWT(Json Web Token) for authentication, you cannot use URL signing and OAuth2 authentication methods with new version. Secondly, in V4 example, File API method of Aspose.Words Cloud is used to upload source file instead of Aspose.Storage Cloud API. And lastly but not least request type is changed to PUT in V4 instead of POST.

Share Your Feedback

Feel free to drop us a comment sharing your thoughts about the new version of Aspose.Words Cloud REST API. Or let us know if you have any suggestions or if you need any particular features which you expect our REST API to have.

And if you have not already had a chance to try our REST API, simply start a free trial today. All you need is to sign up with the aspose.cloud. Once you have signed up, you are ready to try the powerful file processing features offered by aspose.cloud.

Posted in Aspose.Words Cloud Product Family | Tagged , , , | Leave a comment

Introducing Aspose.Imaging Cloud V3

Share on FacebookTweet about this on TwitterShare on LinkedIn

Hello guys, at aspose, we always motivated to provide best solutions to our customers. We keep improving our APIs by fixing the reported issues and adding new features. We are pleased to share all new version of Aspose.Imaging Cloud 19.4. We have taken time since version 19.1 to migrate to the new architecture and enrich Aspose.Imaging Cloud 19.4 with improved performance and enhanced formats support. In this version, the major breaking change is the introduction of API V3 version. The V3 version API is a more simplified API, it has more optimized and refined internal architecture. This version made easy to work with cloud storage. Now you do not need to use a separate API for the purpose. The API includes methods for performing different storage related operations. Learn more.

What’s New in Aspose.Imaging Cloud V3 Version

  • We have added support of CDR, CMX, DJVU and PDF formats, along with enhanced cross-format conversion for common operations. Please, look at the common operations format support map to see what you can achieve!
  • Image rendering quality for export, resize and rotate/flip operations became better
  • Resize operation performance for CDR, CMX, SVG, EMF and WMF vector formats has been improved
  • AI features subsystem has been reworked to improve both performance and stability
  • Advanced EMF and WMF processing APIs now allow to save the result in different formats
  • Several problematic APIs have been fixed
  • Storage APIs from now on are included in Imaging for a better user experience and unification
    • File API – Methods for upload, download, copy, move, delete files: input documents and rendering results, in the cloud storage
    • Folder API – Methods for create, copy, move, delete folders in the cloud storage
    • Storage API – Methods for getting storage information and file information

Breaking Changes

  • API V3 introduction
  • PNG, DNG, ODG and DICOM APIs has been removed since they were supporting only a simple conversion without any advanced processing parameters. Please, use Save As APIs for export operations regarding these formats from now on. It’s possible that some of the removed APIs will be added later in the future if applicable features are implemented
  • Legacy SaaSposeResponse response format has been removed

How it Works

If you are looking for an API to manipulate industry standard images in your application seamlessly. Then your search is over, Aspose.Imaging Cloud is the best option for the purpose. It provides REST APIs & SDKs for advanced processing and manipulation of various image formats, on major platforms via numerous languages.

Here we demonstrate how easily you can crop and convert an image instantly. We are using Aspose.Imaging Cloud SDK for .NET. There are other SDKs available to use the API directly in your favorite platform with ease

The GetImageCrop API accepts the position as well as the dimension values of the cropping rectangle, whereas the format of the cropped image relies on the value of the format parameter.

Following steps are involved in this example:

  • Upload source file to storage
  • Crop and convert the Image
  • Save response Stream to the local system

Share Your Feedback

Your feedback is important! Please feel free to drop us a comment sharing your thoughts about the new version of Aspose.Imaging Cloud REST API. It helps us to continually improve and refine our API.

Posted in Aspose.Imaging Cloud Product Family | Leave a comment

Perform Mail Merge in a Word Document

Share on FacebookTweet about this on TwitterShare on LinkedIn

Mail Merge is a feature of Microsoft Word for quickly and easily creating documents like letters, labels and envelopes. Aspose.Words Cloud takes the standard mail merge and advances it many steps ahead, turning it into a full-fledged reporting solution that allows you to generate even more complex documents such as reports, catalogues, inventories, and invoices. The advantages of the Aspose.Words Cloud reporting solution are:

  • Design reports in Microsoft Word using standard mail merge fields
  • Define regions in the document that grow such as detail rows of an order
  • Insert images during mail merge
  • Insert HTML during mail merge

Basic Steps

Steps to perform a mail merge are quite easy. First, you use Microsoft Word to create and design a Word document normally called a template. Note that the document does not have to be a Microsoft Word Template (.dot), it can be a normal .doc document. You insert some special fields called merge fields into the template in places where you want data from your data source to be later inserted. Then with Aspose.Words REST API you execute a mail merge operation. The mail merge operation will take data from your data source and merge it into the document.

You can also designate repeatable merge regions in the document or insert special merge fields that allow you to insert other content such as images. Depending on how you set up mail merge fields and repeatable regions inside the document, the document will grow to accommodate multiple records in your data source. If you do not use mail merge regions, then the mail merge will be similar to Microsoft Word mail merge and the whole document content will be repeated for each record in the data source. Using repeatable mail merge regions, you can designate portions inside a document that will be repeated for each record in the data source. For example, if you mark a table row as a repeatable region then this table row will be repeated, causing the table to dynamically grow to accommodate all of your data.

Prepare a Document

Before you execute a mail merge, you need to prepare the document template. You should insert merge fields that will be replaced with values from your data source.

Inserting Merge Fields into a Document

To Insert Merge Fields into a Document:

  1. Open your document in Microsoft Word.
  2. In the document, click where you want to place a merge field.
  3. Open the Insert menu and select Field to open the Field dialog.
  4. From the Field names list, select MergeField.
  5. In the Field name text box, enter a name for the merge field and press OK.

Since a merge field is a regular Microsoft Word field, you can switch between displaying field codes and results in your document in Microsoft Word using the keyboard shortcut Alt+F9. Field codes appear between curly braces.

Simple Mail Merge

In order to prepare your template to perform a simple mail merge (without regions, similar to the classic mail merge available in Microsoft Word) you should just insert one or more merge fields in the places you want to be populated with data from the data source.

Let us take a look at the Dinner Invitation demo. It creates a letter for a list of clients defined in the data source. The template contains a number of merge fields that are populated from two data sources; in other words, two mail merges are performed one after the other. First, data from the first data source is merged into the template. This data source contains only one row because this is information about the inviter, so the whole document content is not repeated and only the appropriate fields are filled with data. Then the second mail merge operation is executed. The data source it uses contains information about the clients. The whole template is repeated for each data row and every repeated copy is populated with the corresponding client’s data.

As a result, we have a document that consists of five filled-in, complete, and personalized invitation letters (a fragment of the very first one is shown below):

As you can see, it is possible, and sometimes useful to perform more than one merge operation with the same template to add data in stages. You can insert NEXT fields in the Word document to cause the mail merge engine to select the next record from the data source and continue merging. When the engine encounters a NEXT field, it just selects the next record in the data source and continues merging without copying any content. This can be used when creating documents such as mailing labels.

The code to perform Simple Mail Merge is given below:

Mail Merge with Regions

If you want to dynamically grow portions inside the document, use mail merge with regions. To specify a mail merge region in the document you need to insert two mail merge fields to mark the beginning and end of the mail merge region. All document content that is included inside a mail merge region automatically will be repeated for every record in the data source.

To mark the beginning of a mail merge region, insert a MERGEFIELD with the name TableStart:MyTable, where MyTable corresponds to the tag or key in XML or JSON respectively. To mark the end of the mail merge region insert another MERGEFIELD with the name TableEnd:MyTable. Between these marking fields, place merge fields that correspond to the fields of your data source. These merge fields will be populated with data from the first row of the data source, then the whole region will be repeated, and the new fields will be populated with data from the second row, and so on.

Follow these simple rules when marking a region:

  • TableStart and TableEnd fields must be inside the same section in the document
  • If used inside a table, TableStart and TableEnd must be inside the same row in the table
  • Mail merge regions can be nested inside each other
  • Mail merge regions should be well formed (there is always a pair of matching TableStart and TableEnd with the same table name)

As an example, have a look at the Item Catalog demo. Here is a fragment of a region prepared for mail merge:

Note that both the marking fields TableStart:Item and TableEnd:Item are placed inside the same row of the Word table. After executing the mail merge, here is the result:

The code to perform Mail Merge with Regions is given below:

Mail Merge using ‘Mustache’ Template Syntax

This syntax allows you to create templates for use with mail merge that use plain text markers instead of merge fields. These markers look like this: {{ FieldName }}

Object.Attribute Syntax

You can easily merge attributes of fields using the following syntax:

  {{ Address.Street }}  

This will merge data from XML data which looks like this:

<Order> // <-- Current context is here.
<Number>23</Number>
<Address>
<Street>Nelson Street</Street>
<Suburb>Howick</Suburb>
<City>Auckland</City>
</Address>
<PhoneNumber>543 1234</PhoneNumber>
</Order>

Foreach Blocks

You can merge data from multiple records using the foreach tag. This is similar to mail merge regions with conventional merge fields. You can nest such blocks.

{{ #foreach Order }}
{{ Number }}
  {{ Address.Street }}
    {{ #foreach Item }}
      {{ Description }} {{ Cost}} {{ Total }}
     {{/foreach Item }}
{{ /foreach Order }}

You can also mix these fields and place them inside other Microsoft Word fields such as IF or Formula fields.

Conditional Block

You can use mail merge with IF statement using Aspose.Words Cloud. The IF block executes only if the Boolean expression associated with it is true. The syntax of IF is shown below.

{ IF "{{ GENDER }}" = “MALE” “true text” “false text” }

The code to perform Mail Merge using ‘Mustache’ Template is given below:

Insert HTML During Mail Merge

Both executeMailMerge and executeTemplate APIs provide support for inserting HTML on a merge field. You just need to make sure you escape HTML characters in data source string and use “format”=”html” attribute as shown below:

{   
"dataSourceList": {
"contractDS": {
"contractDescription": {
"format":"html",
"htmlText": "<b>Test me 1<br><br><i>Test me 2<br><br><u>Test me 2</u></i></b><br>"
}
}
}
}

Following code shows how to insert HTML during mail merge:

Insert Images During Mail Merge

You can also insert images on a merge field. Scale factor for images can be set using ‘%’, ‘px’ or ” (proportional scaling). The code to insert images during Mail Merge is given below:

Cloud SDKs

Although the above code is in .NET, Aspose.Words Cloud SDKs are available in five different languages: .NET, Java, Ruby, Python and Node.js. Therefore, you can conveniently call Mail Merge APIs in any of these languages.

Posted in Aspose.Words Cloud Product Family | Leave a comment

Insert Headers and Page Numbers in a Word Document

Share on FacebookTweet about this on TwitterShare on LinkedIn

The header is a section of the document that appears in the top margin and generally contains information such as the page number, date, and document name. With Aspose.Words REST APIs you can insert headers and page numbers in a Word document. By default, the headers are the same on each page but we can create different headers for odd and even pages.

This post aims to achieve the following layout of the document in which the header on the first page is different than the rest of the pages:

Before calling any Aspose REST API, we need to create Aspose Cloud account and obtain our App Key and App SID. Getting Started article explains how to perform these steps.

Moreover, we need to upload the sample document to the Cloud Storage as all the operations on the document will be performed in the Cloud:

Insert Header in a Word Document

PUT /words/{name}/{sectionPath}/headersfooters API adds headers in a document and its headerFooterType parameter can take one of the following six values:

ValueDescription
HeaderFirstHeader for the first page of the section.
HeaderPrimaryPrimary header, also used for odd numbered pages.
HeaderEvenHeader for even numbered pages.
FooterFirstFooter for the first page of the section.
FooterPrimaryPrimary footer, also used for odd numbered pages.
FooterEvenFooter for even numbered pages.

Please use HeaderFirst value to insert header in the first page:

and HeaderPrimary value to insert header in the rest of the pages:

Since the first header is different than the others, set DifferentFirstPageHeaderFooter parameter value to true as shown below:

So far empty paragraphs have been added to the headers of the document. In oder to add text to these headers we will use PUT /words/{name}/{paragraphPath}/runs API. The code shown below is adding “Aspose” text in the first header and “Cloud File Format APIs” text in all other headers:

Apply Formatting to a Header’s Text

Formatting can be applied to a header’s text using POST /words/{name}/{paragraphPath}/runs/{index}/font API. The API accepts fontDto object in its body, whose Resource Properties’ details are given in Update Font Properties of the Text article. The following code is setting font family of the header text to Verdana, text size to 14 and text colour to black.

After making the above API calls, the input document looks as follows:

Insert Page Numbers in a Word Document

POST /words/{name}/insertPageNumber API is used to insert page numbers in a Word document. The API accepts following JSON object in its body:

{
  "Format": "string",
  "Alignment": "string",
  "IsTop": true,
  "SetPageNumberOnFirstPage": true
}

Since we are adding page numbers in the header, we will set IsTop parameter’s value to true. However, to add page numbers in the footer, set the value to false.

Finally, we have added headers and page numbers to the document.

The complete code of this post is available on GitHub.

Posted in Aspose.Words Cloud Product Family | Leave a comment

Aspose.CAD Cloud is Launching Soon!

Share on FacebookTweet about this on TwitterShare on LinkedIn

We are glad to announce that the first release of Aspose.CAD Cloud REST API is about to launch. The REST API will be available very soon to be consumed in your applications. It will allow you to manipulate AutoCAD files in your application using a simple set of requests. Aspose.CAD Cloud REST API will give you a rich set of features to work with AutoCAD files on any platform with minimal learning curve.

It is a REST API that will allow developers to convert AutoCAD DWG, DWF and DXF files to PDF and Raster images. It does not require AutoCAD or any other software for working with the AutoCAD files. 

Salient features

  • Export AutoCAD files to PDF and Raster Image Formats
  • Get Properties of AutoCAD files
  • Change Scale of AutoCAD files
  • Rotate and Flip AutoCAD files

Supported formats

Aspose.CAD Cloud REST API supports following file formats:

Read: DWG, DXF, DWF, DGN

Write: PDF, PNG, BMP, TIFF, JPEG, GIF

Our first version

We are currently in the process of preparing Examples and Documentation for this new product. We have planned to release the first version of Aspsoe.CAD Cloud REST API soon with features shared above. If you have any questions or suggestions, please feel free to write on aspose.cloud Forum.

 

Please stay tuned to this blog for further updates.

Posted in Aspose.CAD Cloud Product Family | Tagged , , , | Leave a comment

Working with Cloud File Format REST APIs and SDKs – aspose.cloud Newsletter February 2019

Share on FacebookTweet about this on TwitterShare on LinkedIn
LinkedIn YouTube Twitter Facebook
Share this issue:

Monthly Newsletter

February 2019

Cloud REST API and SDKs for working with Microsoft Visio Diagrams
Manipulate Visio files without Microsoft Visio installed
 
Cloud REST API and SDKs for working with Microsoft Visio Diagrams
 

Aspose.Diagram offers cloud REST API and SDKs for .NET, Java, cURL, PHP, Python, Ruby and Node.js platforms to seamlessly create, edit and convert Visio file formats without needing Microsoft Visio. It supports working with native VSD/VSDX format as well as other popular Visio formats including VSS, VST, VSX, VTX, VDW, VDX, VSSX, VSTX, VSDM, VSSM and VSTM.

Explore NOW Free Trial

Individual Cloud SDKs also available for: .NET Java PHP cURL Python NodeJS Ruby
Product News
Product News
Product News
 
Feedback
Feedback
Feedback
 
Posted in Customer Newsletters | Leave a comment

Download HTML Page from Web using Aspose.HTML Cloud 18.12

Share on FacebookTweet about this on TwitterShare on LinkedIn

We are pleased to announce Aspose.HTML Cloud 18.12 release. This release extends the functionality of Template Merge feature by fixing some minor issues and introducing new options to control the template data population. We have also included a new feature to download HTML of a web page with its linked resources. Please check the detailed release notes to get an idea about all the new features/enhancements and fixes made in this release.

The following sections describe some details regarding these features.

New features and enhancements

  • Downloading HTML page from Web

Now you can download HTML page from the Web by its URL with linked resources as a ZIP archive.

  • We have introduced options parameter in Template Merge API that allows to pass a JSON list of options that provide control on some template elements. In the current version, the following options are implemented:
    • rm_tabhdr: possibility to leave the header row in a TABLE template element if there are no data to fill it (by default, empty table is omitted). 
    • cs_names: possibility to use case-insensitive names of template fields (by default names are case-sensitive). Partially implemented in this release, this option is supported only for JSON data.

Usage example (any option can be omitted):

options={ 'cs_names':false, 'rm_tabhdr':false }

Aspose.HTML Cloud Product Family Resources

Following are the links to some useful resources you may need to accomplish your tasks.

  • Product Overview – An overview of Aspose.HTML Cloud REST APIs
  • Online Documentation – Detailed API documentation with code examples and details about API functional areas
  • Cloud Dashboard UI Help Topics
  • Forum – Our free online support forum where we address your queries and inquiries
  • Web API Explorer (Live Examples) – Quickly browse through all Aspose.HTML Cloud REST APIs and test them in the browser
  • Cloud SDKs – An SDK takes care of a lot of low-level details of making requests and handling responses and lets you focus on writing code specific to your particular project

Start a Free Trial Today

Start a free trial today – all you need is to sign up with the aspose.com. Once you have signed up, you are ready to try the powerful file processing features offered by Aspose for Cloud.
Posted in Aspose.HTML Cloud Product Family | Tagged , , | Leave a comment

Convert HTML to Markdown and MHTML File Format in Aspose.HTML Cloud 18.11

Share on FacebookTweet about this on TwitterShare on LinkedIn

We are happy to announce Aspose.HTML Cloud 18.11 release. This monthly release extends the list of supported file formats. Now, you can convert HTML file to Markdown and MHTML file formats using Aspose.HTML Cloud REST API. Please check the detailed release notes of this version to get an idea about all the new features/enhancements and fixes made in this release.

The following sections describe some details regarding these features.

Convert HTML to Markdown

In this version, we have included the support of Markdown format. Now you can convert HTML file to Markdown file format. The API supports two flavors of Markdown format: standard Markdown and GitLab Flavored Markdown format. All you need to set useGit API parameter as per your requirements. Please check following APIs for converting HTML to Markdown.

Convert HTML to MHTML

Aspose.HTML Cloud 18.11 introduced the conversion of HTML to MHTML. MHTML, short for MIME Encapsulation of Aggregate HTML Documents, is a web page archive format used to combine several HTML documents along with their resources into a single document archive. While converting the HTML to MHTML, you can handle the resource depth level using maxDepth API parameter, scripts with javaScript API parameter, URLs with urlRestrict API parameter and use defaults API parameter to specify the default way of resource handling.  Please check following APIs and their parameters detail for the HTML to MHTML conversion.

Aspose.HTML Cloud Resources

Following are the links to some useful resources you may need to accomplish your tasks.

  • Product Overview – An overview of Aspose.HTML Cloud REST APIs
  • Online Documentation – Detailed API documentation with code examples and details about API functional areas
  • cloud Dashboard UI Help Topics
  • Forum – Our free online support forum where we address your queries and inquiries
  • Web API Explorer (Live Examples) – Quickly browse through all Aspose.HTML Cloud REST APIs and test them in the browser
  • Cloud SDKs – An SDK takes care of a lot of low-level details of making requests and handling responses and lets you focus on writing code specific to your particular project

Start a Free Trial Today

Start a free trial today – all you need is to sign up with the aspose.com. Once you have signed up, you are ready to try the powerful file processing features offered by Aspose for Cloud.

Posted in Aspose.HTML Cloud Product Family | Leave a comment

Create, Read and Convert or Manipulate Microsoft Visio Diagrams with Aspose.Diagram Cloud

Share on FacebookTweet about this on TwitterShare on LinkedIn

Aspose is extending its community by providing robust and efficient file formatting APIs. We are glad to announce our another Cloud API: Aspose.Diagram Cloud.  It is a platform independent REST API, that allows developers to work with Microsoft Visio files in their application without installing Microsoft Visio. It seamlessly enhances your application with the capability to create, read and manipulate Microsoft Visio files using a simple set of requests.

The following sections describe some feature details of Aspose.Diagram Cloud REST API. Please also check the first release notes for more details.

Aspose.Diagram Cloud Features

It supports working with native VSD/VSDX format as well as other popular Visio formats including VSS, VST, VSX, VTX, VDW, VDX, VSSX, VSTX, VSDM, VSSM and VSTM. First version of Aspose.Diagram Cloud provides following features:

Supported formats

Read: VDW, VSD, VSS, VST

Read and Write: VSDX, VSX, VTX, VDX, VSSX, VSTX, VSDM, VSSM, VSTM

Export: BMP, JPEG, TIFF, EMF, SVG, PNG, PDF, HTML, XPS, SWF, XAML

Convert diagram to another format

Aspose.Diagram Cloud REST API provides feature to convert the diagrams to other popular formats for quick and easy information sharing across the organization. Please see the following URI and REST command(cURL) for the purpose.

URI

https://api.aspose.cloud/v1.1//diagram/{filename}/SaveAs

Aspose.Diagram Cloud for cURL example

// First get Access Token
// Get App Key and App SID from https://dashboard.aspose.cloud/
curl -v "https://api.aspose.cloud/oauth2/token" \
-X POST \
-d 'grant_type=client_credentials&[Your AppSid]&client_secret=[Your AppKey]' \
-H "Content-Type: application/x-www-form-urlencoded" \
-H "Accept: application/json"
  
// cURL example to convert Diagram file to another format
curl -v "https://api.aspose.cloud/v1.1/diagram/file_get_1.vdx/SaveAs?IsOverwrite=true&newfilename=file_get_1.pdf" \
-X POST \
-d '{"Format":"pdf"}' \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Authorization: Bearer [Access Token]"

Aspose.Diagram Cloud SDK for.NET example

protected ApiClient client;
protected Configuration config;
protected static OAuthApi oauth2 = null;
protected string grantType = "client_credentials";
protected string clientId = ""; // Get App Key and App SID from https://dashboard.aspose.cloud/
protected string clientSecret = ""; // Get App Key and App SID from https://dashboard.aspose.cloud/
protected static string accesstoken;
protected string refreshtoken;

static void Main(string[] args)
{
    DiagramExamples diagramExamples = new DiagramExamples();
    // Convert Diagram File to Another Format
    diagramExamples.PostSaveAs();
}

// Convert Diagram File to Another Format
private void PostSaveAs()
{
    DiagramFileApi instance = new DiagramFileApi(GetConfiguration());

    string name = "file_get_1.vdx";
    bool isOverwrite = true;
    string folder = null;

    FileFormatRequest format = new FileFormatRequest() { Format = "pdf" };
    string newfilename = "file_saveas_1.pdf";

    UpdateDataFile(name);
    var response = instance.DiagramFilePostSaveAs(name, format, newfilename, folder, isOverwrite);
}

private void UpdateDataFile(string filename)
{
    StorageApi StorageApi = new StorageApi(clientSecret, clientId);

    // Upload document to Cloud Storage
    PutCreateRequest request = new PutCreateRequest(filename, File.OpenRead(@"c:\Data\" + filename), null, null);
    StorageApi.PutCreate(request);
}

private Configuration GetConfiguration()
{
    if (oauth2 == null)
    {
        oauth2 = new OAuthApi("https://api.aspose.cloud");
        var oauth2response = oauth2.OAuthPost(grantType, clientId, clientSecret);
        accesstoken = oauth2response.AccessToken;
        refreshtoken = oauth2response.RefreshToken;
    }
    Dictionary<string, string> headerParameters = new Dictionary<string, string>();
    headerParameters.Add("Authorization", "Bearer " + accesstoken);
    client = new ApiClient();
    config = new Configuration(client, headerParameters);
    return config;
}

Security and Authentication

The Aspose.Diagram Cloud REST API is secured and requires authentication using an app access key ID (appSID) and app secret access key with OAuth 2.0 or URL Signing authorization header. You can see the complete details here.

API Explorer

Aspose for Cloud REST APIs comes with a web based API Explorer as well. It is the easiest way to try out our API right away in your browser. It is a collection of Swagger documentation for the aspose.cloud APIs. So simply, first you need to sign up with aspose.cloud, get APP key and SID and start testing Aspose.Diagram Cloud REST API in your favorite browser interactively.

SDKs

Aspose.Diagram Cloud REST API comes with SDKs for different platforms to use this REST API in your specific project effortlessly. An SDK takes care of a lot of low-level details of making requests and handling responses and lets you focus on writing code specific to your particular project. Please check out our GitHub repository for a complete list of Aspose.Diagram Cloud SDKs along with working examples, to get you started in no time.

Aspose.Diagram Cloud Resources

Following are the links to some useful resources you may need to accomplish your tasks.

Start a Free Trial Today

Start a free trial today – all you need is to sign up with the Aspose Cloud service. Once you have signed up, you are ready to try the powerful file processing features offered by Aspose for Cloud.

Posted in Aspose.Diagram Cloud Product Family | Tagged , , , , , , , , , , , , , | Leave a comment

Reorder Multiple Slides in one API call using Aspose.Slides Cloud 18.12

Share on FacebookTweet about this on TwitterShare on LinkedIn

Aspose.Slides CloudWe are pleased to announce a new release of Aspose.Slides Cloud 18.12. We have introduced an API that let you reorder multiple slides in one API call. Moreover, we have added separate APIs for adding, cloning and reordering presentations. For a detailed note on what is new and fixed, please visit the release notes section of APIs Documentation.

 

New Features and Enhancements

    • Reorder Multiple Slides in a Presentation in one API Call

Please use POST /slides/{name}/slides/reorder to reorder multiple slides in a presentation in one API call.

    • Add Slides to a Presentation

Please use POST /slides/{name}/slides/add to add slides to a presentation.

    • Copy Slides

POST /slides/{name}/slides/copy API let you copy slides within the current document or from another presentation.

    • Move Slides

POST /slides/{name}/slides/{slideIndex}/move API let you move slides to another position.

Aspose Cloud Resources

You may visit the following API resources for getting started and working with the API:

  • Product Documentation – Detailed API documentation with code examples and details about API functional areas
  • Cloud SDKs – An SDK takes care of a lot of low-level details of making requests and handling responses and let you focus on writing code specific to your particular project
  • API Reference Guide – Quickly browse through all Aspose.Slides Cloud APIs and test them in the browser
  • Aspose.Slides Forum – Our free online support forum where we address your queries and inquiries
Posted in Aspose.Slides Cloud Product Family | Leave a comment