1. Mac Install Postman
  2. Download Postman For Mac
  3. Delete Postman Chrome App Mac Download
  4. Delete Postman Chrome App Mac Desktop

Starting Postman. After you've installed it, simply launch Postman and you will be met with the following UI: Here, you can create an account. It is not necessary but it's advised to make one, since the account allows you to save your data across devices simply by working in the app. Native Postman client installed (This tutorial uses the native Postman extension because Google plans to end support for Chrome apps for Windows, Mac, and Linux users in late 2017. If you use the Postman extension, the steps in this tutorial may be slightly different.) REST samples in the idm-samples repository. Getting Started with Dashboard API and Postman Postman is a popular graphical tool for working with REST APIs. Use this tool to explore and work with the Meraki Dashboard API quickly. Dashboard API Postman Collection Overview If you are new to programming or a seasoned software engineer, knowing what’s possible is half the battle.


Postman is a very popular platform for developing and testing REST APIs. It is a feature-rich application that can run as a Chrome app or natively in Windows or Mac OSX. We recommend Postman as a platform for exploring the Procore API and familiarizing yourself with the various resource endpoints.


The first step is to get Postman installed on your computer. Because Postman is provided as a Chrome App as well as a native application for Windows and Mac OSX, you will want to pick the installation that best fits your development environment and processes. Visit the Postman website, download the appropriate installation package, and install as instructed. The examples described in this article are based on Postman v5.3.3.

Mac Install Postman

The Postman User Interface

At first glance the Postman user interface may seem complicated and even a little intimidating. Let’s take a moment to break down the various components on the screen, focusing on the main sections that you will be working with.

  • The left-hand side of the screen provides a navigation pane where you can toggle between a History of all the API calls you run and Collections that let you organize calls into logical groupings.
  • In the right-hand portion of the screen is the Request Builder. Use the Request Builder to construct Procore API requests to send to your sandbox environment.
  • Using the drop-down in the Request Builder, select the REST Method you want to use with your request. For example, GET, POST, DELETE, etc.
  • In the adjacent address bar, enter the URL for the API endpoint that you want to target.
  • Use the Params button to open up fields where you can enter query parameters that may be required for a given endpoint.
  • Request Headers can also be specified and you can create Header Presets to store frequently used header data such as Content-Type or Authorization keys.
  • Use the lower portion of the Request Builder to enter a Request Body. The Response Body is also displayed in the lower portion of the screen.
  • Finally, use the Send button to initiate the API call in the sandbox environment.

Using Postman with Your Development Sandbox

Getting Started

After you create an App on the Developer Portal you have access to a sandbox environment you can use for development. The development sandbox is pre-poulated with a company and test project. See Sandbox Environments for additional information.

Development Sandbox Credentials

Working in a development sandbox requires using authentication credentials that are separate and distinct from the Procore production environment. The Client ID and Client Secret are unique to your sandbox and are available to use for testing your App in an isolated environment. Keep in mind that these credentials are only valid for your sandbox and are not recognized in the Procore production environment.

Development Sandbox Company Directory Users

Download Postman For Mac

In addition to the user account you use to log into the Developer Portal, a minimum set of users is included in the company directory of your development sandbox when it is first generated.

Development Sandbox Test Project

Your Development Sandbox comes pre-configured with a test project called 1234 - Sandbox Test Project. This project includes the following seed data to help get you started.

  • Project Directory - three project users (Test Architect, Test Subcontractor, and API Support as described above)
  • Schedule - basic high-level schedule with 8 tasks
  • Documents - a basic document folder structure
  • Photos - one basic ‘sandbox’ image
  • Drawings - a basic set of construction plans
  • RFIs - a single RFI record
  • Submittals - a single submittal record

Postman Collection for Development Sandbox Test Projects

We have assembled a collection of Postman requests that you can use to work with your sandbox test project seed data described above.Follow the steps below to obtain a copy of this collection and import it into Postman. Visit Getting Started with Collections to learn moreabout using collections in Postman.

  1. In the upper left-hand corner of the Postman user interface, click Import.
  2. In the Import dialog, click the Import From Link tab.
  3. Copy and paste the following link into the available field... https://www.getpostman.com/collections/9c3280c30910e433c283 ...then click Import.

The collection is imported and available for use within Postman. The collection includes requests for the following Procore API actions.

Delete Postman Chrome App Mac Download

ActionProcore API Endpoint
List Projects/vapid/projects?company_id={{company_id}}
List Project Users/vapid/projects/{{project_id}}/users
List Project Folders and Files/vapid/folders?project_id={{project_id}}
List Drawing Areas/vapid/projects/{{project_id}}/drawing_areas
List Drawings/vapid/drawing_areas/{{drawing_areas}}/drawings
List Image Categories/vapid/image_categories?project_id={{project_id}}
List Images/vapid/images?project_id={{project_id}}&image_category_id={{image_category_id}}
List RFIs/vapid/projects/{{project_id}}/rfis
List Calendar Events/vapid/calendar_events?project_id={{project_id}}
List Submittals/vapid/projects/{{project_id}}/submittals
Get Me/vapid/me

