Verify a destination from its emailed link
POST
/email-routing/destinations/verify
const url = 'https://api.nsin.ir/email-routing/destinations/verify';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"token":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.nsin.ir/email-routing/destinations/verify \ --header 'Content-Type: application/json' \ --data '{ "token": "example" }'Consumes the token from the verification mail. No authentication — the person clicking owns the destination mailbox and need not be an NSIN user; the single-use 256-bit token is the proof. Once verified, rules pointing at the destination go live within a minute.
Request Body required
Section titled “Request Body required ” Media type application/json
object
token
required
The 64-character token from the emailed link.
string
Example generated
{ "token": "example"}Responses
Section titled “ Responses ”Verified.
Media type application/json
object
email
string
verified
boolean
Example generated
{ "email": "example", "verified": true}Malformed token.
Media type application/json
The single error shape used by every endpoint.
object
error
required
Human-readable description of what went wrong.
string
Example
{ "error": "read-only API key"}The link expired or was already used.
Media type application/json
The single error shape used by every endpoint.
object
error
required
Human-readable description of what went wrong.
string
Example
{ "error": "read-only API key"}