How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

LangSmith sandboxes API

The sandboxes API from LangSmith — 12 operation(s) for sandboxes.

LangSmith sandboxes API is one of 73 APIs that LangSmith publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sandboxes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 17 operations across 12 paths, and defines 23 schemas. It is described by OpenAPI 3.1.0, at version 0.1.0.

Requests are made against a single base URL, /.

17 operations 12 paths 23 schemas 2 DELETE7 GET1 PATCH7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.1.0
Base URL
https://api.smith.langchain.com
Authentication
API Key, API Key, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 4

LangSmith sandboxes API declares 4 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (API Key). An API key is passed in the header as X-Tenant-Id (Tenant ID). It accepts HTTP bearer tokens (Bearer Auth). An API key is passed in the header as X-Organization-Id (Organization ID).

  • Bearer Auth — Bearer tokens are used to authenticate from the UI. Must also specify x-tenant-id or x-organization-id (for org scoped apis).

Paths & Operations 17

Across 12 paths, the API surfaces 17 operations — 2 DELETE, 7 GET, 1 PATCH, 7 POST. Each is listed below with its method, path, parameters, and response codes.

sandboxes 17
GET
/auth/sandbox-access
Get sandbox access decision
2 params → 200400401403404500
GET
/v2/sandboxes/boxes
List sandbox claims
6 params → 200400403500
POST
/v2/sandboxes/boxes
Create a sandbox claim
body → 201400409422429500504
POST
/v2/sandboxes/boxes/batch-delete
Batch delete sandbox claims
body → 200400403500
GET
/v2/sandboxes/boxes/{name}
Get a sandbox claim
1 param → 200404500
DELETE
/v2/sandboxes/boxes/{name}
Delete a sandbox claim
1 param → 204404500
PATCH
/v2/sandboxes/boxes/{name}
Update a sandbox claim
1 param body → 200404409422500
POST
/v2/sandboxes/boxes/{name}/service-url
Generate a service access token
1 param body → 200400404422500501
POST
/v2/sandboxes/boxes/{name}/snapshot
Capture a snapshot from a sandbox
1 param body → 201400403404422500
POST
/v2/sandboxes/boxes/{name}/start
Start a sandbox
1 param → 202400403404500
GET
/v2/sandboxes/boxes/{name}/status
Get sandbox claim status
1 param → 200404500
POST
/v2/sandboxes/boxes/{name}/stop
Stop a sandbox
1 param → 204400403404500
GET
/v2/sandboxes/snapshots
List snapshots
6 params → 200400403500
POST
/v2/sandboxes/snapshots
Create a snapshot
body → 201400403500
GET
/v2/sandboxes/snapshots/{snapshot_id}
Get a snapshot
1 param → 200400403404500
DELETE
/v2/sandboxes/snapshots/{snapshot_id}
Delete a snapshot
1 param → 204400403404500
GET
/v2/sandboxes/usage
Get sandbox resource usage
→ 200500

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are sandboxes.ClaimResponse (18 properties), sandboxes.UsageResponse (14 properties), sandboxes.SnapshotResponse (13 properties), sandboxes.CreateClaimPayload (9 properties). Each schema is shown below with its type and property counts.

sandboxes.ClaimListResponse
object
2 properties
sandboxes.ProxyRule
object
5 properties 2 required
sandboxes.CaptureSnapshotPayload
object
2 properties 1 required
sandboxes.UpdateClaimPayload
object
7 properties
sandboxes.ProxyHeader
object
4 properties 2 required
sandboxes.BatchDeleteResponse
object
2 properties
sandboxes.BatchDeleteSkipped
object
2 properties
sandboxes.ServiceURLPayload
object
2 properties
sandboxes.ClaimStatusResponse
object
2 properties
sandboxes.Callback
object
5 properties 3 required
sandboxes.AccessControl
object
2 properties
sandboxes.ProxyConfig
object
4 properties
sandboxes.ClaimResponse
object
18 properties
sandboxes.UsageResponse
object
14 properties
sandboxes.SnapshotResponse
object
13 properties
sandboxes.ServiceURLResponse
object
4 properties
authn.PublicAuthInfo
object
5 properties
sandboxes.ErrorResponse
object
1 property
sandboxes.CreateClaimPayload
object
9 properties
sandboxes.BatchDeleteRequest
object
1 property
sandboxes.HeaderType
string
sandboxes.SnapshotListResponse
object
2 properties
sandboxes.CreateSnapshotPayload
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

langsmith-sandboxes-api-openapi.yml Raw ↑

Other APIs LangSmith publishes across the network.

LangSmith access_policies API
LangSmith ace API
LangSmith agents API
LangSmith alert_rules API
LangSmith annotation-queues API
LangSmith api-key API
LangSmith audit-logs API
LangSmith auth API
LangSmith aws_marketplace API
LangSmith backfills API
LangSmith beacon API
LangSmith bulk-exports API
Where this information came from

This is an independent, third-party profile of LangSmith sandboxes API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.