DOCX to PDF conversion API Call issue in Aspose.Words Cloud API

Aspose.Words Cloud Product Family
1

Hi There,


For a while we’ve been using the URL http://api.aspose.cloud/v1.1/words as the connection to the Aspose Cloud API service for generating PDFs from within our application.

All of a sudden we’re now getting a 404 error and the resource no longer exists.

Can someone assist as to why it’s changed or what the address should be.

Many thanks
2

Hi Dan,

Can you please try again and let us know if it is working for you? Please also share the complete code/URI if the problem persists.

Best Regards,

3
Hi Muhammed,

No it still doesn't work. Quite obvious to check as you can just paste the URI into a browser and receive a 404 error.

Is there now a different URL required to access the service?

We're using the ProcessCommand code that is published on the support area of your site and signing the URI with the code again provided on your website.

A response ASAP would be appreciated as we have urgent documents now not being created. This was working previously and has now stopped.

Thanks

Dan

muhammad.ijaz:

Hi Dan,

Can you please try again and let us know if it is working for you? Please also share the complete code/URI if the problem persists.

Best Regards,

4

Hi Dan,

The URI you shared is the root URI to call any API supported by Aspose.Words for Cloud. You can call any API supported by Aspose.Words for Cloud. Please check the following links for Aspose.Words for Cloud examples and to construct a valid URI.

Converting a Document

Programmers Guide

Best Regards,

5

Hi,

I’ve checked the full url we’re calling and it is as below:

http://api.aspose.cloud/v1.1/words/storage/exist/defaultcontracttemplate.docx?appSID=xxxxxxxxxxxxxxxxxx&signature=xxxxxxxxxxxxxxxxxxx

This produces a 404 error.

We have tried changing the url to:

http://api.aspose.cloud/v1.1/storage/exist/defaultcontracttemplate.docx?appSID=xxxxxxxxxxxxxxxxxx&signature=xxxxxxxxxxxxxxxxxxx

and this produces a 403 error.

This has been working for a while and we have not changed the code and it’s now not working.

Please advise further.

Thanks

Dan

6

Hi Dan,

First URI is incorrect and that is why it is throwing 404. Second URI is correct and it is working fine at my end.

From error code I have doubt if your App SID and Key are interchanged when signing the URI. Please debug your signed URI and confirm if appSID parameter is showing your App SID correctly. If yes, please share your App SID and Key by private message.

7

Hi,


It looks correct as far as I can tell. I’ve sent you a file with the key and sid in it.

Thanks

Dan
8

Hi,


Any progress on this issue please, it’s now becoming quite urgent.

I don’t know why all of a sudden this started happening as we’ve been using the URI that you’ve now said is incorrect for almost a year with no issues.

Many thanks

Dan
9

Hi Dan,

The URI you mentioned i.e. http://api.aspose.com/v1.1/storage/exist/defaultcontracttemplate.docx is working without any issue at my end using your App SID and Key. Not sure why you see this error. Can you please share your complete code for further analysis?

Best Regards,

10

Hi,

I think I’ve managed to work out what was going on. Our code was actually formatting the URI with double forward slashes in places, so the URI being passed to your service was actually:

http://api.aspose.cloud/v1.1/storage/exist//defaultcontracttemplate.docx

This had previously worked as had calls to http://api.aspose.cloud/v1.1/words

I can only assume some minor change in your service has been made that has now prevented routing URI’s with additional forward slashes in them.

Like I stated, we’ve performed over a hundred calls to this URI during testing and not encountered any problems.

Thanks

11

Hi Dan,

Good to know that you have resolved the issue and thanks for sharing the details with us.

Best Regards,

12

Can you provide an explanation as to why this previously worked and then stopped functioning as expected?

13

Hi Dan,

Please check http://www.aspose.com/blogs/aspose-total-product-family/archive/2014/11/10/saaspose.com-end-point-is-going-to-be-discontinued.html for more details and feel free to contact us in case you have further comments or questions.

Best Regards,

14

@DanBailey

As an update, we have introduced API Version 4.0 since Aspose.Words Cloud 19.4 release. This version has a number of improvements. Some of these are the introduction of Storage API methods and the use of JSON Web Token(JWT) to authenticate the API calls. Please find a sample cURL example to convert DOCX to PDF using API Version 4.0.

# First get Access Token
# Get Client ID and Secret from https://dashboard.aspose.cloud/
curl -X POST "https://api.aspose.cloud/connect/token" 
-d "grant_type=client_credentials&client_id=xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx&client_secret=xxxxxxxxxxxxxxxxxx" 
-H "Content-Type: application/x-www-form-urlencoded" 
-H "Accept: application/json"

# cURL example to convert Word Document to PDF
curl -v "https://api.aspose.cloud/v4.0/words/sample.docx/saveAs" \
-X PUT \
-d "{'SaveFormat':'pdf', 'FileName': 'sample.pdf'}" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Authorization: Bearer <jwt token>"