Abnormal Security

App · 25 actions

Act on what Abnormal Security, the AI email security platform, finds: read and remediate threats, acknowledge account takeover cases, review emails employees report, check vendors and employees, and report emails it got wrong. Start a workflow when a threat, case, reported campaign or vendor case arrives.

Actions

ActionWhat it does
Get AI Security Mailbox campaignGet a campaign employees reported: its subject, sender, who received it, when it was reported and Abnormal's judgement.
Get caseGet an account takeover case: its status, severity, the employee it's about, its threats and Abnormal's summary.
Get case action statusCheck whether a change to a case is done, still running, or failed.
Get case analysisGet what Abnormal noticed about a case, such as impossible travel, and its timeline of sign-ins, mail rules and emails sent.
Get employeeGet an employee's name, job title and manager, as Abnormal knows them.
Get employee identity analysisGet what's usual for an employee, such as the IP addresses, devices and places they sign in from, to compare a suspicious sign-in with.
Get employee sign-insGet an employee's sign-ins over the last 30 days: when, from where, with which app and device, and whether each worked.
Get message remediation historyGet each remediation status one email has had, such as Auto-Remediated, and the folder it's in now.
Get threatGet a threat (an email campaign): its subject, sender, kind of attack, and each recipient's copy with its remediation status.
Get threat action statusCheck whether a remediation request on a threat is done, still running, or failed.
Get threat linksList the links in a threat's emails, with their domains, such as to block them in a web filter.
Get vendorGet a vendor's risk level, the people on each side who email, where its email comes from and Abnormal's analysis.
Get vendor activityGet what Abnormal has seen from a vendor: attacks from its domain, signals from other customers, and what Abnormal did.
Get vendor caseGet a vendor case: the vendor, what Abnormal noticed, and the emails involved.
List AI Security Mailbox campaignsList the IDs of campaigns employees reported to AI Security Mailbox (formerly Abuse Mailbox).
List audit logsList who did what in the Abnormal portal, such as viewing an email or remediating a threat.
List casesList account takeover cases, by when they last changed.
List misclassification reportsList the false positives or missed attacks your organization reported (Detection 360), with where Abnormal is with each and its analysis.
List reported emails not analyzedList emails employees reported to AI Security Mailbox that Abnormal did not analyze, such as phishing simulations, and why.
List threatsList the IDs of threats in Abnormal's threat log, by when they were received or remediated, the kind of attack, sender, recipient or subject.
List vendor casesList the IDs of vendor cases: vendors whose email looks compromised.
List vendorsList the vendors your organization emails with, riskiest first.
Remediate threatTake a threat's emails out of every inbox, or put them back.
Report misclassified emailTell Abnormal it flagged a safe email (a false positive), or missed an attack, spam or graymail, so it can review it.
Update case statusAcknowledge a case (in progress, attack resolved or not an attack), mark it as needing action, or record that you remediated it yourself.

Get AI Security Mailbox campaign

Get a campaign employees reported: its subject, sender, who received it, when it was reported and Abnormal's judgement.

Inputs

Campaign IDcampaigntextRequired
The reported campaign's ID, such as fff51768-c446-34e1-97a8-9802c29c3ebd, from 'List AI Security Mailbox campaigns' or a trigger.

Outputs

attack_typetext
The kind of attack, for malicious or spam ones
campaign_idtext
The campaign's ID
first_reportedtext
When it was first reported (ISO 8601)
from_addresstext
The sender's email address
from_nametext
The sender's display name
judgementtext
Abnormal's judgement, such as Malicious
last_reportedtext
When it was last reported (ISO 8601)
message_idtext
Its first message's ID in Abnormal
recipient_addresstext
The recipient's email address
recipient_nametext
The recipient's display name
subjecttext
Its first email's subject
threat_idtext
The threat it matches in the threat log; empty if none
Example output
{
  "attack_type": "Malicious: Phishing",
  "campaign_id": "fff51768-c446-34e1-97a8-9802c29c3ebd",
  "first_reported": "2020-11-11T13:11:40-08:00",
  "from_address": "support@secure-reply.org",
  "from_name": "Support",
  "judgement": "Malicious",
  "last_reported": "2020-11-11T13:11:40-08:00",
  "message_id": "-1234567891011121314",
  "recipient_address": "example@example.com",
  "recipient_name": "Tom",
  "subject": "Fwd: This is spam",
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}

