We started getting 401 error this morning at 11:10 am. Before that we had no issue with API.
Making a post request to the following API: https://api.aspose.cloud/v3.0/barcode/recognize?Type=Pdf417
and getting the following error
{
“requestId”: “xxxxxxx-xxxx-xxxxx-xxxxx”,
“error”: {
“code”: “errorAuthorization”,
“message”: “invalid_token”,
“description”: “The signature key was not found”,
“dateTime”: “2025-01-09T17:38:54.1604579Z”,
“innerError”: null
}
}
1 Like
ASPOSE support emailed us after 3 hours, and had no update on their status page. This server issue was on their side
We did have some issues today earlier that could have affected your subscription temporarily.
Hello @forthdev !
Please accept our sincerest apologies for the inconvenience and the lack of timely updates on our status page.
The 401 (“invalid_token”) issue you encountered was due to a misconfiguration on our side during an infrastructure migration. Our team identified the problem and has since resolved it. You should now be able to use the Aspose.BarCode Cloud API again as expected.
Should the issue persist, let us know right away, and we will investigate further. We sincerely appreciate your patience and understanding, and we’re taking steps to ensure that this kind of interruption does not happen again.
@denex I’m facing the exact same issue now. I’m fetching fresh token from the token endpoint, and using it in the words convert endpoint. I don’t think its an issue with the request because we haven’t changed the way we make requests in a while and have been using Aspose cloud for many months.
The status page does indicate there was a downtime today but says it’s fixed whereas it’s not - the reliability has been quite disappointing lately.
image.png (35.1 KB)
Hello!
We’re having some issues with our billing backend, but we’re working on a fix. It should be resolved soon. Sorry for the trouble! Let us know if you need any help in the meantime.