Seal

Release-Datei per GitHub-Actions-OIDC-Token versiegeln

Seals a release file: anchors poe/<sha256> on the Doichain with repository, ref and commit taken from a GitHub Actions OIDC token (Authorization: Bearer <token>, audience 'doichain-seal', job permission id-token: write). No API key is needed, the quota counts per repository and day (DOI_SEAL_PER_REPO_DAY) with a shared daily limit (DOI_SEAL_PER_DAY). Responds 201 with the new anchoring, or 200 if the hash was already anchored (then the existing proof is returned and the file is only recorded in the seal index). Repository, ref, commit and file name become public on the chain. Error texts of this endpoint are English because they appear in workflow logs.

post/v1/seal/github

Request

  • Base URL: https://doi-api.sendlabs.de (the document declares no server; this is the origin it was published from)
  • URL: https://doi-api.sendlabs.de/v1/seal/github
  • Auth: none declared

Request body

hashstring required

SHA-256 of the release file, 64 hex characters

filenamestring nullable

File name as published (public on the chain), at most 80 characters

sizeinteger nullable

File size in bytes (only stored in the seal index, not on the chain)

notestring nullable

Optional note, at most 60 characters (public on the chain)

Example request

{
  "hash": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
}

Response

Hash war schon verankert, bestehender Nachweis

Changes

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