Find stored blobs by hash

GET

/content/management/v1/blobs

const url = 'https://api.ebitex.io/content/management/v1/blobs';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://api.ebitex.io/content/management/v1/blobs \
  --header 'Authorization: Bearer <token>'

Answers “which of these files does the organization already hold?” for one or more SHA-256 digests of the bytes, given as repeated hash parameters (64 hex characters each, up to 100 per request). It writes nothing, so a read-only key can resolve a content model’s media ids and plan it without uploading.

A digest with no stored bytes is simply absent from the result: that is the answer, not an error. Upload the missing files with POST /blobs.

Key: a management key with content.management.read.

Authorizations

apiKey

Responses

200

{ "blobs": [ { "hash", "blobId", "contentType", "sizeBytes" } ] }

400

validation_failed: no hash, more than 100, or one that is not a 64-character hex digest (named in hash).

401

missing_api_key or invalid_api_key: no key was sent, or it is unknown, revoked or expired.

402

payment_required: the organization’s subscription needs attention.

403

scope_denied: the key lacks this route’s scope. tier_required: the Content Management API needs the Pro plan or above. ip_denied: the caller’s address is outside the key’s allowed ranges. app_not_available: Content is not enabled for the organization.

429

Rate limit or quota exceeded; Retry-After says how long to wait. too_many_failed_authentications: too many bad keys from this address.