Free Support Forum -

Aspose Cloud file formatting API end point version issue in Href/Url

Our client complaint about our system not working, we tracked it down to the return Href/URL in the returned array call to PDF to image conversion.

This is what we were expecting:

We are still on v1.1 and have been a customer for a long time, this is the second time you have modified a legacy version, the first time was when .cloud was added in favor of .com which was understandable.

My question is was this an error? Will this continue to happen? And why are we changing a legacy version?

- Luis


Thank you for your inquiry and sharing details.

Current swagger is changed a bit on last Friday to set version number in requested URL on user choice. User can set any version like v1.0 or v1.1. Please take a look over updated swagger link!/v{version:apiVersion}/pdf/PdfDocument_PutConvertDocument

The current swagger will be replaced with the new Dynabic.Swagger which will have a combo box for version number and the selected version will be put in the requested URL. This will ensure APIs will never break.

I hope this helps. If you have any further questions, please feel free to share.


Naeem Akram

Aspose - File Format APIs.

Got a Complaint? File it!