Remove a session resource
⚠️
Preview — this feature is being built; the design below is the spec.
DELETE https://app.syntic.ai/v1/sessions/{session_id}/resources/{resource_id}Unmount a resource from the session. The underlying file, repository or memory store is not deleted. The agent sees a resource.removed event on its next turn. Writes made to a writable repository mount are lost unless the agent pushed them.
For how this fits into a full workflow, see Session resources.
Headers
| Header | Required | Value |
|---|---|---|
Authorization | Yes | Bearer <key>: a private inference key (sk_live_...). See Authentication. |
syntic-beta | Yes, while in preview | agents-2026-11-01. Without it the call fails with 400 beta_required. See Versioning. |
Path parameters
| Parameter | Type | Description |
|---|---|---|
session_id | string | The session id, starting with sesn_. |
resource_id | string | The resource id, starting with sres_. |
Response
200 OK, Content-Type: application/json
{
"id": "sres_01JCB2E4G6J8L0N2Q4S6",
"type": "session_resource",
"status": "removed",
"removed_at": "2026-11-05T11:00:00Z"
}Examples
curl -sS -X DELETE "https://app.syntic.ai/v1/sessions/sesn_01JC7M2K4P6R8T0V2X4Z/resources/sres_01JCB1D3F5H7K9M1P3R5" \
-H "Authorization: Bearer $SYNTIC_API_KEY" \
-H "syntic-beta: agents-2026-11-01"Errors
Errors use the error envelope and carry a request_id. Codes specific to this operation:
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request_error | beta_required | The syntic-beta header is missing. |
| 409 | conflict_error | session_running | The agent is mid-turn; wait for status: idle or interrupt first. |
| 404 | not_found_error | resource_not_found | No resource with this id on the session. |
| 401 | authentication_error | invalid_api_key | The key is missing, unknown, revoked or expired. |
| 429 | rate_limit_error | rate_limited | Too many requests; wait for Retry-After. See Rate-limit headers. |
Was this page helpful?