You can create and save a request from the:

  • Workspaces build view
  • New button
  • Launch screen

Using the New Button

  1. In the header toolbar, click the New button.

    new button

    The "Create New" screen appears.

    create screen

  2. In the SAVE REQUEST screen:

    • Enter a title and description for your request.
    • Select a collection and save the request in it.
    • Click the Save button.

After you save the request, you can add the URL, method, headers, and body to the request in the builder.

Using the Launch screen

The "Create New" screen appears by default when you launch Postman. At the bottom of the screen you can select "Show this window at launch" to indicate whether you want the "Create New" screen to display each time you open Postman.

  1. Open Postman.
  2. In the "Create New" screen, click "Request".
  3. In the SAVE REQUEST screen:

    • Enter a title and description for your request.
    • Select a collection and save the request in it.
    • Click the Save button.

Using Workspaces build view

In Workspaces, you can create any kind of HTTP request quickly. The four parts of an HTTP request are the URL, method, headers, and the body. Postman gives you tools to work with each of these parts.



When you enter the request URL in the URL input field, previously-used URLs will show an autocomplete dropdown.

Click the Params tab to open the data editor for URL parameters. When you add key-value pairs, Postman combines everything in the query string above. If your URL already has parameters - for example, if you are pasting a URL from some other source. Postman splits the URL into pairs automatically.

Note: Parameters you enter in the URL bar or in the data editor will not automatically be URL-encoded. Right click a piece of selected text, and select "EncodeURIComponent" to manually encode the parameter value.

Note: Postman automatically adds http:// to the beginning of the URL if no protocol is specified.

url and parameters section

Some API endpoints use path variables. You can work with those in Postman. Below is an example of a URL with a path variable:

To edit the path variable, click on Params to see it already entered as the key. Update the value as needed. For example, :entity can be “user” in this specific case. Postman also gives you suggestions to autocomplete the URL.

edit path variables


Clicking on the Headers tab shows the headers key-value editor. You can set any string as the header name. The autocomplete dropdown provides suggestions of common HTTP headers, as you type in the fields. Values for the “Content-Type” header are also available in an auto-complete drop down.

autocomplete headers

Note on restricted headers: If you're using the Postman Chrome app, some headers are restricted by Chrome and the XMLHttpRequest specification. However, sending restricted headers is simple using the Interceptor extension.  


You can manage Cookies in native apps by using the cookie manager to edit cookies associated with each domain. To open the modal, click the Cookies link under the Send button. For more information, see Managing cookies.

manage cookies modal

Header presets

You can save commonly used headers together in a header preset. Under the Headers tab, you can add a header preset to your request when you select "Manage Presets" from the Presets dropdown on the right.  

preset headers


Use the control dropdown to change the request method. The request body editor area changes depending on whether the method can have a body attached to it.

url methods

You can also customize the methods the way you want. To learn more about customizing methods, refer to creating custom methods section.

Request Body

While constructing requests, you'll work frequently with the request body editor. Postman lets you send almost any kind of HTTP request. The body editor is divided into six areas and has different controls, depending on the body type.

Note about Headers: When you are sending requests through the HTTP protocol, your server might expect a Content-Type header. The Content-Type header allows the server to parse the body properly. For form-data and urlencoded body types, Postman automatically attaches the correct Content-Type header so you don't have to set it. The raw mode header is set when you select the formatting type. If you manually use a Content-Type header, that value takes precedence over what Postman sets. Postman does not set any header type for the binary body type.

'None' option

Postman defaults to 'none' option whenever you send a request. Choose this option if you don't want to send body with your request. If your request has a body, you may choose an appropriate option available there. The default body option appears as below:

body none



multipart/form-data is the default encoding a web form uses to transfer data. This simulates filling a form on a website, and submitting it. The form-data editor lets you set key-value pairs (using the data editor for your data.) It also lets you specify the content type for each part of a multi-part form request individually. You can attach files to a key as well.

When you repeatedly make API calls that require sending these files again and again, Postman persists your file paths for subsequent use. This also helps you run collections that contain requests requiring file upload.

Uploading multiple files each with their own Content-Type is not supported yet.

URL encoded

urlencoded data

This encoding is the same as the one used in URL parameters. You just need to enter key-value pairs and Postman will encode the keys and values properly. Note that you cannot upload files through this encoding mode. There might be some confusion between form-data and urlencoded so make sure to check with your API first.

Raw request

raw data

A raw request can contain anything. Postman doesn’t touch the string entered in the raw editor except replacing environment variables. Whatever you put in the text area gets sent with the request. The raw editor lets you set the formatting type along with the correct header that you should send with the raw body. You can set the Content-Type header manually too and this will override the Postman defined setting. Selecting XML/JSON in the editor type enables syntax highlighting for your request body and also sets the Content-Type header.

Tip: Selecting text in the editor and pressing CMD/CTRL + B can beautify the XML/JSON content automatically.

Binary data

binary data

Binary data allows you to send things which you can not enter in Postman, for example, image, audio, or video files. You can send text files as well.

GraphQL query

Authoring and sending a GraphQL query in Postman is simple. The following screen illustrates sending a GraphQL query in Postman using the new body type GraphQL:

binary data

To send a GraphQL query, ensure you're present in the Body tab and then select GraphQL (shown above in red circle). Enter your GraphQL query in the Query section and send your request. The GraphQL body type provides a rich user interface for authoring and sending requests. The Editor enables you to author both queries and variables separately, as illustrated in the above screen. Refer to the Using GraphQL section for more information on GraphQL and how to enable Autocomplete feature powered by Postman API schemas.

Custom settings for requests

Postman allows specific configurations for individual requests via the "Settings" tab under request builder view. It provides a number of settings that enable the user to send requests to non-standard API or requests that need logic not present in the request sending algorithm by selecting them from a set of options for every request.

Request settings

Following is a list of options provided by request settings tab:

Setting Description
Automatically follow redirects Choose whether or not to let requests that return a 300-series response to be automatically redirected.
Remove referrer header on redirect Remove the referrer header when a redirect happens.
Preserve authorization header on redirect Retain authorization header when a redirect happens to a different hostname.
Follow original HTTP Method Turn it on to redirect with the original HTTP method instead of the default behavior of redirecting with GET.
Use server cipher suite during handshake  Use the server's cipher suite order instead of the client's during handshake.
Protocols disabled during handshake Specify the SSL and TLS protocol versions to be disabled during handshake. All other protocols will be enabled.
Cipher suite selection Order of cipher suites that the SSL server profile uses to establish a secure connection.
Maximum number of redirects Set a limit on the maximum number of redirects to follow.