Enable REST access
Apply the Studio migrations and enable the API inconfig/media-studio.php:
php artisan media-studio:permissions to create the permission definitions, then assign studio.api.use and, for people who issue tokens, studio.api.manage through Spatie Permission. Existing file, folder, comment and workspace permissions continue to apply.
Open AI → API & SDK inside Studio, select the intended workspace and create a token. A token cannot create access to a workspace that its owner cannot already use.
First request
docs/api/openapi.json in the package checkout) to your own application before using an interactive request builder. No shared hosted API or public demo credential is provided.
Available operations
Browse files and folders, read originals and conversions, upload files, resume chunk uploads, use S3 Multipart when configured, update metadata, manage manual tags, trash and restore entries, prepare downloads, and work with notes and comments. The reference only includes registered REST operations. Account administration, token management, source imports, workspace creation and billable AI analysis are not exposed through REST tokens. Token management uses the signed-in Studio interface. These boundaries are separate from the configurable MCP tools.Pagination and updates
Listings use bounded cursor pagination. PassnextCursor unchanged with the same filters for the next page. Do not interpret or store it as a permanent bookmark. File updates require the most recently read revision; a conflict returns 409 instead of overwriting newer changes.
Use Idempotency-Key for ordinary file uploads and the documented retry key for resumable uploads, notes and comments. Do not automatically retry arbitrary writes.