Procore Sandboxes

Overview

Procore offers three sandboxes that serve two distinct purposes:

For building — the Development Sandbox, where developers build and test the integration.
For customer trial and testing — On-Demand Sandbox and Monthly Sandbox, where Procore customers trial or test the integration inside their own Procore accounts.

This page explains how each sandbox works and when to use it.

Note: Every developer building on Procore can use a Development Sandbox. On-Demand Sandbox and Monthly Sandbox are part of a Procore customer’s account — only Procore customers can enable them. If you’re a Procore customer building your own integration, you can use both: a Development Sandbox to build, and your company’s On-Demand or Monthly Sandbox to test on real data.

Compare the Sandboxes

Sandbox	Primary user	Set up by	Refresh model	Multi-sandbox	Best for
Development Sandbox	App developer	Auto-created when an app is registered in the Developer Portal	Never — register a new app to start fresh	Yes — one per app	Building and testing the integration
On-Demand Sandbox	A Procore customer’s Company Admin	Self-enabled in Procore Explore	Customer-controlled — no automatic refresh	Yes — multiple parallel sandboxes	Trialing the integration on real customer data, with full control
Monthly Sandbox	A Procore customer’s Company Admin	Enabled in company General Settings	Automatic monthly refresh from Production	No — one shared per company	Trialing the integration against a recent production snapshot

Development Sandbox: For App Building

The Development Sandbox is the primary environment for building and testing an integration. It’s separate from Production, comes pre-loaded with seed data, and uses its own OAuth credentials.

What’s included

When you register a new app in the Developer Portal, a Development Sandbox is generated within a few minutes. You’ll receive an email to set your sandbox password.

Each Development Sandbox includes:

A minimum set of users in the Company Directory: Test Architect, Test Subcontractor, and API Support, each with example email addresses (for example, sandbox+arch@example.com). To add more, see Add a User Account to the Company Directory.
A starter project named 1234 – Sandbox Test Project with seed data: three project users, eight Schedule Tasks, a basic folder structure, one Photo, a Drawing Set, one RFI, and one Submittal.

Endpoints

Resource	URL
Authentication base URL	`https://login-sandbox.procore.com`
API and browser base URL	`https://sandbox.procore.com`

Use the Sandbox OAuth credentials (Client ID and Client Secret) from your app’s configuration page in the Developer Portal.

Working with the Development Sandbox

Once your sandbox is ready, you can:

Retrieve your client_id and client_secret from the Sandbox OAuth Credentials section of your app’s configuration.
Request an access token using OAuth, then make API requests to https://sandbox.procore.com (for example, https://sandbox.procore.com/rest/v1.0/me).
Sign in to the Procore web UI with the credentials you set after receiving the sandbox welcome email, and add or modify data through the Procore tools.

Next: Choose your OAuth grant type and walk through the Quick Start Guide to make your first API call.

Important considerations

Development Sandboxes can’t be refreshed or deleted, but you can have many of them. To start with a clean environment, register a new app to get a fresh Development Sandbox, then migrate your app setup. Each new Development Sandbox has its own company_id, so update your app’s connection to point to the new sandbox.

On-Demand and Monthly Sandboxes

Note: A Company Admin needs to enable Monthly Sandbox or On-Demand Sandbox in a Procore customer’s account before the integration can be tested in either one.

On-Demand and Monthly Sandboxes are both enabled by a Company Admin and use Production OAuth credentials — so the integration uses the same Client ID and Client Secret it does in Production. Each new sandbox needs the integration installed separately, and the OAuth connection should be verified after each install.

On-Demand Sandbox

When to use it: A Procore customer wants to trial or test the integration on their own data, on their own schedule, with the option to spin up multiple parallel sandboxes. This is Procore’s recommended sandbox for most testing scenarios.

How it’s enabled: A Company Admin self-enables On-Demand Sandbox in Procore Explore. See the customer guide (for Procore customers): Create and Manage an On-Demand Sandbox.

Setup notes: Each new On-Demand Sandbox needs the integration installed separately. After installation, verify the OAuth connection succeeds.

Important: Each On-Demand Sandbox has its own company_id. To your app, every sandbox looks like a separate customer company. Install the app in each new sandbox.

What you need to know:

On-Demand Sandbox runs on Production infrastructure with the same Production endpoints (https://api.procore.com, https://login.procore.com) and Production OAuth credentials.
Each On-Demand Sandbox is independent. A Company Admin must install the app separately in each one. Plan for this if multiple sandboxes are in use.
Sandboxes are managed on the customer’s schedule (create and use as needed), and data is not wiped on a fixed cadence.

Monthly Sandbox

When to use it: A Procore customer wants to trial or test the integration against a full-database snapshot of their Production account, doesn’t need multiple parallel sandboxes, and is comfortable with a monthly refresh that wipes all sandbox-only changes.

How it’s enabled: A Company Admin enables Access to the Monthly Sandbox Environment in the company’s General Settings.

Setup notes: Plan the Production install with the next monthly refresh in mind. After the refresh, verify the OAuth connection succeeds.