Aspose Cloud end Point Change for Word Document Conversion in C# using Aspose.Words Cloud API

Aspose.Total Cloud Product Family
1

I received following message
advise our customers to move from api.saaspose.com to the new end-point, https://api.aspose.cloud/.

I already distributed the apps with the saaspose URL. Is there any way you could forward the api.saaspose.com to the https://api.aspose.cloud/? Unfortunately it isn’t possible for me to update existing apps.

I tested and code works with the new URL.

Thanks

2

Hi,

As you know we receive signed requests and signatures are different for old and new end-points. Up till now we are maintaining both signatures and redirecting api.saaspose.com requests to our new end-point but now this redirection will also stop on 31st December. We are advertising this since last one and a half year and all references to old end-point have been upgraded to new end-point to enforce this migration.

Is not it possible for you to change the end-point and distribute a hotfix version of your apps? In the meantime, we will also consult our development team what can be done in your case.

Best Regards,

3

Thank you for the reply unfortunately it isn’t possible for me to update since I need to submit to Apple and they rejected the update.

4

Aspose.Cloud.Words.SaveFormat.html is missing from the new .net API

5

Hi,

This issue has been logged into our issue tracking system as MARKETING-9611. We will update you as soon as it is resolved. In the meantime, you can add html to Aspose.Cloud.Words.SaveFormat enum in your copy of the SDK and rebuild the SDK to quickly fix the issue.

Best Regards,

6

is there any update on the issue?
The apps use only one api
convert

Folder folder = new Folder();
folder.UploadFile(@"" + filePath, "");
Saaspose.Words.Converter converter = new Saaspose.Words.Converter(inputFileName);
converter.Convert(outPath,saveformat);



Thanks

7

Hi,

Actually, you are using the older version of the SDK. Latest version of the SDK is 2.0 as you can see at https://github.com/aspose-words-cloud/aspose-words-cloud-dotnet but this version is not backward compatible so you will have to update your code in order to use this version.

We are updating SDK examples in the documentation and will update your required examples on priority and let you know. Sorry for the inconvenience.

Best Regards,

8

Thanks for the reply.
I tested my code. without any code change I pointed to http://api.aspose.com/v1.1 and it worked.

Product.BaseProductUri = @"http://api.aspose.com/v1.1";



is there any way you could extend it 6 more months or forward?

Thanks

9

Hi,

As far as api.saaspose.com end-point is concerned, we will extend it for your convenience but the main thing we will not do right now is upgrade the SSL certificate for api.saaspose.com to SHA-2. Provided you do not require SHA-2 right now then your app will continue to work beyond the cut-off date. However we cannot make guarantees about this end-point in future so you should continue to try and get this updated within your App at your earliest convenience.

In terms of a redirect; if you are using the HTTPS end-point I’m not sure if a security error would be thrown in your app since we’d be redirecting from one top-level domain to a different top-level domain. As different platforms can behave differently the best approach is for you to test this yourself within your app to see if a redirect from https://temp.bewrite.com to https://api.aspose.cloud work or not.

Best Regards,

10

Thank you for extending.
I don’t need SHA-2 and I don’t use https.
I am updating the new apps. Unfortunately I cannot update the existing ones.

11

Hi,

Thanks for the details. Your existing apps can keep using api.saaspose.com end-point. Please feel free to contact us in case you see any issue at any stage.

Best Regards,

12

Hi,
My users are getting 400 bad request error. I thought you will keep the old API.

Thanks

13

Hi,

Old API is working fine at my end. Can you please share your code and sample document to reproduce the issue? Please also share the email ID registered with your Aspose for Cloud account for further investigation.

Best Regards,

14

It is working now. I was getting 400 error yesterday.

Thanks

15

Hi,

There was some issue in calculating usage of few accounts which was resolved yesterday. You were facing the same issue so it is resolved.

Sorry for the inconvenience.

Best Regards,

16

My customers reported that they are getting upload error often. I also tried 4 times and get error 2 times for the same call (content).
is there any issues with servers?
Thanks

17

Update
I am getting upload files error.

18

Hi,

Unfortunately api.saaspose.com servers have been stopped completely and are not in use now. Aspose for Cloud APIs will work with api.aspose.com end-point only.

We are sorry for the inconvenience.

Best Regards,

19

I know it is too much to ask but is there any way to extend 6 more months
Is there anybody I can call and talk on the phone.
Thanks

20

Hi,

The decision was taken by the management because maintaining api.saaspose.com was not viable for us. However, you can contact our business team if you want to further discuss the issue.

Best Regards,