Get case

Get an account takeover case: its status, severity, the employee it's about, its threats and Abnormal's summary.

Inputs

Case IDcasetextRequired
The case's ID, such as 1234, from 'List cases' or a trigger.

Outputs

affected_employeetext
The employee it's about
ai_summarylist
Abnormal's AI-written summary, point by point
analysistext
Abnormal's analysis
case_idtext
The case's ID
confidencetext
How sure Abnormal is: LOW, MEDIUM or HIGH
customer_visible_timetext
When the case was shown to you (ISO 8601)
first_observedtext
When the behaviour was first seen (ISO 8601)
remediation_statustext
Not remediated, remediated or Remediation attempted
severitytext
What kind of case it is, such as Potential Account Takeover
severity_leveltext
NONE, LOW, MEDIUM or HIGH
statustext
Its status, such as Action Required
tenanttext
The tenant it's in
threat_idslist
The threats tied to it
Example output
{
  "affected_employee": "FirstName LastName",
  "ai_summary": [
    "Sign-in from a new country followed by a new mail rule."
  ],
  "analysis": "Signs in from an unusual location.",
  "case_id": "1234",
  "confidence": "HIGH",
  "customer_visible_time": "2020-06-09T17:42:59Z",
  "first_observed": "2020-06-09T17:42:59Z",
  "remediation_status": "Not remediated",
  "severity": "Potential Account Takeover",
  "severity_level": "HIGH",
  "status": "Action Required",
  "tenant": "my-tenant",
  "threat_ids": [
    "184712ab-6d8b-47b3-89d3-a314efef79e2"
  ]
}

Get case action status

Check whether a change to a case is done, still running, or failed.

Inputs

Case IDcasetextRequired
The case's ID, such as 1234, from 'List cases' or a trigger.
Request IDaction_idtextRequired
The request's action_id, from 'Update case status'.

Outputs

action_idtext
The request's ID
case_idtext
The case
descriptiontext
What Abnormal says about it
donetrue/false
True once the request has finished
statustext
acknowledged, in_progress, done or error
Example output
{
  "action_id": "61e76395-40d3-4d78-b6a8-8b17634d0f5b",
  "case_id": "1234",
  "description": "The request was completed successfully",
  "done": true,
  "status": "done"
}

Get case analysis

Get what Abnormal noticed about a case, such as impossible travel, and its timeline of sign-ins, mail rules and emails sent.

Inputs

Case IDcasetextRequired
The case's ID, such as 1234, from 'List cases' or a trigger.

Outputs

case_idtext
The case
eventslist
The flagged events, as Abnormal's timeline lists them
insightslist
What Abnormal noticed
Example output
{
  "case_id": "1234",
  "events": [
    {
      "category": "Sign In Event",
      "description": "Suspicious Failed Sign In Attempt for foo@bar.com",
      "details": {
        "browser": "Chrome",
        "operating_system": "Windows 10"
      },
      "ip_address": "123.456.78.900",
      "location": "Aldie, Virginia, US",
      "timestamp": "2020-05-19T17:47:30Z",
      "title": "Suspicious Failed Sign In Attempt"
    }
  ],
  "insights": [
    {
      "description": "Signed in from two countries an hour apart.",
      "signal": "Impossible Travel"
    }
  ]
}

Get employee

Get an employee's name, job title and manager, as Abnormal knows them.

Inputs

Employee emailemailtextRequired
The employee's email address, such as tom@example.com.

Outputs

emailtext
Their email address
managertext
Their manager's email address
nametext
Their name
titletext
Their job title
Example output
{
  "email": "example@example.com",
  "manager": "manager_email@example.com",
  "name": "Tom",
  "title": "General Manager"
}

Get employee identity analysis

Get what's usual for an employee, such as the IP addresses, devices and places they sign in from, to compare a suspicious sign-in with.

Inputs

Employee emailemailtextRequired
The employee's email address, such as tom@example.com.

Outputs

