REST endpoint

Abort a multipart upload

Abort a multipart session when the client cannot finish all parts. This prevents an abandoned upload from remaining open in object storage.

DELETE/api/v1/uploads/multipart204 No Content

Use this endpoint OpenAPI spec

Authentication

Send an active Fast Transcriber API key as an HTTP bearer token.

Authorization: Bearer ft_live_replace_me

Input

Request

Use the fields below and send a JSON body.

Field	Type	Description
`key`required	string	Owned object key from prepare-upload.
`storage`required	r2 \| wasabi	Storage value from prepare-upload.
`upload_id`required	string	Multipart upload identifier to abort.

curl --request DELETE https://fast-transcriber.com/api/v1/uploads/multipart \
  --header "Authorization: Bearer $FAST_TRANSCRIBER_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
    "key": "transcriptions/user_…/recording.wav",
    "storage": "r2",
    "upload_id": "upload_…"
  }'

204 No Content

Response

Successful JSON responses use a top-level data envelope. A 204 response has no body.

Successful response has no body.

Stable envelope

Errors

API errors return a machine-readable code and message.

Status	Code	Meaning
401	`missing_api_key`	No bearer key was supplied.
401	`invalid_api_key`	The bearer key is malformed, unknown, or revoked.
400	`invalid_multipart_upload`	The upload identity is invalid or does not belong to the API account.

{
  "error": {
    "code": "invalid_multipart_upload",
    "message": "A valid owned key, storage, and upload_id are required."
  }
}

Production guidance

Implementation notes

A successful abort returns an empty response body.