Skip to main content
Spin up a short-lived Salesforce REST mock for agents and evals. One snapshot = one org-shaped sandbox until the TTL expires.

How it works

  1. Create a snapshot with POST /providers/salesforce/create-snapshot (API key required).
  2. Call the returned base URL like a Salesforce instance: https://{snapshotId}.salesforce.mock.ressl.cc
  3. Paths follow normal Salesforce REST (v67.0 in examples below): sObjects, describe, SOQL /query, and so on.
  4. Seed loads initial records into memory. Config (optional) replaces describe metadata for this snapshot. Omit config to keep the emulator’s baked describes.
  5. GET /openapi on the snapshot base URL returns this provider’s OpenAPI document (single-provider snapshots only).
When the TTL ends, the sandbox is torn down. There is no list/delete API in v1. See also: Create snapshot, Quickstart.

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:
Response includes url. Then:

Notes

  • Snapshot URLs are public but unguessable until expiresAt.
  • Prefer seed-only when the baked schema is enough; add config when you need a custom or reduced describe surface.
  • For the generic create-snapshot contract (any provider), see Create snapshot.