Submit PostSale Action Feedback

post

https://api.signifyd.com/v3/orders/events/postsale/actions/feedback

Use this to report the quality of a return once the item is received, inspected, or confirmed. This feedback trains Signifyd’s models and powers insights dashboards.

Use cases include:

Indicating whether returned items were fraudulent or abusive
Labeling returns that were fully legitimate
Flagging package tampering, item switches, or serial return behavior

Merchants specify granular disposition fields per item (e.g., MISSING, DAMAGED, AS_EXPECTED) and can optionally include returnOutcome (e.g., GOOD, FRAUD, ABUSIVE).

This endpoint is essential for merchants participating in Returns Insights, Returns Fraud prevention, or policy-triggered automations.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

orderId

string

required

The unique identifier for the order. This must be the same order ID originally provided in the Checkout/Sale event.

postSaleActionId

string

required

Unique identifier for this return, refund, or appeasement request.

items

array of objects

A list of products that were returned by the buyer.

items

outcome

string

enum

Final classification of the return after inspection or analysis.

GOOD - The return was legitimate. The item was received in the expected condition, and the return complied with policies.
FRAUD - The return was blatantly fraudulent. The expected item was not returned — for example, the box was empty, the item was fake, or something completely different was sent back.
ABUSIVE - The return was manipulative or excessive, but the correct item was returned. Examples include wardrobing (used then returned), bracketing, or excessive return volume that violates policy intent.

Allowed:

outcomeReason

string

Additional detail that helps explain why a return was classified as Fraud or Abuse.

feedbackAt

date-time

Timestamp indicating when the outcome was determined.

Headers

SIGNIFYD-TEAM-ID

int64

The team id requested for authentication. This should normally be omitted, as it's only relevant when auth credentials allow requests for multiple teams.

Responses

200If Feedback has been created in the Signifyd system with the same orderId and returnId, then no updates to the Feedback will occur. We will simply return the existing Feedback details.

201Feedback for the order and return is created

400Response if there was a problem with the request, such as when a required field is missing or otherwise fails validation.

401Response if the provided authentication credentials are not known or do not match what is on file for the specified user.

403Response if the authenticated user does not have permission to perform the requested action.

404Response if the requested entity can't be found.

500Response if an unexplained error occurs on the server.