countnumber
How many traits
emailtext
The employee
traitslist
What's usual for them, trait by trait
Example output
{
  "count": 1,
  "email": "example@example.com",
  "traits": [
    {
      "description": "Common IP Addresses for user logins",
      "key": "ip_address",
      "name": "Common IP Addresses",
      "values": [
        {
          "count": 9,
          "share": 0.9,
          "value": "203.12.172.182"
        }
      ]
    }
  ]
}

Get employee sign-ins

Get an employee's sign-ins over the last 30 days: when, from where, with which app and device, and whether each worked.

Inputs

Employee emailemailtextRequired
The employee's email address, such as tom@example.com.

Outputs

countnumber
How many sign-ins
emailtext
The employee
loginslist
Their sign-ins in the last 30 days
Example output
{
  "count": 1,
  "email": "example@example.com",
  "logins": [
    {
      "app_display_name": "Office 365 Exchange Online",
      "app_id": "00000002-0000-0ff1-ce00-000000000000",
      "browser": "Chrome",
      "city": "Sydney",
      "client_app_used": "Browser",
      "country_or_region": "AU",
      "device_id": "",
      "ip_address": "203.12.172.182",
      "latitude": "-33.86",
      "longitude": "151.20",
      "operating_system": "Windows 10",
      "resource_display_name": "Office 365 Exchange Online",
      "state": "New South Wales",
      "status": "Success",
      "timestamp": "2026-11-04T08:15:02Z",
      "user_display_name": "Tom",
      "user_principal_name": "example@example.com"
    }
  ]
}

Get message remediation history

Get each remediation status one email has had, such as Auto-Remediated, and the folder it's in now.

Inputs

Message IDmessage_idtextRequired
The email's message_id, from 'Get threat', or its page in the Abnormal portal.

Outputs

folder_locationslist
The mailbox folders it's in now, such as Junk
historylist
Each remediation status it has had, oldest first
latest_statustext
Its most recent remediation status
message_idtext
The message
Example output
{
  "folder_locations": [
    "Junk"
  ],
  "history": [
    {
      "at": "2023-04-11T20:54:56.244716+00:00",
      "status": "Auto-Remediated"
    }
  ],
  "latest_status": "Auto-Remediated",
  "message_id": "4551618356913732076"
}

Get threat

Get a threat (an email campaign): its subject, sender, kind of attack, and each recipient's copy with its remediation status.

Inputs

Threat IDthreattextRequired
The threat's ID, such as 184712ab-6d8b-47b3-89d3-a314efef79e2, from 'List threats' or a trigger.

Outputs

attack_strategytext
How it attacks, such as Name Impersonation
attack_typetext
The kind of attack, such as Phishing: Credential
attack_vectortext
What carries the attack, such as Link
from_addresstext
The sender's address, from its first message
from_nametext
The sender's name, from its first message
impersonated_partytext
Who it pretends to be, if anyone
message_countnumber
How many of its messages are listed
messageslist
Its messages, one per recipient
portal_urltext
Its first message's page in the Abnormal portal
received_timetext
When its first message arrived (ISO 8601)
recipient_countnumber
How many people received it
remediation_statustext
Its first message's remediation status
subjecttext
Its subject, from its first message
tenant_nametext
The tenant it was found in
threat_idtext
The threat's ID
Example output
{
  "attack_strategy": "Name Impersonation",
  "attack_type": "Extortion",
  "attack_vector": "Text",
  "from_address": "support@secure-reply.org",
  "from_name": "Support",
  "impersonated_party": "None / Others",
  "message_count": 1,
  "messages": [
    {
      "attachment_count": 1,
      "attachment_names": [
        "attachment.pdf"
      ],
      "attack_score": 0.97,
      "attack_strategy": "Name Impersonation",
      "attack_type": "Extortion",
      "attack_vector": "Text",
      "attacked_party": "VIP",
      "auto_remediated": true,
      "cc_emails": [
        "cc@example.com"
      ],
      "from_address": "support@secure-reply.org",
      "from_name": "Support",
      "impersonated_party": "None / Others",
      "internet_message_id": "<5edfca1c.1c69fb81.4b055.8fd5@mx.google.com>",
      "is_read": true,
      "judgement": "Attack",
      "message_id": "4551618356913732076",
      "portal_url": "https://portal.abnormalsecurity.com/home/threat-center/remediation-history/4551618356913732076",
      "post_remediated": false,
      "received_time": "2020-06-09T17:42:59Z",
      "recipient_address": "example@example.com",
      "remediation_status": "Auto Remediated",
      "remediation_time": "2020-06-09T17:42:59Z",
      "reply_to_emails": [
        "reply-to@example.com"
      ],
      "return_path": "support@secure-reply.org",
      "sender_domain": "secure-reply.org",
      "sender_ip_address": "100.101.102.103",
      "sent_time": "2020-06-09T17:42:59Z",
      "subject": "Phishing Email",
      "summary_insights": [
        "Bitcoin Topics",
        "Personal Information Theft"
      ],
      "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2",
      "to_addresses": "example@example.com, another@example.com",
      "url_count": 1,
      "urls": [
        "https://www.google.com/"
      ]
    }
  ],
  "portal_url": "https://portal.abnormalsecurity.com/home/threat-center/remediation-history/4551618356913732076",
  "received_time": "2020-06-09T17:42:59Z",
  "recipient_count": 2,
  "remediation_status": "Auto Remediated",
  "subject": "Phishing Email",
  "tenant_name": "example-tenant",
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}

