You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the API with the email parameter with rate throttling on our client software and we have noticed a dramatic increase in "Socket Timeout Exceptions" and "Read Timeout Exceptions", even with delays between API requests as high as 1 second. We also cache responses where feasible.
Is there anything we should look that might be causing the Crossref API to excessively throttle us?
-Mike / newsrx.com
The text was updated successfully, but these errors were encountered:
In all likelihood you're experiencing some instability we've been suffering from over the last few weeks. Our polite pool (and to a lesser extent the public pool) have been hit by overeager bots that we've had trouble isolating. Hopefully things will smooth out soon.
If you send me a handful of sample requests (preferably including the email parameter you're using) I can check our logs to look for anything else amiss.
If you're hitting our API in support of a production service and need a more reliable service on our end, we recommend subscribing to our Metadata Plus service, which comes with guaranteed uptimes, increased rate limits, and technical support with 1 business day response times.
Good morning,
We are using the API with the email parameter with rate throttling on our client software and we have noticed a dramatic increase in "Socket Timeout Exceptions" and "Read Timeout Exceptions", even with delays between API requests as high as 1 second. We also cache responses where feasible.
Is there anything we should look that might be causing the Crossref API to excessively throttle us?
-Mike / newsrx.com
The text was updated successfully, but these errors were encountered: