Cant access Barcode API

Hi

I have tried to use Barcode API V1.1

1.First i tried REST Live example link

http://api.aspose.com/v1.1/barcode/generate?text=test%20Text&type=code128&appSID=2aa66507-1239-4838-91d2-45dc226077ec&signature=FcBfacAOMBeYyCP5Hg%2FWymB%2B2IY

I have changed appSID value with my appSID provided when aspose cloud account created but dont know what value is given to signature param

Then i tried the help link

http://api.aspose.com/v1.1/Help/Api/GET-barcode-generate_appSid_text_type_format_resolutionX_resolutionY_dimensionX_dimensionY_enableChecksum

In the above link i have entered values(ScreenShot 1) and tested it

Link formed by test API method : barcode/generate?appSid=xxx&text=test&type=code128&format=jpeg&resolutionX=400&resolutionY=400&dimensionX=0.35&dimensionY=2&enableChecksum=Yes

xxx - appSID

It returns Bad request error(ScreenShot 2)

I append ( http://api.aspose.com/v1.1/ )to the above link and tested it in RESTCLIENT, it returns 403 Forbidden error

So kindly provide detailed URI Link for Barcode API or notify my mistakes

Hi

Well, there is no way to replace App SID of live example. You need to generate your own signature based on the App Key. The signature is the base64 encoded App Key. So you need to generate the signature and then you can use it in the application. Please have a look over sign method: REST API Methods . It adds signature parameter to the url.

Second, I’m sorry to share with you that the help test service is not working as expected. It always gives a bad request message. I’ll check with concern team and update you soon. However, you can try using the following example codes: Working with Barcode Generation

Please feel free to reply us in case of any confusion or questions.

Hi

Thank you for being patient.
Imran Rafique:
I'm sorry to share with you that the help test service is not working as expected. It always gives a bad request message.
It is to update you that we've logged this problem under ticket id SAASBARCODE-45 in our issue tracking system. Your request has also been linked to this issue. We'll keep you informed regarding any updates. We're sorry for the inconvenience you faced.