Get threat action status

Check whether a remediation request on a threat is done, still running, or failed.

Inputs

Threat IDthreattextRequired
The threat's ID, such as 184712ab-6d8b-47b3-89d3-a314efef79e2, from 'List threats' or a trigger.
Request IDaction_idtextRequired
The request's action_id, from 'Remediate threat'.

Outputs

action_idtext
The request's ID
descriptiontext
What Abnormal says about it
donetrue/false
True once the request has finished
statustext
acknowledged, in_progress, done or error
threat_idtext
The threat
Example output
{
  "action_id": "a33a212a-89ff-461f-be34-ea52aff44a67",
  "description": "The request was completed successfully",
  "done": true,
  "status": "done",
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}

List the links in a threat's emails, with their domains, such as to block them in a web filter.

Inputs

Threat IDthreattextRequired
The threat's ID, such as 184712ab-6d8b-47b3-89d3-a314efef79e2, from 'List threats' or a trigger.

Outputs

countnumber
How many links
linkslist
The links in its messages
threat_idtext
The threat
Example output
{
  "count": 1,
  "links": [
    {
      "display_text": "This is not a spoof!",
      "domain": "lamronba.com",
      "link_type": "html href",
      "message_id": "4551618356913732076",
      "source": "body",
      "url": "http://spoof.lamronba.com"
    }
  ],
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}

Get vendor

Get a vendor's risk level, the people on each side who email, where its email comes from and Abnormal's analysis.

Inputs

VendorvendortextRequired
The vendor's domain, such as vendor.com.

Outputs

analysislist
Abnormal's analysis of the vendor
company_contactslist
Your mailboxes that deal with the vendor
countrieslist
Where the vendor's emails come from
domaintext
The vendor's domain
ip_addresseslist
The IP addresses the vendor's emails come from
risk_leveltext
Its risk level, such as High; empty unless details asked
tenant_nametext
The tenant it's in
vendor_contactslist
The vendor's mailboxes your people deal with
Example output
{
  "analysis": [
    "Vendor compromise observed in Abnormal Community"
  ],
  "company_contacts": [
    "bob@company.com"
  ],
  "countries": [
    "United States"
  ],
  "domain": "vendor.com",
  "ip_addresses": [
    "127.0.0.1"
  ],
  "risk_level": "High",
  "tenant_name": "example-tenant",
  "vendor_contacts": [
    "alice@vendor.com"
  ]
}

Get vendor activity

Get what Abnormal has seen from a vendor: attacks from its domain, signals from other customers, and what Abnormal did.

Inputs

VendorvendortextRequired
The vendor's domain, such as vendor.com.

Outputs

countnumber
How many events
domaintext
The vendor's domain
eventslist
The vendor's activity, as Abnormal's timeline lists it
Example output
{
  "count": 1,
  "domain": "vendor.com",
  "events": [
    {
      "action_taken": "Post Remediated",
      "attack_goal": "malware and ransom",
      "domain_ip": "",
      "event_type": "Targeted Attack",
      "has_engagement": false,
      "ip_country": "",
      "recipient": "bob@company.com",
      "suspicious_domain": "alice@vendor.com",
      "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2",
      "timestamp": "2021-01-01T00:00:00Z"
    }
  ]
}

