You’ve heard it before: “Houston, we have a problem!”
Customers like Vestiaire are translating hundreds of product descriptions every day, and new partnerships are seeing dozens of new platforms offer translation to their users via our API. We’ve seen a huge increase in API requests compared to last year.
The bad news: If you’ve been using our API recently, you may have experienced problems. Some calls may have only gone through after several tries. Some calls may not have gone through at all.
So this is us saying a big “sorry” to all of you who use our API. We know you’re in pain.
Our Engineering team has now made fixes to prevent these specific issues coming up again. As specific examples, we have added more aggressive caching and separated incoming traffic (i.e. ‘writes’) from outgoing traffic (i.e. ‘reads’). We’re also working hard on longer-term improvements to our system. These will help us support massive scale for years to come. Our commitment to you is top priority for us.
In the meantime, here are a few tips that may help you avoid running into problems:
1) Reduce the amount of jobs, words, and characters in each payload to have a better chance of getting through the first time. If you have more than 150 jobs or 8,000 units, don’t hesitate to get in touch first.
2) Submit your jobs outside 10:00-19:00 GMT, which is our peak load time. We’ll improve our ability to show peak times over the next few months.
To stay updated on API stability, check back on this blog post for updates.