Manav signed the canonical JSON below with its server secret. Hash the JSON with HMAC-SHA256 using the MANAV_SERVER_SIGNING_SECRET and compare - if it matches, this proof is authentic.
Canonical proof JSON
{"actionPayloadHash":"67e401128ac5a84dd514df38efa2a110de7c1f15f3e313670aeb98a9fa8674b3","actionTitle":"Work session approved · global corp","actionType":"work_session","actorHandle":null,"externalReference":null,"organizationSlug":null,"signatureSlug":"mnav_sig_zetaqf4JfdMa","signedAt":"2026-06-02 13:26:18"}
Action payload hash · SHA-256 of the canonical action payload
67e401128ac5a84dd514df38efa2a110de7c1f15f3e313670aeb98a9fa8674b3
Server signature · HMAC-SHA256 over canonical JSON above
83000886157c5199dd7eeab66d9ae2a49ee05980f20716c0280f067202df46d6
Recompute it yourself
$ printf '%s' '{"actionPayloadHash":"67e401128ac5a84dd514df38efa2a110de7c1f15f3e313670aeb98a9fa8674b3","actionTitle":"Work session approved · global corp","actionType":"work_session","actorHandle":null,"externalReference":null,"organizationSlug":null,"signatureSlug":"mnav_sig_zetaqf4JfdMa","signedAt":"2026-06-02 13:26:18"}' \
| openssl dgst -sha256 -hmac "$MANAV_SERVER_SIGNING_SECRET" -hex
$ # expected: 83000886157c5199dd7eeab66d9ae2a49ee05980f20716c0280f067202df46d6