Get vendor case

Get a vendor case: the vendor, what Abnormal noticed, and the emails involved.

Inputs

Vendor case IDvendor_casetextRequired
The vendor case's ID, such as 42, from 'List vendor cases' or a trigger.

Outputs

domaintext
The vendor's domain
first_observedtext
When its first message arrived (ISO 8601)
insightslist
What Abnormal noticed
last_modifiedtext
When the case last changed (ISO 8601)
timelinelist
The emails involved
vendor_case_idtext
The vendor case's ID
Example output
{
  "domain": "vendor.com",
  "first_observed": "2020-06-09T17:42:59Z",
  "insights": [
    {
      "description": "The sender's domain imitates the vendor's.",
      "highlight": "Look-alike domain"
    }
  ],
  "last_modified": "2020-06-09T17:42:59Z",
  "timeline": [
    {
      "marked_as": "Malicious",
      "recipient": "bob@company.com",
      "sender": "alice@vendor.com",
      "subject": "Click Me!",
      "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2",
      "timestamp": "2021-01-01T00:00:00Z"
    }
  ],
  "vendor_case_id": "42"
}

List AI Security Mailbox campaigns

List the IDs of campaigns employees reported to AI Security Mailbox (formerly Abuse Mailbox). Without dates, the last 24 hours.

Inputs

Fromsincedate and time
Only campaigns on or after this date and time.
Tountildate and time
Only campaigns on or before this date and time.
Dates aredate_fieldtext
Which date From and To are about. Defaults to when it was last reported.One of: lastReportedTime (When it was last reported), receivedTime (When its first email was received).
Sendersendertext
Words in the sender's name or address.
Recipientrecipienttext
Words in the recipient's name or address.
Subjectsubjecttext
Words in the email's subject.
Reporterreportertext
Words in the reporter's name or address.
Attack typeattack_typetext
The kind of attack Abnormal judged it.One of: Internal-to-Internal Attacks (Email Account Takeover), Spam, Reconnaissance, Scam, Social Engineering (BEC), Phishing: Credential, Invoice/Payment Fraud (BEC), Malware, Extortion, Phishing: Sensitive Data, Other.
Judgementjudgementtext
What Abnormal judged it.One of: All (Any), Malicious, Spam, Safe.
Sort bysort_bytext
Defaults to when it was last reported.One of: lastReportedTime (When it was last reported), receivedTime (When its first email was received).
Ordersort_ordertext
Defaults to newest first.One of: desc (Newest first), asc (Oldest first).
How manylimitnumber
The most to list on a page, up to 500. Defaults to 100.From 1 to 500.
Pagepagenumber
Which page to list, from 1. A list's next page is in its next_page.At least 1.

Outputs

campaignslist
The reported campaigns found, by ID
countnumber
How many are listed
next_pagenumber
The next page to ask for; 0 when this is the last
pagenumber
The page listed
Example output
{
  "campaigns": [
    {
      "campaign_id": "fff51768-c446-34e1-97a8-9802c29c3ebd"
    }
  ],
  "count": 1,
  "next_page": 0,
  "page": 1
}

List audit logs

List who did what in the Abnormal portal, such as viewing an email or remediating a threat. Abnormal keeps 90 days.

Inputs

Fromsincedate and time
Only entries on or after this date and time.
Tountildate and time
Only entries on or before this date and time.
Categorycategorytext
Only these areas of the portal, separated by spaces, such as threat_log abuse_mailbox.
Actionaction_nametext
Only these actions, separated by spaces, such as view_message_content.
Resultstatustext
Only what succeeded, or what failed.One of: SUCCESS (Succeeded), FAILURE (Failed).
Source IPsource_iptext
Only what was done from this address.
How manylimitnumber
The most to list on a page, up to 100. Defaults to 100.From 1 to 100.
Pagepagenumber
Which page to list, from 1. A list's next page is in its next_page.At least 1.

Outputs

