We have been evaluating the words convert API with a trial account. It was working fine but suddenly from some point today it started throwing 401 Unauthorized. We tried regenerating the token, new account/application, nothing worked. Its blocking our evaluation and development. Kindly help us on priority.
Here is the sample request and response,
curl --location --request PUT 'https://api.aspose.cloud/v4.0/words/convert?format=pdf' \
--header 'Authorization: Bearer token' \
--form 'Document=@"/path/to/sample.docx"'
Response:
{"requestId":"5d8c0041e2c79fee6461c7490fb902f3","error":{"code":"errorAuthorization","message":"Unauthorized","description":"Operation Failed. The authorization data is incorrect.","dateTime":"2025-01-09T17:41:41.080766Z","innerError":null}}
@avinashs2401
It seems that you are encountering a 401 Unauthorized error when using the Words Convert API, which indicates that the authorization data is incorrect. Here are some steps you can take to troubleshoot and resolve this issue:
-
Token Validity: Ensure that the token you are using is valid and has not expired. Tokens typically have a limited lifespan, and if you are using a trial account, it may have specific limitations.
-
Regenerate Token: Since you mentioned that you have already tried regenerating the token, make sure that you are using the new token in your request. Double-check that the token is correctly formatted and included in the Authorization header.
-
Correct API Endpoint: Verify that you are using the correct API endpoint. The endpoint you provided seems correct, but ensure that there are no typos or incorrect parameters.
-
Account Status: Check the status of your trial account. Sometimes, trial accounts may have restrictions or may be disabled after a certain period.
-
Client ID and Secret: Ensure that the Client ID and Client Secret you are using are correct. If they are incorrect, it will lead to authorization failures.
-
Testing with a Different Account: If possible, try creating a new account or using a different account to see if the issue persists. This can help determine if the problem is account-specific.
-
Debugging: If you have access to debugging tools, consider enabling debug mode in your API client to get more detailed error messages that might help identify the issue.
If you continue to experience issues after trying these steps, please provide any additional error messages or logs that may help in diagnosing the problem further.
Feel free to reach out for more assistance if needed!
Sorry for the inconvenience, admin team said that issue was fixed.