ai.newnal.illi.artwork.ackDelivery

Device app. Acknowledges one delivery: outcome received after the whole file was downloaded, its CID, size and sha256 matched the manifest and a decoder frame was prepared without starting playback (playbackReady true); outcome failed with the failure stage otherwise. received is final and counts the work's originals as used; a failure consumes nothing. The same requestKey replays the first answer.

Details · procedure
Kindprocedure
Authorityartwork.illi.newnal.ai
Indexed

Procedure

procedure · POST

Input

application/json

blobCid

string · cid

byteSize

integer
  • minimum: 0
  • maximum: 314572800
  • maxLength: 128

deliveryId

requiredstring
  • maxLength: 64

failure

string
  • knownValues: download | size | hash | storage | metadata | decode

homeId

requiredstring · tid

outcome

requiredstring
  • knownValues: received | failed

Required true for received after complete metadata and decoder-frame verification, without starting playback.

requestKey

requiredstring

Client-chosen idempotency key (1 to 64 characters of A-Za-z0-9._:-), new for each user action and reused when the same request is sent again after a lost answer. The same key with the same input replays the first answer; the same key with other input is RequestConflict.

  • minLength: 1
  • maxLength: 64

Output

application/json

recorded

requiredboolean

false when the same acknowledgement had been recorded before.

Errors

NotMember

No description in schema.

DeliveryNotFound

No description in schema.

NotDevice

No description in schema.

DeliveryMismatch

No description in schema.

DeliveryWithdrawn

No description in schema.

RequestConflict

No description in schema.

DeliveryExpired

No description in schema.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Device app. The fixed composition version, CID, size, sha256 and download URL of one delivery. Cancelled or expired unreceived deliveries have no manifest; received versions remain accessible after retry expiry. The file and a new acknowledgement follow the same access rule.