Test your request signature (B2B debug)
Runs the exact same HMAC-SHA256 verification pipeline as the enforcing endpoints, but ALWAYS returns 200 with a field-by-field diagnostic instead of an opaque 401. Use it to validate your signing implementation before calling business endpoints: send any JSON body signed exactly as you would a real request, then compare received_body with the bytes you signed and recompute HMAC-SHA256 over signed_payload_string locally to compare against your own v1. For security the server does NOT return its computed signature. Never takes any business action regardless of payload. Rate-limited to 20 requests/minute per client.
Headers
Client API Key
The signature under test. Format: t=,v1=. Omitting it is allowed — the diagnostic will report missing_signature_header.
Body
Any JSON payload — hashed byte-for-byte, never parsed as business data
The body is of type object.