Batch-check which asset hashes already exist

Given a list of SHA-256 content hashes, returns a map of each hash to its existing asset record (or null if not stored in this workspace). Lets syncing clients skip the upload round-trip for content that's already been uploaded — compute the hash locally, batch-check, then only POST the missing ones to /assets.

Max 100 hashes per request.

post/assets/check

Request body

content_hashesstring[] required

Response

Map of hash → asset record or null. Keys are the hashes from the request; values are the existing asset for that hash, or null if not found.

object required

Changes

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