Verification

Phase 1: build the standard signing string

Raw HTTP verification uses a strict two-phase handshake. First send the exact verification body here, sign the returned signerString, then submit the same body plus signature to POST /api/v1/verification.

post/api/v1/verification/standardize

Request

  • Base URL: https://api.proofable.me
  • URL: https://api.proofable.me/api/v1/verification/standardize
  • Auth: none required

Request body

walletAddressstring required

Signer wallet address. Must be the same wallet that signs the returned signerString and the same walletAddress later submitted to POST /api/v1/verification.

verifierIdsstring[] required
signedTimestampnumber required

Unix ms timestamp that becomes part of the signerString. For raw HTTP, reuse this exact value unchanged when later submitting POST /api/v1/verification.

chainIdinteger

Advanced/optional. EVM signing context; defaults to Base mainnet (8453) when omitted and remains independent from the optional protocol hub. For non-EVM, use chain (CAIP-2). For chain-specific asset claims (NFT, token, contract), set chainId inside verifier data, not here.

chainstring

CAIP-2 signer-chain identifier. Non-EVM wallets must provide it (for example solana:mainnet); EVM wallets may provide eip155:<id> or use the Base mainnet default.

signatureMethodstring

Response

OK

successtrue required

Changes

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