verify_email_code
Use this after create_invoice returns verification_required. Arguments: { challenge_id, code }. On success returns a verification_token. Retry create_invoice with the same arguments plus that verification_token passed in its verification_token field. The token is reusable for ~30 min, so thread the same one into every subsequent create_invoice for the same sender email until it expires. Only ever call this with a code the user gave you: attempts are capped, a handful of failures revokes the challenge and forces the user to request a new email, and a rate_limited error means stop and tell them to wait, not retry.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | The 6-character code copied from the verification email body. Drawn from the confusable-free alphabet {2,3,4,5,6,7,8,9}. Check the user's paste against that alphabet before calling — a malformed code costs one of the few attempts the challenge allows. | |
| challenge_id | Yes | The opaque challenge id surfaced by the previous `create_invoice` `verification_required` error. |