UPDATE – 2013-04-08 16:32 GMT – it’s been working fine again for the last 10 minutes, and will hopefully continue to do so. Sorry again for the problem.
The problem described in this post has arisen again, affecting our API and website. See the linked post for the details. Sincere apologies!