How it works
-
Create a snapshot with
POST /providers/salesforce/create-snapshot(API key required). -
Call the returned base URL like a Salesforce instance:
https://{snapshotId}.salesforce.mock.ressl.cc -
Paths follow normal Salesforce REST (v67.0 in examples below): sObjects, describe, SOQL
/query, and so on. - Seed loads initial records into memory. Config (optional) replaces describe metadata for this snapshot. Omit config to keep the emulator’s baked describes.
-
GET /openapion the snapshot base URL returns this provider’s OpenAPI document (single-provider snapshots only).
Seed — records
seed is the world state: which sObjects exist and which rows they contain.
Recommended shape:
Seed template
Config — describe metadata
config is Salesforce describe JSON — the same shape as the emulator’s baked salesforce-describes.json.
The handler uses uploaded describes when present for an sObject; otherwise it can fall back from seeded field shapes. You decide how rich
config is; a minimal describe is enough for many evals.
Typical describe fields the mock cares about: name, label, keyPrefix, and fields[] entries with at least name, label, type (plus createable / updateable when relevant).
Config template
Example
Create a snapshot with the templates above:url. Then:
Notes
- Snapshot URLs are public but unguessable until
expiresAt. - Prefer seed-only when the baked schema is enough; add
configwhen you need a custom or reduced describe surface. - For the generic create-snapshot contract (any provider), see Create snapshot.

