Screen an email for phishing

post/v1/ai/fraud/email-phishing

Request

Base URL
https://api.intura.co (the document declares no server; this is the origin it was published from)
Auth
none declared

Request body

bodystring required

The message body, plain text or HTML. HTML is worth sending as-is: an anchor whose text and href name different domains is one of the strongest signals available, and flattening to text destroys it. Bounded by the module's MAX_CHARS.

subjectstring nullable

The subject line. Scored together with the body, because phishing subjects carry much of the urgency.

senderstring nullable

The From header, with or without a display name. Compared against reply_to and against the brand the message claims to be.

reply_tostring nullable

The Reply-To header. A registrable domain that disagrees with sender is evidence an attacker cannot remove by rewriting copy.

display_namestring nullable

The sender's display name, if you have it separately from sender. Sending it inside sender works just as well.

thresholdsobject nullable

Move the cuts for this one call: block (default 0.75) and review (default 0.45). Either alone is fine; the other keeps Intura's default.

Example request

{
  "body": "Akun BCA anda akan diblokir dalam 24 jam. Verifikasi identitas anda sekarang: <a href=\"https://secure-bca.xyz/login\">bca.co.id</a>",
  "subject": "PENTING: Akun anda akan diblokir",
  "sender": "\"BCA Security\" <admin@secure-bca.xyz>",
  "reply_to": "collect@mail.ru",
  "display_name": "BCA Security",
  "thresholds": {
    "block": 0.8,
    "review": 0.5
  }
}

Response

Successful Response

statusstring

Always success on a 2xx

codeinteger

Mirrors the HTTP status code

Changes

No recorded changes to this operation across all 1 revision of this API.