mazira Developer Profile | RapidAPI
mazira / mazira
Discussions
7
AllQuestionsAnswers
arrowNewest
a7@EricLayne, thanks. You might be correct. I tried some stuff, but I can't seem to figure out the problem. I am going to ask one of our senior devs to look at it. Unfortunately, she is on vacation this week. I will keep you posted. Sorry about this.
Mon 1:213/7/17
a7So MaShape is being a bit of a pain. I think they changed some stuff recently that's causing these problems. I reset a bunch of stuff. Can you try again and see if it works?
Wed 4:5028/6/17
a7Hi EricLayne and Sairamakrishna, we are having some problems with the server and MaShape integration at our end. Looking into it right now. We might have to do some upgrades at our end to improve performance. Is this an API you are interested in consuming for commercially?
Tue 3:1727/6/17
a1This error occurs when the Mashape proxy times-out and assumes it is getting no response from the server. This can happen when processing multiple pages at high resolution. I believe that Mashape recently reduced its timeout, exacerbating the problem. There is a way to process a PDF page-by-page, which should avoid the timeout issue. This is not yet documented in Mashape, but I will describe it below: If the output parameter is not specified, it will assume that you are processing page-by-page, and will immediately return a JSON array of relative page URLs. You can then send individual GET requests to these URLs, along with the res, quality, and png8 parameters as query parameters. Note that in this mode, it is not necessary to send res, quality, or png8 along with the original POST request. I will update the Mashape documentation to reflect this additional option.
Fri 3:0620/5/16
a6I will add that if Mashape is still timing out when processing the pages individually, there are a few things we can try. Your `res` and `quality` params are pretty high, and reducing them will speed up the processing. If this is not acceptable, we may have to implement a session endpoint, where you can fire off the conversion and then ping a new URL to detect when the processing is complete.
Thu 7:463/7/14
a6This error occurs when the Mashape proxy times-out and assumes it is getting no response from the server. This can happen when processing multiple pages at high resolution. I believe that Mashape recently reduced its timeout, exacerbating the problem. There is a way to process a PDF page-by-page, which should avoid the timeout issue. This is not yet documented in Mashape, but I will describe it below: If the `output` parameter is not specified, it will assume that you are processing page-by-page, and will immediately return a JSON array of relative page URLs. You can then send individual GET requests to these URLs, along with the `res`, `quality`, and `png8` parameters as query parameters. Note that in this mode, it is not necessary to send `res`, `quality`, or `png8` along with the original POST request. I will update the Mashape documentation to reflect this additional option.
Thu 7:463/7/14
Showing 1-6 of 7 results

Install SDK for (Node.js)Unirest

OAuth2 Authentication
Client ID
Client Secret
OAuth2 Authentication