audit_logslist
The audit log entries
countnumber
How many are listed
next_pagenumber
The next page to ask for; 0 when this is the last
pagenumber
The page listed
Example output
{
  "audit_logs": [
    {
      "action": "view_message_content",
      "category": "threat_log",
      "message_id": "4551618356913732076",
      "reason": "Investigating a reported email",
      "recipient": "example@example.com",
      "request_url": "",
      "sender": "support@secure-reply.org",
      "source_ip": "203.0.113.7",
      "status": "SUCCESS",
      "subject": "Phishing Email",
      "tenant_name": "example-tenant",
      "timestamp": "2026-11-05T10:02:11Z",
      "user_email": "analyst@example.com"
    }
  ],
  "count": 1,
  "next_page": 0,
  "page": 1
}

List cases

List account takeover cases, by when they last changed. Needs Abnormal's Account Takeover product.

Inputs

Fromsincedate and time
Only cases changed on or after this date and time.
Tountildate and time
Only cases changed on or before this date and time.
How manylimitnumber
The most to list on a page, up to 500. Defaults to 100. Counts only when a date is given.From 1 to 500.
Pagepagenumber
Which page to list, from 1. A list's next page is in its next_page.At least 1.

Outputs

caseslist
The cases found
countnumber
How many are listed
next_pagenumber
The next page to ask for; 0 when this is the last
pagenumber
The page listed
Example output
{
  "cases": [
    {
      "case_id": "1234",
      "confidence": "HIGH",
      "created": "2020-06-09T17:42:59Z",
      "description": "Potential Account Takeover",
      "first_observed": "2020-06-09T17:42:59Z",
      "last_modified": "2020-06-09T18:02:00Z",
      "severity_level": "HIGH",
      "tenant": "my-tenant"
    }
  ],
  "count": 1,
  "next_page": 0,
  "page": 1
}

List misclassification reports

List the false positives or missed attacks your organization reported (Detection 360), with where Abnormal is with each and its analysis. Without dates, the last 30 days.

Inputs

Reports ofinquiry_typetextRequired
False positives or missed attacks.One of: FALSE_POSITIVE (False positives), MISSED_ATTACK (Missed attacks).
Fromsincedate and time
Only reports sent on or after this date and time.
Tountildate and time
Only reports sent on or before this date and time.
Statusesstatuseslist
Only reports in these statuses. Leave empty for all.One or more of: UNREVIEWED, CONTAINING_ATTACK (Containing the attack), IMPROVING_PLATFORM (Improving detection), CORRECTING_JUDGEMENT (Correcting the judgement), RESOLVED.

Outputs

countnumber
How many are listed
reportslist
Your misclassification reports
Example output
{
  "count": 1,
  "reports": [
    {
      "analysis": "The sender's new mail server looked unfamiliar.",
      "id": "5021",
      "inquiry_type": "FALSE_POSITIVE",
      "message_ids": [
        "4551618356913732076"
      ],
      "root_causes": [
        {
          "description": "The vendor moved to a new mail provider.",
          "name": "Unusual sender infrastructure"
        }
      ],
      "status": "RESOLVED",
      "submitted_at": "2026-11-02T15:20:00Z",
      "submitted_by_email": "lhching@bigcompany.com",
      "submitted_by_name": "Ching Li-Hsieh"
    }
  ]
}

List reported emails not analyzed

List emails employees reported to AI Security Mailbox that Abnormal did not analyze, such as phishing simulations, and why. Without dates, the last 90 days.

Inputs

Fromsincedate and time
Only reports on or after this date and time.
Tountildate and time
Only reports on or before this date and time.
Sort bysort_bytext
Defaults to the date reported.One of: dateReported (Date reported), subject.
Ordersort_ordertext
Defaults to newest first.One of: desc (Newest first), asc (Oldest first).

Outputs

countnumber
How many are listed
reportslist
The reported messages Abnormal did not analyze
Example output
{
  "count": 1,
  "reports": [
    {
      "message_id": "7362810024012345678",
      "reason": "PHISHING_SIMULATION",
      "recipient_email": "lhching@bigcompany.com",
      "recipient_name": "Ching Li-Hsieh",
      "reported_at": "2026-11-05T09:12:00Z",
      "reporter_email": "lhching@bigcompany.com",
      "reporter_name": "Ching Li-Hsieh",
      "subject": "Read me"
    }
  ]
}

List threats

List the IDs of threats in Abnormal's threat log, by when they were received or remediated, the kind of attack, sender, recipient or subject. Use 'Get threat' for each one's details.

