Provided free and as is, without warranty of any kind — including merchantability, fitness for a particular purpose, and the accuracy or completeness of any result. See the licence. You are responsible for checking what this produces before relying on it.
communicationnexmopaymentsearch
Nexmo Verify
Nexmo Verify is an API service, now part of Vonage, for verifying users with one-time codes sent by SMS, voice, or other channels.
Base URL: https://api.nexmo.com/verify
Auth: bearer (pass your key via the apiKey input)
Operations
verifysearch — GET /search/{format} — Verify Search
verifycheck — POST /check/{format} — Verify Check
verifycontrol — POST /control/{format} — Verify Control
networkunblock — POST /network-unblock — Request a network unblock
verifyrequest — POST /{format} — Request a Verification
Inputs
apiKey — your nexmo-verify API key
operation — one of the operations above
path parameters when an operation's path contains {...}
query — optional JSON object of query params
body — JSON object for create/update ops
Example
operation: verifysearch
apiKey: <your key>
Publishes
The keys a later task may reference as {{taskName.key}}. Referencing anything not listed here resolves to nothing at run time.
error
operation
result
status
Input Properties
Every property this tool accepts, from its own tool.iml.
Property
Type
Required
Default
Description
apiKey
string
yes
—
DEPRECATED — bind an API Key credential to the task with credentialName instead. A key pasted here is stored in the workflow definition in clear and appears in every export of it. Still honoured for workflows built before the change.
operation
string
yes
—
One of: verifysearch, verifycheck, verifycontrol, networkunblock, verifyrequestwithpsd2, verifyrequest
format
string
no
—
Path parameter format (required by some operations).
query
string
no
—
Optional query params as a JSON object string, e.g. {"limit": 10}.
body
string
no
—
Request body as a JSON object string (for create/update operations).