Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/HelenaLM32/ECHO/llms.txt

Use this file to discover all available pages before exploring further.

ECHO includes two parallel trust mechanisms: a review system that lets buyers rate creators after completed orders, and a formal dispute process for when an engagement does not go as expected. Both systems are designed to keep activity on-platform and give all parties a clear record of what happened.

​
Reviews

After an order is completed, the buyer can submit a review that becomes part of the creator’s public reputation on ECHO. 
POST /reviews
{
  "order_id": 99,
  "score": 4,
  "comment": "Great communication throughout. The final deliverable matched the brief closely."
}
Reviews are linked to a specific order and carry a score from 1 to 5 and an optional text comment. The author_id is set automatically from the authenticated session.

​
Viewing a creator’s reviews

EndpointReturns
GET /reviews/user/{userId}All reviews authored about a specific creator
GET /reviews/user/{userId}/averageThe creator’s average review score
The average score endpoint returns a single numeric value useful for displaying star ratings on creator profiles and search results.
Reviews are tied to orders, not to individual items. A creator’s overall rating reflects the quality of their fulfillment across all engagements, not any single listing.

​
Opening a dispute

Either party on an order can open a dispute by providing a reason. Disputes are created with a status of OPEN and remain open until an administrator closes them. 
POST /disputes
{
  "order_id": 99,
  "reason": "The delivered files do not match the agreed specification. Three revisions were requested and none were addressed."
}
The created_by_user_id is set automatically from the authenticated session.
Opening a dispute does not automatically cancel the order or stop payment processing. It flags the order for admin review. Continue communicating through the dispute thread while the case is being assessed.

​
Dispute messaging

Once a dispute is open, both parties can exchange messages within it. This creates a dedicated thread separate from the order’s regular messaging, giving administrators a focused record of the disagreement. 
POST /disputes/{disputeId}/messages
{
  "message": "Attached are the original brief and the files that were delivered. The discrepancies are highlighted."
}
Each dispute message records:
  • dispute_id — which dispute the message belongs to
  • user_id — who sent the message
  • message — the message content
Administrators can also post messages in the dispute thread as part of their mediation.

​
How disputes are resolved

An administrator reviews the full dispute record — the reason, the message thread, and the underlying order — and can add a resolution note before closing the case. 
PATCH /disputes/{disputeId}/resolve
{
  "resolution": "After reviewing the brief and deliverables, a partial refund of 50% has been issued. Both parties have been notified."
}
Closing a dispute sets closed_at to the current timestamp and marks the dispute as resolved.

​
Viewing disputes

EndpointWho can accessReturns
GET /disputes/user/my-disputesAny authenticated userYour own disputes (as buyer or creator)
GET /disputes/{disputeId}Parties to the dispute or adminsFull dispute details including messages
GET /disputes/openAdmins onlyAll currently open disputes awaiting review

​
Venue and event reviews

ECHO also has a separate review system for physical venues and events — distinct from the order review system described above. Users can rate a venue or an event after visiting, using a score from 1 to 5 with an optional comment. The target_type field specifies whether the review applies to a VENUE or an EVENT, and each user is limited to one review per target. See Events and Venues for more on how venue and event reviews work in context.

Orders and Payments

Understand the order lifecycle that precedes a review or dispute.

Disputes API

Full reference for opening disputes and managing the resolution process.

Reviews API

Full reference for submitting and querying order reviews.

Build docs developers (and LLMs) love

Get started for freeTalk to us