Free Support Forum - aspose.cloud

[500] Error connecting to the API

Hello Aspose Team,

Starting today we are getting the below error when we try to create a folder:

“[500] Error connecting to the API”

However, the same way we do the request has been working for us for several months until yesterday.

We are using the PHP SDK latest version: 20.9.0

Do you have any issues at your side? Thanks.

@infolemadk

We are sorry for the inconvenience. We have reproduced the issue and logged a ticket WORDSCLOUD-1363 for further investigation and resolution. We will notify you as soon as it is resolved.

Hi there @tilal.ahmad ,

Is there anywhere we can track the progress of WORDSCLOUD-1363?

Getting a similar issue with the mail merge API: [500] Error connecting to the API (https://api.aspose.cloud/v4.0/words/MailMerge).

Thanks in advance.

@Unity5

You can check the status from the following issues status window in this thread or can ask us for the update.

Can you please share how you are calling the MailMerge API, using Aspose.Words Cloud SDK for PHP? As we noticed that the issue is only happening with PHP SDK.

Thank you for your reply @tilal.ahmad

To build the basis of our api calls we use:
$this->wordsApi = new WordsApi(ASPOSE_ID, ASPOSE_KEY);

Then to execute requests we use calls similar to:
$this->wordsApi->executeMailMergeOnline($request);

This code was known to be working last week and stopped working yesterday.

Look forward to hearing your suggestions.

@Unity5

Thanks for your feedback. We are updating our Aspose.Words Cloud SDK for PHP and hopefully will share it shortly.

Please can we get an update ASAP, parts of our system are essentially down as a result of this as it has been going on for days.

Kind regards,

@infolemadk, @Unity5

Thanks for your patience and cooperation. We have fixed the issue, it should work now. Please check and confirm.

1 Like

@tilal.ahmad can confirm that our tests for mail merge via the API are now working.

Thanks for the update!

1 Like

@tilal.ahmad I can confirm that the problem has been fixed now. Thanks.

2 Likes