Quickstart

Everything below uses the live API at https://simulation.ressl.ai. Mock traffic uses https://{snapshotId}.{provider}.mock.ressl.cc.

1. Create an API key

Sign in at simulation.ressl.ai.
Open Settings (avatar menu).
Under API keys, create a key and copy it once. It starts with rsk_ and is shown only at creation time.

Send it on every request:

Authorization: Bearer rsk_...

X-API-Key: rsk_... works too.

2. List providers you can use

curl -sS https://simulation.ressl.ai/providers/list \
  -H "Authorization: Bearer rsk_..."

Example:

{
  "providers": ["jira", "salesforce", "slack"]
}

Your list depends on what your organization is granted. Pick any slug from this array as $PROVIDER below.

3. Create a snapshot

PROVIDER=jira   # any slug from /providers/list

curl -sS -X POST "https://simulation.ressl.ai/providers/${PROVIDER}/create-snapshot" \
  -H "Authorization: Bearer rsk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "ttl": "1h",
    "seed": {}
  }'

Provisioning can take one to two minutes. Example response:

{
  "snapshotId": "snap_a1b2c3d4e5f6789012345678",
  "slug": "jira",
  "url": "https://snap_a1b2c3d4e5f6789012345678.jira.mock.ressl.cc",
  "expiresAt": "2026-07-14T12:00:00.000Z",
  "ttl": "1h"
}

Use url as the public base for your agent.

Optional: seed and TTL

Field	Purpose
`ttl`	How long the snapshot lives. Default `1h`. Forms: `15m`, `1h`, `1d`. Max `7d`.
`seed`	Initial mock data for that provider.
`config`	Provider overrides. For Salesforce: describe JSON that replaces baked metadata. Omit to keep defaults. See Salesforce.

Seed shape (recommended): top-level key equals the provider slug; nested keys are that provider’s resource names:

{
  "ttl": "2h",
  "seed": {
    "jira": {
      "projects": [{ "id": "10000", "key": "DEMO", "name": "Demo" }],
      "issues": [{ "id": "10001", "key": "DEMO-1", "summary": "Example" }]
    }
  }
}

If you omit the slug wrapper and send only the inner object, the API wraps it for you using {slug} from the path. If you omit seed, the snapshot starts empty: { "<slug>": {} }. Exact fields inside each collection depend on the provider. For Salesforce seed and config templates, see Salesforce.

4. Call the mock API

Point your client at url. Paths follow that provider’s real HTTP API.

# Example: hit the snapshot base (path depends on the provider)
curl -sS "$SNAPSHOT_URL/"

Replace $SNAPSHOT_URL with the url from the create response.

Snapshot URLs are public but unguessable. Anyone with the full URL can call the mock until it expires.

Get Started

Providers

Continuous evals

1. Create an API key

2. List providers you can use

3. Create a snapshot

Optional: seed and TTL

4. Call the mock API

Next

​1. Create an API key

​2. List providers you can use

​3. Create a snapshot

​Optional: seed and TTL

​4. Call the mock API

​Next

1. Create an API key

2. List providers you can use

3. Create a snapshot

Optional: seed and TTL

4. Call the mock API

Next