Sandbox and Production

Use sandbox for development and integration testing. Use the matching base URL and credentials together for every request, including token acquisition.

Environment	API base URL
Sandbox	https://sandbox-api.siteservicesnow.com/api/v1
Production	https://api.siteservicesnow.com/api/v1

Guide examples use paths relative to these base URLs. The OpenAPI reference instead selects a host and includes /api/v1 in each operation path; do not add that prefix twice.

Sandbox and production have separate credentials, API data, and webhook subscriptions. Project/item references, resource IDs, and subscription IDs must come from the environment where you will use them. Do not copy identifiers or secrets from one environment into the other, or assume a sandbox reference is valid in production.

Sandbox writes create retained records; sandbox is not a dry-run mode. An active subscription can receive events from those writes. Coordinate test records and any cleanup with SSN. Onboarding packets may already contain a validation site and visit: read those existing IDs rather than creating the same records again.

Before production use, obtain the production credential and approved scopes, confirm production references through /projects and /items, and configure a production webhook receiver if needed. Follow the same authentication, retry, and webhook verification rules in both environments.