Ask HN: Who Owns API Drift

2 points | by Nalin_2408 9 hours ago ago

3 comments

  • huubhermsen 8 hours ago ago

    It really depends on the type of API.

    Is this a generic open source API? Than it's totally on you, you could jump on their repository page or socials and ask why this changed, they deliver this service to you free so don't "hold them responsible".

    For contracted API's wether they're paid or free you should contact the maintainer directly to raise your issue.

    For internal API's: I believe these should never be breaking and the responsibility for this is with the team maintaining them.

  • onion2k 8 hours ago ago

    You miss the announcements..

    If that happens, that means it's a you problem.

    If they changed without an announcement, that probably means it's a them problem, but SLAs may mean it still isn't. If you're expecting free support and not paying anything it's still on you.

    Do you have any solution?

    First, write robust software that handles errors well. Your app should handle 4xx and 5xx errors properly, so if this happens things don't just crash and burn. You were alerted at 2am so I imagine you have this already.

    Second, accept that APIs will fail. Sometimes it'll be a change, other times it'll be an outage, a lot of the time it'll be DNS. Write your software to cope with things being down. It's a pain, but tech isn't perfect.

    Lastly, prefer vendors that version their APIs, or that promise backward-compatibility, or that inform you about changes properly and with plenty of notice.

    (Absolutely reckless suggestion that I'd love to see someone do - hook Claude up to your telemetry system and build an agent that can figure out the problem, fix the code, and deploy it to production all by itself. Call it 'self-healing code' and raise millions to productize it.)

    • huubhermsen 8 hours ago ago

      Thank god you're more awake than me and elaborated a bit more. Great addition!