Matching algorithm

Using the Postman mock service requires the following: a collection with requests, a mock server, and saved request examples. You can save as many examples to a collection as you please, and the mock server will return these examples predictably. But how exactly does the mock decide which example to return?

Matching algorithm for mocks

To begin, let’s start with an example.

create mock diagram

When a mock is created using either the Postman Pro API or the Postman app, a call is made to the Postman servers that associates a particular collection (and environment if you choose one) with a newly created mock. The collection C1 that we just mocked is now associated with the new mock M1.

show mock diagram

When we use the mock M1 via the mock URL in the Postman app, the mock service will retrieve all saved examples from the Postman servers for that particular collection before it begins the matching process.

use mock diagram

Now that the mock service has all the saved examples for the current collection, it will now iteratively pair the incoming request with the closest matching example.

The incoming request can have several configurable variables, such as requestMethod and mockPath. The requestMethod variable corresponds to any valid HTTP request method (e.g. GET, POST,PUT, PATCH, DELETE, etc.), and the mockPath refers to any valid string path (e.g. /, /test, /test/path, /test/path/1).

The request requires an authentication header x-api-key corresponding to the Postman Pro API Key, and optionally accepts a header x-mock-response-code corresponding to the desired response code of the mock request. For example, you could request a 200, 400, 404, or 500 response for a particular endpoint.

mock configurable

Keeping these various configurable elements in mind, let’s take a look at the matching algorithm logic.

  1. Properly formatted responses Any responses that are not in the expected format are removed from the matching process.
  2. HTTP method Any responses that are not the same HTTP method type are removed from the matching process. For example: if the mock request you sent was POST to, all saved examples whose method type is not POST will be disregarded.
  3. Filter by URL The matching process will now examine each saved example, and iterate over every possibility. Compare the mockPath of the input URL with that of the saved example. If the input URL was and the example currently being examined had a URL of, the mock service would compare /test with /help. While comparing URLs, a step-by-step matching is conducted. Each consecutive step that the matching algorithm traverses reduces the matching threshold of the current example response. For example:

    • Try to match the input path with the example path exactly as it is. The max value is set as the matching threshold.
    • Try to strip trailing slashes and match the input path with the example path. The threshold is reduced by a certain value, n.
    • Try to additionally lowercase the input path and the example path The threshold is reduced by a greater value, n + m.
    • Try to additionally strip out alphanumeric ids from the input path and the example path. The threshold is reduced further, n + 2m.
    • If all steps fail, this saved example is not an eligible response.
  4. Response code If the x-mock-response-code header is explicitly provided, filter out all examples that do not have a matching response code.

  5. Highest threshold value Sort the remaining filtered responses in descending order and return the response with the highest threshold value.

And there we have it! This is how the mock service finds and returns the appropriate response to a mock request.

results matching ""

    No results matching ""