{"id":24137,"date":"2019-01-31T16:30:55","date_gmt":"2019-01-31T21:30:55","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=24137"},"modified":"2019-01-31T16:30:55","modified_gmt":"2019-01-31T21:30:55","slug":"mediums-api-stops-working","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/01\/31\/mediums-api-stops-working\/","title":{"rendered":"Medium’s API Stops Working"},"content":{"rendered":"

Write.as<\/a> (Hacker News<\/a>):<\/p>\n

Sometime in the past few weeks, Medium abruptly deleted third-party access<\/a> to their publishing API. There was no warning before, or notice after, this happened — apps just stopped working (including ours).<\/p>\n

[…]<\/p>\n

We trusted that Medium might not do what many VC-funded platforms have done before: open an API, attract developers and users, grow, then shut it all down. Unfortunately, that’s exactly what they did. And unlike their previous pivots<\/a>, they didn’t even give the courtesy of a small heads-up.<\/p>\n

[…]<\/p>\n

Update 11:33am EST: we received a response from Medium, though it’s still confusing:<\/p>\n

We recently experienced an interruption with API, and the ability to generate new oAuth-based applications has been restricted. I have reenabled that feature.<\/p><\/blockquote>\n

This doesn’t really explain why our 2-year-old integration suddenly stopped working (we didn’t need to generate a new application).<\/p>\n<\/blockquote>\n\n

Michael Love<\/a>:<\/p>\n

\n

My general rule of thumb is that unless you’re a) paying for it and also b) those payments represent a significant source of revenue for the company offering it, it’s never worth investing significant effort to rely on a third-party API.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n