Skip to main content

PostMan: an easy-to-use REST client to test all your Web API’s

image

 

PostMan is a REST client available as a  Chrome application. It’s a very easy-to-use and developer friendly tool to test and try your Web API’s. You have lots of options to manipulate the request and it has integrated support for multiple authentication mechanisms. 

Download it here.

 
 
Features
  • Create requests quickly
    • Compact layout
    • HTTP requests with file upload support
    • Formatted API responses for JSON and XML
    • Open responses as an HTML file in a new window
    • HATEOAS support
    • Image previews
    • Request history
    • Basic and OAuth 1.0 helpers
    • Autocomplete for URL and header values
    • Key/value editors for adding parameters or header values. Works for URL parameters too.
    • Use environment variables to easily shift between settings. Great for testing production, staging or local setups.
    • Use Global variables for values which are common throughout APIs
    • Use the quick look feature to preview variables and their values before you use them
    • Keyboard shortcuts to maximize your productivity
  • Document and share APIs
    • Use collections to organize requests and share them quickly using URLs.
    • Document requests inside collections. You can even store entire HTML notes. Postman uses Bootstrap so you can use it too to style your notes.
    • Download and share collections with your team of developers.
  • Collections
    • Collections can be any group of requests. You can save any kind of request by clicking the 'Add to collection' button. While saving the request you can also add a name and a note. There is no limit on the size of the notes so it can be as detailed as possible. Collections can be downloaded and shared as a file.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...