NetBird
verify_verifications_next_channel
Advance an in-progress verification to its next channel and send a fresh passcode. Identify it with the same `to` recipient used to create it; no verification ID is required. This bypasses the resend cooldown, and earlier passcodes remain valid. `last_channel` identifies the most recent completed send. `422 NoNextChannel` means the plan is exhausted; create the verification again to resend on the current channel.
Remote bird/mcp
Remote (network-hosted)
Other tools also called verify_verifications_next_channel?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"to": {
"type": [
"null",
"object"
],
"properties": {
"email": {
"type": [
"null",
"string"
]
},
"phone_number": {
"type": [
"null",
"string"
]
}
},
"description": "The recipient to verify. Provide an email, a phone_number, or both; at least one is required. The addresses also identify the verification: a check must supply exactly the set used on the create call, so a verification created with both addresses is not found by either one alone.",
"additionalProperties": false
},
"idempotency_key": {
"type": "string",
"description": "Client-supplied deduplication key; a retry with the same key replays the original result instead of acting twice."
}
}
}