Local API overview
The SessionDock Local API is a local-first JSON API served by the desktop app itself. It is designed to automate the same domain concepts that SessionDock’s UI works with every day.
Guardrails
- bound only to
127.0.0.1 - bearer token required on every request
- JSON for both success and error responses
- mode-aware writes with read-only and full-automation separation
Endpoint families
Core session resources
Use the sessions endpoints to list, fetch, create, patch, and delete session records. These are the backbone of most integrations.
Session metadata surfaces
Notes and tags are part of the session object model. Dedicated notes and tags endpoints exist for tools that want narrower write access patterns.
Preview and waveform surfaces
Preview metadata, preview audio, waveform peaks, and waveform note markers let external tools build rich listening or review workflows without launching a DAW.
Desktop automation actions
The open and focus actions bridge from data automation back into the desktop app experience.
Import automation
The import endpoint lets external tooling queue large ingestion jobs and attach metadata up front.
Common response envelope patterns
Most success responses are shaped as:
{
"data": {
"id": "session_123",
"title": "Launch cue prep"
}
}
Errors use a shared envelope:
{
"error": {
"status": 403,
"code": "read_only",
"message": "Enable Full Automation to create sessions."
}
}
Where to go next
- Authentication for token handling and mode behavior
- Sessions Endpoints for the main CRUD surface
- Preview Endpoints for playback and waveform workflows
- API Reference for endpoint-by-endpoint contract details