Feedback & refunds

Integrators and end users can submit feedback on any order. Feedback helps Relu prioritize AI improvements. If an order produced no clinical value, the same flow can also request a credit refund.

Two kinds of submissions

Both use the same endpoint (POST /feedback/) with a request_refund flag:

• request_refund=false, plain feedback. Recorded, sent to the Relu team, no credits affected.
• request_refund=true, refund request. The order enters a review state.

Refund lifecycle

1. Integrator or end user calls POST /feedback/ with request_refund=true.
2. The order's status is set to "Rejected".
3. Relu reviews and approves or rejects the refund based on the refund eligibility policy in our End-User License Agreement.
4. On approval, credits are returned to the owner organization, whoever's API key created the order, not whoever requested the refund.

Who can submit

• Integrators with scope create:refunds, via the API.
• End users in the viewer UI, via the "Report problem" button in the top bar. Requires the create:refunds scope on their user token.

Listing submissions

GET /feedback/ returns a list filtered by:

• include_option=refunds|feedback, subset to one kind
• include_processed, also include items that have already been reviewed (default: false)
• user_id / order_id, scoped queries

Related

• Submit feedback & request refunds, API walkthrough
• Orders, where "Rejected" status fits in the lifecycle