V1 API
Compatibility reference and direct access to the established JSON-based API documentation.
The V1 API remains available for existing JSON jobs, uploads and media tools. The V2 API is a separate HTML-first product surface and never silently converts a V1 document. The full legacy documentation remains available at docs.jsoncut.com.
Existing reference
- Open the interactive V1 Swagger reference
- Download the V1 OpenAPI document
- Browse the complete legacy guides and examples
Existing integrations can remain on their versioned
/api/v1/...routes. There is no migration contract between the two formats: adopt the V2 API for new HTML-first projects or templates when it suits the workflow. Useful V1 metadata tools, including video duration and media inspection, remain supported; new integrations should use V2 media inspection.
V1 developer surface
The generated Swagger reference remains authoritative for request and response schemas. This compact index keeps the established developer routes discoverable inside the new documentation.
| Area | Operations |
|---|---|
| Jobs | POST /api/v1/jobs, GET /api/v1/jobs, GET /api/v1/jobs/{jobId}, DELETE /api/v1/jobs/{jobId} |
| Validation | POST /api/v1/jobs/validate, GET /api/v1/schemas, GET /api/v1/schemas/image, GET /api/v1/schemas/video |
| Media tools | POST /api/v1/tools/video/duration, POST /api/v1/tools/audio/duration and their /bulk variants |
| Files | POST /api/v1/files/upload, GET /api/v1/files, GET /api/v1/files/{fileId}, DELETE /api/v1/files/{fileId} |
| File delivery | GET /api/v1/files/{fileId}/download, GET /api/v1/files/{fileId}/stream, POST /api/v1/files/{fileId}/public-link |
| File validation | POST /api/v1/files/validate/image, /video and /audio; GET /api/v1/files/supported-types |
| API keys | POST /api/v1/api-keys, GET /api/v1/api-keys, GET /api/v1/api-keys/{apiKeyId}, DELETE /api/v1/api-keys/{apiKeyId} |
| V1 AI helper | POST /api/v1/ai/media-config, GET /api/v1/ai/usage |
Account, authentication and legacy billing routes are also preserved in the generated reference. New automation should not depend on those Studio-oriented legacy routes.
V1 MCP clients use https://mcp.jsoncut.com/legacy/mcp. New clients use https://mcp.jsoncut.com/mcp; the two tool surfaces are intentionally separate.
These docs do not duplicate the complete generated schema because the existing Swagger reference remains the source of truth for legacy request and response fields.