Using Environment Variables in Postman

The endpoint descriptors shown in the table above include items enclosed in double curly braces. The curly brace notation is used to denote Postman environment variables. You can use environment variables to customize the collection requests to conform to the particular details of your sandbox test project. For example, you would set the values for the {{company_id}} and {{project_id}} and variables to match the company and project IDs of your sandbox environment. Visit Setting Up an Environment with Variables to learn more about using variables in Postman. The Sandbox Test Project collection includes the following environment variables:

{{company_id}}Integer ID for the sandbox company
{{project_id}}Integer ID for the sandbox test project
{{drawing_areas}}Integer ID for drawing area in the sandbox test project
{{image_category_id}}Integer ID for the image category in the sandbox test project

Generating OAuth 2.0 Tokens in Postman


Delete Postman Chrome App Mac Desktop

Postman provides a very handy and user-friendly mechanism for generating and managing OAuth 2.0 access tokens. This alleviates the burden of having to implement a fully fleshed out OAuth 2.0 solution in your application at the outset of your development cycle. Using Postman’s OAuth 2.0 token management tool, you can dive right into making Procore Connect API calls to your sandbox test project with minimal effort. The following sections outline the steps for generating OAuth 2.0 access tokens for the Authorization Code grant type.

What You'll Need

In order to begin generating OAuth 2.0 access tokens in Postman, you will need the following items:

  • Sandbox Client ID for your application
  • Sandbox Client Secret for your application
  • The Callback URI for your application
  • The Authorization endpoint URL for the sandbox environment (https://login-sandbox.procore.com/oauth/authorize)
  • The Access Token endpoint URl for the sandbox environment (https://login-sandbox.procore.com/oauth/token)

Generating OAuth 2.0 Tokens

As you will likely use the same access tokens for each of your Postman requests, we recommend configuring authorization for an entire collection rather than individual requests. Here are the steps for configuring OAuth 2.0 authorization for a Postman collection.

  1. Locate the collection you want to configure authorization for, open the drop-down and choose Edit.

  2. In the EDIT COLLECTION dialog, select the Authorization tab.

  3. In the TYPE drop-down, choose OAuth 2.0.
  4. For the Add auth data to setting, leave the default value of Request Headers.
  5. Click the Get New Access Token button.
  6. Complete the following fields in the GET NEW ACCESS TOKEN dialog.

    • Token Name - enter a meaningful name for your access token.
    • Grant Type - choose ‘Authorization Code’.
    • Callback URL - enter the address for your application’s callback URL as registered in the Developer Portal.
    • Auth URL - enter ‘https://login-sandbox.procore.com/oauth/authorize’.
    • Access Token URL - ‘https://login-sandbox.procore.com/oauth/token’.
    • Client ID - enter the sandbox Client ID for your application as registered in the Developer Portal.
    • Client Secret - enter the sandbox Client Secret for your application as registered in the Developer Portal.
    • Scope - (n/a) no need to enter a value here.
    • State - (n/a) no need to enter a value here.
    • Client Authentication - choose ‘Send as Basic Auth header’.

  7. Click the Request Access Token button. The Procore login dialog displays.

  8. Enter a valid username and password for the Procore account you will be accessing and click OK. The MANAGE ACCESS TOKENS dialog displays.

  9. Click Use Token, then click Update in the Edit Collection dialog. You are now ready to make API calls from Postman to the Procore API.

Redirect URI Limitation in Postman Token Management Tool

It is important to note that Postman's token management tool behaves differently when you use urn:ietf:wg:oauth:2.0:oob as the redirect URI for your test application. The token management tool completes only a partial handling of urn:ietf:wg:oauth:2.0:oob by displaying an authorization code that you must then use to manually generate an access token. It does not complete the full process of creating and storing an access token within the token management tool.

Procore OAuth 2.0 Postman Collection with cURL Examples

We've put together a helpful Postman collection of cURL examples for the Procore OAuth 2.0 Authentication endpoints that you can use while you build, test, and maintain your application. Simply visit this link to view the collection and begin exploring the Procore OAuth 2.0 authentication endpoints. Each endpoint includes an explanation of its functionality along with a pre-formatted cURL example command that you can copy and paste as needed.

Postman Documentation

The Postman documentation website provides complete descriptions of all available features, compelling case studies, and comprehensive training material. Below are a number of links to useful documentation on the Postman website.

And here are some helpful Postman training videos...