Check a blob
Returns the headers GET /blobs/{hash} sends and no body, so you can check that you can read a blob and learn its type and size. Send one Range as you would to download.
bearerAuthAuthorizationBearer <token>Authenticate with an API key (marfa_k1_…) or an OAuth access token (marfa_at_…).
hash*stringThe blob's hash, sha256:<hex>. You can read a blob only if an item, edge or extension you can read references its hash, and whoever wrote that reference had uploaded the bytes or could read them. The blobs.manage permission reads every blob.
Returns the headers, with the Content-Type the blob was first uploaded under, and no body.
Returns the headers of the range you asked for, and no body. Marfa serves one range, bytes=<first>-<last> or bytes=<first>-. For any other Range, it answers 200.
validation_error: the hash is malformed.
unauthorized: the request has no credential, or its credential is not valid. For a key that has expired, details.expired_at says when it expired.
type_not_permitted: your credential reaches no type.
blob_not_found: no blob has this hash, nothing you can read references it, or no store holds its bytes.
contract_mismatch: X-Marfa-Contract names another contract version than this instance speaks, or is not a whole number. Nothing was done.
range_not_satisfiable: the range starts past the end of the blob, or ends before it starts.Content-Rangegives the blob's size.
rate_limited: you sent too many requests. Wait for the number of seconds in Retry-After, then try again.
internal_error: Marfa failed in a way it didn't expect, and the request may not have completed. Read what you changed before you repeat a write.
blob_store_unavailable: no store that holds this blob answered, so Marfa couldn't tell whether it still has the bytes. Try again later.write_contention: the database was busy, and Marfa couldn't complete the request in time. Nothing changed. Try the request again.
insufficient_storage: the disk that holds the instance's data has no room for the request, or the request would leave less free than the instance keeps in reserve. Nothing changed, unless details.write_outcome is unknown, which means the write may have landed: read what you changed before you repeat it. Free space on the disk, then try the request again.
curl -X HEAD 'http://localhost:8600/blobs/string'