Skip to main content
Hosted Verify and the SDK’s client.verify() sign for you. Use this reference when you call POST /api/v1/verification directly or debug a SIGNATURE_VERIFICATION_FAILED response. The signature authenticates the exact request, not the later verifier outcome. Proofable returns a qHash and the complete portableProof envelope to the creator.

Raw HTTP

  1. Build the verification JSON body you will submit.
  2. POST /api/v1/verification/standardize with that body to get signerString, the exact bytes to sign.
  3. Sign signerString.
  4. POST /api/v1/verification with the same body plus signature.
Sign only what standardize (or the SDK’s standardizeVerificationRequest) returns for that exact body. Never hand-edit the message.

Troubleshooting

  • Re-run /standardize on the same payload and compare signerString to what the wallet signed.
  • walletAddress, verifierIds, data, signedTimestamp, and chain fields must match between standardize and submit.
  • Every data field is bound, so keep nonces and timestamps in data when recomputing qHash.

Shape

UTF-8, LF newlines.

SDK helpers

Wallets

The envelope format is defined in CAIP-380.
Last modified on October 25, 2026