Inputs

Fromsincedate and time
Only threats on or after this date and time.
Tountildate and time
Only threats on or before this date and time.
Dates aredate_fieldtext
Which date From and To are about. Defaults to when it was received.One of: receivedTime (When it was received), latestTimeRemediated (When it was last remediated).
Kindsourcetext
Attacks, borderline emails, spam, or everything. Defaults to everything.One of: all (Everything), attacks, borderline, spam.
Sendersendertext
Words in the sender's name or address.
Recipientrecipienttext
Words in the recipient's name or address.
Subjectsubjecttext
Words in the email's subject.
Topictopictext
What the email is about.One of: Billing Account Update, Covid-19 Related Attack, Cryptocurrency, Invoice, Invoice Inquiry.
Attack typeattack_typetext
The kind of attack.One of: Internal-to-Internal Attacks (Email Account Takeover), Spam, Spam Bomb, Reconnaissance, Scam, Social Engineering (BEC), Phishing: Credential, Invoice/Payment Fraud (BEC), Malware, Extortion, Phishing: Sensitive Data, Other.
Attack vectorattack_vectortext
What carries the attack.One of: Link, Attachment, Text, Others, Attachment with Zipped File, QR Code, Calendar Invite.
Attack strategyattack_strategytext
How the attack works.One of: Name Impersonation, Internal Compromised Email Account, External Compromised Email Account, Spoofed Email, Unknown Sender, Covid 19 Related Attack.
Impersonated partyimpersonated_partytext
Who the email pretends to be.One of: VIP, Assistants, Employee (other), Brand, Known Partners, Automated System (Internal), Automated System (External), Unknown Partner, None / Others.
Flagged by your own rulescustomer_overridelist
Only threats your own custom AI model, custom rules or blocklist flagged.One or more of: Custom AI Model, Custom Rule, Customer Blocklist.
How manylimitnumber
The most to list on a page, up to 500. Defaults to 100. Counts only when a date is given.From 1 to 500.
Pagepagenumber
Which page to list, from 1. A list's next page is in its next_page.At least 1.

Outputs

countnumber
How many are listed
next_pagenumber
The next page to ask for; 0 when this is the last
pagenumber
The page listed
threatslist
The threats found, by ID
Example output
{
  "count": 1,
  "next_page": 0,
  "page": 1,
  "threats": [
    {
      "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
    }
  ]
}

List vendor cases

List the IDs of vendor cases: vendors whose email looks compromised. Use 'Get vendor case' for each one's details.

Inputs

Fromsincedate and time
Only vendor cases on or after this date and time.
Tountildate and time
Only vendor cases on or before this date and time.
Dates aredate_fieldtext
Which date From and To are about. Defaults to when it last changed.One of: lastModifiedTime (When it last changed), firstObservedTime (When its first email arrived).
How manylimitnumber
The most to list on a page, up to 100. Defaults to 100. Counts only when a date is given.From 1 to 100.
Pagepagenumber
Which page to list, from 1. A list's next page is in its next_page.At least 1.

Outputs

countnumber
How many are listed
next_pagenumber
The next page to ask for; 0 when this is the last
pagenumber
The page listed
vendor_caseslist
The vendor cases found, by ID
Example output
{
  "count": 1,
  "next_page": 0,
  "page": 1,
  "vendor_cases": [
    {
      "vendor_case_id": "42"
    }
  ]
}

List vendors

List the vendors your organization emails with, riskiest first.

Inputs

Include detailsinclude_detailstrue/false
Add each vendor's risk level, contacts, countries and analysis. The token needs access to vendor details.
How manylimitnumber
The most to list on a page, up to 1,000. Defaults to 100.From 1 to 1000.
Pagepagenumber
Which page to list, from 1. A list's next page is in its next_page.At least 1.

Outputs

countnumber
How many are listed
next_pagenumber
The next page to ask for; 0 when this is the last
pagenumber
The page listed
vendorslist
The vendors, riskiest first
Example output
{
  "count": 1,
  "next_page": 0,
  "page": 1,
  "vendors": [
    {
      "analysis": [
        "Vendor compromise observed in Abnormal Community"
      ],
      "company_contacts": [
        "bob@company.com"
      ],
      "countries": [
        "United States"
      ],
      "domain": "vendor.com",
      "ip_addresses": [
        "127.0.0.1"
      ],
      "risk_level": "High",
      "tenant_name": "example-tenant",
      "vendor_contacts": [
        "alice@vendor.com"
      ]
    }
  ]
}

