--- title: "List protection events" method: GET path: "/protection/events.{format}" tags: ["protection_events"] --- # List protection events `GET /protection/events.{format}` Retrieve an ordered and paginated list of all protection events in the environment. ## Query parameters - `order` string - `since_token` string - `count` string - `state` string ## Response `200` Successful - ListProtectionEventsResponse - `events` ProtectionEventProperties[] - `updated_at` string — The time the fraud check was last updated - `created_at` string — The time the fraud check was created - `fraud_control_vendor_key` string — The token of the Fraud Control Vendor used for this check - `vendor_transaction_id` string — The transaction identifier in the vendor's system - `order_id` string — The order identifier in the vendor's system - `protection_provider_key` string — The token of the Protection Provider used for this check - `amount` number — The transaction amount checked - `currency_code` string — The currency of the funds in ISO format (e.g., USD) - `ip` string — The IP address associated with the transaction - `email` string — The email address associated with the transaction - `callback_url` string — The URL where Spreedly will attempt delivery of asynchronous results (if provided) - `test_scenario` string — The test scenario used - `acquiring_bank_fraud_rate` string — The threshold for bank fraud rate used for exemption requests - `exemption_type` string — The type of exemption requested (if applicable) - `warning` string — Any warning messages from the fraud check - `managed_order_token` string — The token of the fraud check returned by the fraud check provider - `fraud_decision` string — The fraud decision outcome (e.g., approve, decline, review) - `fraud_recommendation` string — Additional recommendation information from the fraud provider - `fraud_decision_reason` string — Reason for the fraud decision - `vendor_response` object — Detailed response from the fraud protection vendor - `forterDecision` string — The decision returned by Forter - `recommendation` string — Recommended action from the vendor - `verificationMethod` object — Methods used to verify the transaction - `decisionReason` string — Reason for the vendor's decision - `merchantPolicyId` string — Merchant policy identifier used to make the decision - `orderId` string — Order identifier in the vendor's system - `linkToEventInDashboard` string — URL to view the transaction details in the vendor's dashboard - `token` string — The token uniquely identifying the transaction at Spreedly. This token can be passed into an `authorize` or `purchase` transaction via the `sca_authentication_token` field to automatically fill its `payment_method_token` and Third Party 3DS2 fields. - `succeeded` boolean — `true` if the transaction request was successfully executed, `false` otherwise - `state` string — The current state of the authentication. Valid values are `succeeded`, `failed`, and `pending` - `message` string — A human-readable string indicating the result of the transaction - `transaction_type` string — The type of transaction; contains “Sca::Authentication” for a Spreedly 3DS Global authentication - `gateway_transaction_key` string — The Spreedly transaction token of the parent gateway transaction - `sca_provider_key` string — The SCA Provider that was used to create the authentication - `acs_transaction_id` string — The unique ID of the transaction given by the ACS server (3DS2 only) - `three_ds_server_trans_id` string — The unique ID of the transaction given by the 3DS Server (3DS2 only) - `directory_server_transaction_id` string — The unique ID of the transaction given by the directory server (3DS2 only) - `xid` string — The transaction identifier given by the 3DS Server - `three_ds_version` string — The version of 3DS that was used to authenticate the transaction - `flow_performed` string — An enumerated field that denotes what flow was most recently performed. Valid values are `frictionless`, `device_fingerprint`, `challenge`, `app_challenge`, and `not_authenticated`. - `ecommerce_indicator` string — Contains the ecommerce indicator (ECI) returned by the 3DS Server - `directory_response_status` string — The transaction status given by the directory server in the initial response. This field’s value corresponds to the `transStatus` enumeration in the EMV 3-D Secure Protocol. Valid values can be `Y`, `N`, `U`, `A`, `C`, or `R`. Please see the EMV 3-D Secure Protocol spec for more information. - `authentication_response_status` string — The most recent transaction status given received by the 3DS Server. This field’s value corresponds to the `transStatus` enumeration in the EMV 3-D Secure Protocol. Valid values can be `Y`, `N`, `U`, `A`, `C`, or `R`. Please see the EMV 3-D Secure Protocol spec for more information. - `authentication_value` string — The authentication value returned by the 3DS Server for successful authentications - `trans_status_reason` string — Provides information on why the `authentication_response_status` field has the specific value. This field’s value corresponds to the `transStatusReason` enumeration in the EMV 3-D Secure Protocol. Please see EMV 3-D Secure Protocol spec for more information. - `daf` boolean — Boolean field to indicate if the authentication request utilized Visa’s Digital Authentication Framework. - `payment_method_key` string — The token of the payment method being authenticated. This is the same as the `payment_method_token` field in the `sca_authentication` transaction request. ## Other responses - `401` — Unauthorized - `404` — Not found - `422` — Unauthorized --- [API](https://skmtc.dev/spreedly/apis/spreedly-api-v1.md) · [All operations](https://skmtc.dev/spreedly/apis/spreedly-api-v1/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/spreedly/spreedly-api-v1/revisions/72ba4e23e65c/schema)