home.social

#restapis — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #restapis, aggregated by home.social.

  1. Several "good-to-remember" questions - both for software developers and technical writers focused on API documentation:

    "REST APIs power most of the internet's integrations. Whether you are applying for a backend role, a full stack position, or a software engineering job, you will likely face questions about REST API design, HTTP methods, and authentication patterns.

    In this guide, I will walk you through the questions interviewers actually ask. I have organized them by difficulty level and role type, so you can focus on what matters most for your target position. Each answer includes practical examples and, where relevant, code snippets you can adapt.

    One thing to keep in mind: interviewers test fundamentals far more often than advanced topics. If you nail the basics (HTTP methods, status codes, statelessness), you will handle most REST API interviews confidently. The fancy architectural patterns come later."

    datacamp.com/blog/rest-api-int

    #APIs #REST #RESTAPI #RESTAPIs #Programming #API #SoftwareDevelopment #TechnicalWriting

  2. "Getting to this point isn’t unusual. Clients clearly think they’re making the call correctly, or else they would fix the endpoint themselves. Some misspellings are difficult to catch. The enum USER_RETREIVE may not be noticed from USER_RETRIEVE, especially if picking it from a list. Misspellings happen and they’re not always caught before making it to the contract. As an aside, that’s why it’s important writers routinely check development’s changes. This applies, too, to our testing calls in Postman, where manually entering endpoints and values are more pervasive.

    The reason this isn’t caught is simple: We’re not expecting it.

    For our testing, the call is made and we get results. We may even spot check some of them. But generally, results aren’t examined that closely. For instance, how often do you so carefully examine a returned list of 50 or 100 items? You check may check that the objects are complete but not that the list conforms to the search criteria.

    The reason this happens is because of an intentional behavior on the server. This behavior is called Lenient Handling or Strict Handling."

    robertdelwood.medium.com/under

    #APIs #RESTAPIs #Rest #APITesting #APIDesign #APIDocumentation #SoftwareDevelopment