The Fraud Consortium by AtData was created to detect and monitor fraudulent email statuses and history within our platform and network. Our partners can update profile statuses and report confirmed fraud using a dedicated API. If you come across any fraudulent activity, report it to AtData.

Why Submit Fraud Feedback?

Reporting fraudulent activity to AtData helps to:

  • Prevent similar frauds from happening in the future by keeping track of past fraud reports.
  • Improve the accuracy of our fraud detection models by incorporating new fraud trends.

How to Submit Feedback?

The Submit Feedback API is how you can contribute to AtData's continuous improvement by reporting detected fraudulent activity. Your feedback helps enhance the accuracy and effectiveness of our fraud prevention measures, benefiting all users.

To use the Submit Feedback API, you will add your API key as a query parameter in the URL. This is exemplified below:

https://api.atdata.com/feedback/v1?api_key=<YOUR_API_KEY>

Remember to replace <YOUR_API_KEY> with the API key created in Getting started's Step 2. Also, you will need to send a tab-separated file in the request. The recipe below shows an example code using Python to perform this request:

This tab-separated file can have the fields presented below:

FieldDescription
query_id*The UUID from the original query to the fraud API (if applicable).
reference_idClient’s reference Id.
email*Email address.
md5_email*MD5 hashed email address.
risk_levelHigh/Medium/Low.
firstFirst name.
lastLast name.
streetAddress line 1.
street2Address line 2.
cityCity.
stateState.
zipZip code.
ipIP address.
phonePhone number.
risk_typeCategory of risk or fraud identified by the client (e.g., credit card, chargeback, account takeover, etc.).
sourceHow the feedback was determined (e.g., rule, manual review, chargeback).
timeThe date the fraud occurred in ISO-8601 format with time and time zone.
commentThe optional text field provides context to the risk level for analysis, reporting, and modeling.

📘

*Required fields

At least one of query_id, email, or md5_email must be included to ensure each submission can be uniquely identified and properly processed.