Skip to main content
Use test reports to check your Inbound Processing flow and Customer Resolution setup without waiting for real abuse reports to arrive. We recommend sending test reports as XARF through an API Data Channel instead of test emails. XARF is already structured, so the report doesn’t go through email parsing. If a test report doesn’t show up as expected, you know the cause is in your configuration, not in how the email was parsed.

Prerequisites

  • The XARF endpoint and API key of your Abusix Ops instance. You find both in Step 3 of the Abusix Ops Getting Started page.
  • curl to send the request.
  • Optional: jq to set the report timestamp to the current time. jq ships with recent macOS versions. On Linux, install it with your package manager.

Step 1: Create the XARF Test Report

Save the following report as xarf-test-report.json. It describes a port scan from a single IP address and uses the XARF v4 connection / port_scan type.
xarf-test-report.json
Before you send the report, replace these values:
The timestamp is when the abuse happened. If your inbound processing flow filters by age, an old timestamp can route your test report somewhere you don’t expect. Step 2 sets it to the current time.

Step 2: Set the Timestamp to Now (Optional)

Run this command in the folder that contains xarf-test-report.json. It sets timestamp and first_seen to the current UTC time and saves the result back to the file.
Run it again before each send so that every test report is current.

Step 3: Send the Test Report

Set your Data Channel API key, then send the report from the same folder:
A successful request returns HTTP 200 and the ID that Abusix assigned to the report:

Troubleshooting

Step 4: Check the Report in Abusix Ops

After the report has been processed, check where it ended up:
  • Customers: If a resolver matched the source IP to a customer, the report appears under that customer.
  • Cases: If your flow routes the report to a case group, it appears in a case.
  • Unassigned events: If the report wasn’t resolved, caused a processing error, or didn’t reach a case group, it appears here. For common causes, see Unassigned Events.
If you haven’t configured inbound processing yet, your test report most likely ends up in Unresolved and error events. Look there first.
Only the active inbound processing flow processes incoming reports. Draft flows don’t. For details, see Flow States.

Need Help?

If your test report doesn’t arrive or doesn’t show up where you expect it, contact us via the chat in app.abusix.com or at [email protected].