whatisgithub

What is postman-app-support?

postmanlabs/postman-app-support — explained in plain English

Analysis updated 2026-06-26

5,996Audience · developerComplexity · 2/5Setup · hard

In one sentence

The original Postman Chrome extension source and early issue tracker, a historic snapshot of the API testing tool before it became the standalone desktop app developers use today.

Mindmap

mindmap
  root((postman-app-support))
    What it was
      Chrome extension
      API testing tool
      Issue tracker
    Core features
      Request builder
      Request history
      Collections
      Environments
    Auth support
      Basic Auth
      OAuth 1.0
    Response handling
      JSON pretty-print
      XML formatting
      Image preview
    Status
      Chrome app era
      Historical reference
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Study how the original Postman Chrome extension was architected as a starting point for building your own API testing tool

USE CASE 2

Understand how request history and named collections were implemented in an early browser extension codebase

USE CASE 3

Trace how environment variable switching in API clients was first designed and implemented

USE CASE 4

Review early OAuth 1.0 and Basic Auth helper patterns as reference when building your own auth tooling

What is it built with?

JavaScriptNodeGrunt

How does it compare?

postmanlabs/postman-app-supportlakr233/vphone-cliweiye-jing/datax-web
Stars5,9965,9965,996
LanguageSwiftJava
Setup difficultyhardhardhard
Complexity2/55/54/5
Audiencedeveloperresearcherdata

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Covers the archived Chrome packaged app era, for the current Postman product visit getpostman.com rather than building from this source.

License terms not specified in the explanation, check the repository directly.

So what is it?

This repository holds the early source and support materials for Postman, an API testing tool that began as a Chrome browser extension. Postman was built to solve a practical problem: one of its creators needed to test an HTTP API and could not find a tool that felt right, so they built their own. The project started by adding two things that were missing elsewhere: a history of sent requests and the ability to organize requests into named collections. The tool lets you compose HTTP requests by filling in a URL, choosing a method (GET, POST, and so on), and adding headers or body data. Responses come back formatted for readability: JSON and XML are pretty-printed rather than shown as raw text. You can also preview image responses directly in the interface. For authentication, early versions supported Basic Auth and OAuth 1.0 helpers. A key feature is environments, which let you define a set of variables (like a base URL or API key) and swap between them. This makes it easy to point the same saved requests at a local development server, a staging server, or a production server without rewriting anything. Collections keep related requests grouped together and can include documentation written in HTML. This README covers the Chrome packaged app era of Postman, before it became a standalone desktop application. The build process described here uses Node and Grunt, and installation involved loading the extension manually in Chrome's developer mode. The repository appears to have served as an issue tracker and early codebase home rather than as the primary home of the current Postman product. If you want the current Postman platform, the README points to getpostman.com.

Copy-paste prompts

Prompt 1
I am building a Chrome extension that lets developers send and save HTTP requests. What can I learn from the original Postman Chrome extension source about structuring request history and collections?
Prompt 2
How did the early Postman Chrome extension handle environment variables so the same saved request could point at localhost or production without editing the request itself?
Prompt 3
Walk me through how the original Postman extension formatted JSON and XML responses for readability, what library or approach did it use?
Prompt 4
I want to add OAuth 1.0 support to my API client. How did the original Postman extension implement the OAuth 1.0 helper, and what does it compute before sending the request?
Prompt 5
How was the original Postman Chrome packaged app built and loaded into Chrome in developer mode? What does the Grunt build process produce and what manifest settings did it use?

Frequently asked questions

What is postman-app-support?

The original Postman Chrome extension source and early issue tracker, a historic snapshot of the API testing tool before it became the standalone desktop app developers use today.

What license does postman-app-support use?

License terms not specified in the explanation, check the repository directly.

How hard is postman-app-support to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is postman-app-support for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.