Tom Scott made a wonderful video a while back about open APIs, and about how they (mostly) died out[0]. It's currently called "This Video Has 51,973,714 Views", and I personally believe it's a great watch.<p>[0] <a href="https://youtube.com/watch?v=BxV14h0kFs0" rel="nofollow">https://youtube.com/watch?v=BxV14h0kFs0</a>
I build APIs with the assumption that they'll be open eventually. If not open to the public then at least a third party or some other part of the company once it grows big enough. As such, all of my APIs are open, but some of them don't have a public endpoint. Working like this pushes me to consider how other people would use an API and think about more than just my use case, to document things properly, and spend more time on the DX. I think it makes my APIs better even if no one else actually ever sees them.<p>The downside is that some of the APIs I've built in the past have a bunch of features no one uses. That's a bad thing.
> On the FAIRTIQ side, we do not support this authorisation model yet as we don’t provide an open API<p>So I guess the message from the article is "we love that others provide open APIs but we can't bother".
Tom Scott made a wonderful video a while back about open APIs, and about how they (mostly) died out[0]. It's currently called "This Video Has 51,973,714 Views", and I personally believe it's a great watch.<p>[0] <a href="https://youtube.com/watch?v=BxV14h0kFs0" rel="nofollow">https://youtube.com/watch?v=BxV14h0kFs0</a>