• This is Microsoft.
  • He returns Webhook success with a code 200 and plaintext 1.
  • He returns Webhook failure with a code 200 and a string tells its endpoint returned error 400.
  • the string didn’t tell what exactly the error.
  • Don’t be like Microsoft.

EDIT: Got a few details wrong since this happens a few months ago and this meme used to be on r/ProgrammerHumor. Also the proof:

  • barrage4u@lemmy.world
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    1 year ago

    It’s hard when you hit an endpoint that hits another endpoint, because technically the first request IS a 200. No right or wrong way as long as they are consistent and document it clearly imo

    • callmepk@lemmy.worldOP
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Now here is the fun part: they do not have a API documentation; they only have a very generic guide on how to setup webhook API

        • vfsh@lemmy.blahaj.zone
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Microsoft docs in general are the worst. Can’t tell you how many fucking dead links and straight up incorrect information I’ve come across on their official help articles

        • masterspace@lemmy.ca
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Lmao, Microsoft code docs are absolutely amazing compared to the undocumented bullshit I have to deal with at most companies that have rolled their own services.

          • candyman337@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            Right but Microsoft isn’t most companies, it’s a SOFTWARE company. A multibillion dollar one at that. Compared to other even multimillion dollar companies, their docs are fucking atrocious

    • Scrubbles@poptalk.scrubbles.tech
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I my experience you then send a different error code to help developers know that right away. Really if there is nothing the developer could do it should be a 500 server error. The server did in fact error.

      If the developer should have done something different then translate it to an appropriate code, 400 bad request or something

  • marcos@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    The quality of Microsoft APIs is legendary… if you just take a minute to study win32, you will be always glad that those webserver responses are the kind of shit you have to deal with.

    But to be fair, this looks exactly like a well designed API that somebody pushed behind a corporate firewall.

  • flashgnash@lemm.ee
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Working with Microsoft’s APIs is akin to trying to navigate a maze of barbed wire with a blindfold on

  • Ducks@ducks.dev
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Or when you hit an API and the error message comes back as html instead of json.

    • squirmy_wormy@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      What don’t you like about graphql error handling? Whenever I’ve made a graphql api, I use the default errors as unhandled/system errors and payloads return handled error types.

      It’s a bit more boilerplate to wire up, but I find it smooth to build and use

      • z2k_@lemmy.nz
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Just making a point that it always returns a 200 even when it errors.

  • UncommonBagOfLoot@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Wait, do you know if this still happens?

    I have a ticket in our backlog to investigate similar issue with Teams Webhook reporting success but not posting anything.

    None of us wanted to look at it so been in our backlog for a whilr