Check one server-proxied transfer, not the stored mirror or client attestation.

Check one server-proxied transfer, not the stored mirror or client attestation.

Inputs. Path, query and header fields are listed below. No request body is required.

Outputs. See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

Errors. API JSON failures use the documented response schema. Read code, message and next; retry only when the response allows it. Auth, invalid input and missing records need a caller change.

Rate limits. Public read budgets apply by client IP and route group. This operation can have a smaller route-specific budget. Read Retry-After on 429 or retryable 503 responses.

Example setup. Use an identifier returned by the matching list, search or create operation. Sample identifiers are not a promise that a record exists.

get/api/downloads/{id}/{path}/verify-status

Request

  • Base URL: https://huggingbay.xyz
  • URL: https://huggingbay.xyz/api/downloads/{id}/{path}/verify-status
  • Auth: none declared

Path parameters

idstring required
pathstring required

Query parameters

receiptstring
ticketstring

Response

Pending means no result for this transfer; it does not negate the mirror's byteVerificationStatus. Client attestation is localHashAttested on POST download-completions.

status'pending' | 'recorded'
verificationScope'server-proxied-transfer'
serverTransferVerifiedboolean
byteVerifiedboolean

Legacy alias of serverTransferVerified. Neither stored-mirror verification nor client attestation.

byteVerifiedAtstring nullable

Changes

No recorded changes to this operation across all 1 revision of this API.