Apps

Verify a presigned-URL upload landed in S3

Changed on

Confirm a bundle uploaded via a presigned PUT URL actually landed in S3.

S3 returns an empty body on a successful PUT — the ETag is only in response headers, which browser clients often can't read due to CORS. This endpoint does a server-side HEAD and returns {etag, size_bytes, last_modified, exists} so clients can verify the upload before calling /deploy.

post/v1/apps/{app_id}/deploy/verify-upload

Request

  • Base URL: https://api.mixpeek.com
  • URL: https://api.mixpeek.com/v1/apps/{app_id}/deploy/verify-upload
  • Auth: HTTP bearer

Path parameters

app_idstring required

Request body

bundle_s3_keystring required

S3 key returned by /deploy/upload-url — the object you just PUT to.

Response

Successful Response

bundle_s3_keystring required

S3 key that was verified

existsboolean required

True if the object exists in S3

etagstring nullable

S3 ETag of the uploaded object (MD5 for single-part uploads).

size_bytesinteger nullable

Size of the uploaded object in bytes.

last_modifiedstring nullable

Last-modified timestamp (ISO 8601).

Changes

  • 61a175e8eb9aRevision changes
    • warning

      removed the optional property from the response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the optional property to the response with the status

    • info

      added the required property to the response with the status

    • info

      added the required property to the response with the status

  • 5d4c905106b4Revision changes
    • info

      the endpoint scheme security BearerAuth was added to the API