Remediate threat

Take a threat's emails out of every inbox, or put them back. Abnormal does it in the background: 'Get threat action status' says when it's done.

Inputs

Threat IDthreattextRequired
The threat's ID, such as 184712ab-6d8b-47b3-89d3-a314efef79e2, from 'List threats' or a trigger.
RemediationremediationtextRequired
Take the emails out of inboxes, or put them back.One of: remediate (Remediate: take it out of inboxes), unremediate (Unremediate: put it back in inboxes).

Outputs

action_idtext
The request's ID, for 'Get threat action status'
remediationtext
What was asked: remediate or unremediate
status_urltext
Where Abnormal reports the request's progress
threat_idtext
The threat
Example output
{
  "action_id": "a33a212a-89ff-461f-be34-ea52aff44a67",
  "remediation": "remediate",
  "status_url": "https://api.abnormalplatform.com/v1/threats/184712ab-6d8b-47b3-89d3-a314efef79e2/actions/a33a212a-89ff-461f-be34-ea52aff44a67",
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}

Report misclassified email

Tell Abnormal it flagged a safe email (a false positive), or missed an attack, spam or graymail, so it can review it. Abnormal's answer shows in 'List misclassification reports'.

Inputs

What happenedreport_typetextRequired
A safe email was flagged, or an unwanted one was missed.One of: false-positive (False positive: a safe email was flagged), missed-attack (Missed attack), missed-spam (Missed spam), missed-graymail (Missed graymail (unwanted bulk email)).
Portal linkportal_linktext
The flagged email's page in the Abnormal portal, such as the portal_url from 'Get threat'.Only when What happened is False positive: a safe email was flagged.
Sender emailsender_emailtext
Who sent the missed email.Only when What happened is Missed attack, Missed spam or Missed graymail (unwanted bulk email).
Recipient emailrecipient_emailtext
Who received it.Only when What happened is Missed attack, Missed spam or Missed graymail (unwanted bulk email).
Subjectsubjecttext
Its subject.Only when What happened is Missed attack, Missed spam or Missed graymail (unwanted bulk email).
Received onreceived_datedate
The day the email arrived.
Detailsdetailstext
Anything that helps Abnormal, such as who noticed and why.

Outputs

report_typetext
What was reported, such as false-positive
submittedtrue/false
True once Abnormal accepted the report
Example output
{
  "report_type": "false-positive",
  "submitted": true
}

Update case status

Acknowledge a case (in progress, attack resolved or not an attack), mark it as needing action, or record that you remediated it yourself. 'Get case action status' says when it's done.

Inputs

Case IDcasetextRequired
The case's ID, such as 1234, from 'List cases' or a trigger.
New statusnew_statustextRequired
What to set the case to.One of: action_required (Action required), acknowledge_in_progress (Acknowledged: in progress), acknowledge_resolved (Acknowledged: attack resolved), acknowledge_not_an_attack (Acknowledged: not an attack), remediated_externally (Remediated outside Abnormal).
Resolutionresolutiontext
Whether it was a real attack.Only when New status is Acknowledged: attack resolved. One of: TRUE_POSITIVE (True positive: it was an attack), FALSE_POSITIVE (False positive: it was not an attack), TRUE_FALSE_POSITIVE (True false positive), UNKNOWN.
Commentcommenttext
How it was resolved, up to 4,000 characters.Only when New status is Acknowledged: attack resolved.

Outputs

action_idtext
The request's ID, for 'Get case action status'
case_idtext
The case
new_statustext
What was asked, such as acknowledge_resolved
status_urltext
Where Abnormal reports the request's progress
Example output
{
  "action_id": "61e76395-40d3-4d78-b6a8-8b17634d0f5b",
  "case_id": "1234",
  "new_status": "acknowledge_resolved",
  "status_url": "https://api.abnormalplatform.com/v1/cases/1234/actions/61e76395-40d3-4d78-b6a8-8b17634d0f5b"
}

On this page