Sandbox API

Name: Sandbox API
Brand: Sandbox API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting QaapiKey9 EndpointsREST

For Agents

Create, fork, update, and reset HTTP mock sandboxes and search activity across them through an API_Key header.

Connect the Sandbox API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sandbox API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Sandbox API.

Create a new mock sandbox under your account with an initial routing definition

Fork an existing sandbox to spin up an isolated copy for a feature branch

Update a sandbox's routing or stub script via PUT

Reset a sandbox's captured state to wipe assertions and recorded calls between tests

GET STARTED

Start building with Sandbox API

Explore with Jentic

View OpenAPI Document

Sandbox by getsandbox.com is an HTTP mocking and stubbing service that lets developers spin up scriptable mock servers behind their own subdomain. The v1 API exposes nine endpoints covering sandbox CRUD, fork operations to clone a sandbox into a new instance, activity search across requests, and state reset for resetting captured state between test runs. It is the control surface for managing mock servers used in contract testing, demos, and frontend development against unfinished backends.

Use Cases

Patterns agents use Sandbox API for, with concrete tasks.

★ Per-feature-branch mock servers

Engineering teams fork a baseline mock sandbox for each feature branch so frontend changes can iterate against a contract that diverges from main without touching the shared mock. The fork endpoint returns a fresh sandbox identifier the branch's CI pipeline writes into its env vars.

Fork sandbox 'payments-baseline' into 'payments-feature-x' and return the new mock URL

Reset between integration test runs

CI suites that record requests to verify behaviour need a clean slate per run. Calling DELETE /1/sandboxes/{sandboxName}/state wipes captured calls and assertions, so the next test starts from a known empty state and previous-run data does not leak across CI jobs.

Before each integration test, call DELETE /1/sandboxes/payments-mock/state to clear recorded interactions

Activity search for incident triage

When a frontend or contract test fails, engineers query sandbox activity to see exactly which inbound requests landed and what was returned. The /1/activity/search endpoint accepts URL and time filters so you can replay the failing scenario against the mock without redeploying the upstream client.

Search activity in sandbox 'payments-mock' for URLs containing '/charges' between two timestamps

AI agent for mock infrastructure ops

An ops agent connected through Jentic provisions, forks, and tears down sandboxes on demand based on chat requests like 'spin up a mock for the new auth flow'. Jentic injects the API_Key header so the agent never holds the raw credential.

Create a sandbox named 'auth-flow-mock' with a starter routing definition and return its public URL

Key Endpoints

9 endpoints — sandbox by getsandbox.

METHOD

PATH

DESCRIPTION

GET

/1/sandboxes

List sandboxes

POST

/1/sandboxes

Create a sandbox

GET

/1/sandboxes/{sandboxName}

Get a sandbox

PUT

/1/sandboxes/{sandboxName}

Update a sandbox

GET

/1/sandboxes/{sandboxName}/fork

Fork a sandbox

DELETE

/1/sandboxes/{sandboxName}/state

Reset sandbox state

GET

/1/activity/search

Search request activity

GET

/1/sandboxes

List sandboxes

POST

/1/sandboxes

Create a sandbox

GET

/1/sandboxes/{sandboxName}

Get a sandbox

PUT

/1/sandboxes/{sandboxName}

Update a sandbox

GET

/1/sandboxes/{sandboxName}/fork

Fork a sandbox

DELETE

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Sandbox API_Key values are stored encrypted in the Jentic vault. Agents receive a scoped reference and the raw header value is injected per request without entering the prompt.

Intent-based discovery

Agents search by intent such as 'fork a mock sandbox' and Jentic returns the matching Sandbox operation along with its input schema.

Time to first call

Direct Sandbox integration: a few hours to wire auth, sandbox lifecycle, and activity search. Through Jentic: under 30 minutes to search, load, and execute.

FAQs

Specific to using Sandbox API through Jentic.

What authentication does the Sandbox API use?

Sandbox uses an API key sent as the API_Key header on every request. Through Jentic the key is stored encrypted in the vault and injected per request, so it never enters your agent's prompt or logs.

Can I fork a sandbox to create an isolated copy?

Yes. GET /1/sandboxes/{sandboxName}/fork returns a new sandbox cloned from the source, including its routing and stub script. This is the supported way to create per-feature-branch mocks without re-authoring the routing from scratch.

What are the rate limits for the Sandbox API?

The OpenAPI spec does not declare explicit rate limits. Practical guidance is to avoid hammering /1/activity/search in tight polling loops and to batch sandbox lifecycle operations rather than firing them in parallel from many CI jobs at once.

How do I reset a sandbox's state between test runs through Jentic?

Search Jentic for 'reset sandbox state', load the DELETE /1/sandboxes/{sandboxName}/state schema, then execute with the sandbox name. Jentic handles the API_Key injection so the reset is one structured call.

Can I search captured request activity across sandboxes?

Yes. GET /1/activity/search accepts filters for URL and time so you can locate the exact inbound request from a failing test or demo without scrolling the full request log.

Is the Sandbox API free?

Sandbox offers a free tier with limits on simultaneous sandboxes and request volume; paid plans scale up sandbox count and storage. Check getsandbox.com for current pricing before relying on the API for production-grade test infrastructure.

Sandbox API

Connect the Sandbox API to your agent

Capabilities

Start building with Sandbox API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs