Marketplace feedback
Marketplace feedback is what a buyer leaves about an order on a marketplace: eBay feedback and Amazon reviews. Replyco collects it for each connected account. Through the API you can search it, which suits a report on negative feedback or a watch on new reviews. It’s read-only here.
Fields that matter
Section titled “Fields that matter”| Field | Meaning |
|---|---|
id |
The feedback’s id. Pass it to GET /openapi/thread/byfeedback/{feedbackId} for the related tickets. |
commentType |
The rating: 0 Positive, 1 Neutral, 2 Negative, 3 CustomCode, 4 IndependentlyWithdrawn, 5 Withdrawn. |
amazonRating |
The star rating on Amazon, 1 to 5. It is 0 for other marketplaces. |
commentText |
What the buyer wrote. |
commentingUser |
The buyer’s marketplace username. |
creationDate |
When the feedback was left on the marketplace, in UTC. startDate and endDate filter on this date. |
accountId |
The connected account (integration) it belongs to. |
customerId |
The Replyco customer. |
orderId |
The Replyco order, when the feedback could be matched to one. Otherwise null. |
itemTitle, itemPrice, itemCurrency |
The item the feedback is about. |
unread |
Whether your team has read it in Replyco. |
Listing and filtering
Section titled “Listing and filtering”POST /openapi/feedback/paged takes its settings in the body, and every one is optional. Filters combine, so a result
matches all of them. You only get feedback for the accounts your user can access. The user also needs the Feedbacks view
permission in Replyco. Without it the call answers 403.
| Parameter | What it does | Default | Limits |
|---|---|---|---|
page |
The page to return, from 1. | 1 | Lower than 1 is rejected with 400. |
count |
Items per page. | 50 | 1 to 100; anything else is rejected with 400. |
term |
Searches the buyer’s username, name, email and marketplace id, the comment, and the item’s title and marketplace id. | none | — |
sort |
creationDate, commentingUser, commentType, commentText or accountId. |
creationDate |
Any other value sorts by creationDate. |
asc |
true for ascending, false for descending. |
false |
— |
accountFilter |
Only this account. | all your user’s accounts | An account your user can’t access gives an empty page. |
commentTypeFilter |
Only this rating, as a number from the table above. | all | — |
marketplaceFilter |
Only these marketplaces. | all | — |
startDate, endDate |
Only feedback left in this range, in UTC, both ends included. | no limit | startDate after endDate is rejected with 400. |
curl -X POST https://open-api.replyco.com/openapi/feedback/paged \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{"page": 1, "count": 50, "commentTypeFilter": 2, "startDate": "2026-11-01T00:00:00Z", "endDate": "2026-11-07T23:59:59Z"}'{ "page": 1, "count": 50, "commentTypeFilter": 2, "startDate": "2026-11-01T00:00:00Z", "endDate": "2026-11-07T23:59:59Z"}{ "totalRecords": 1, "pageSize": 50, "pagesCount": 1, "currentPage": 1, "data": [ { "id": "3b8f2c1e-6d4a-4f7b-9a2e-5c1d7e9f0a3b", "orderId": "6a1c3e5f-7b9d-4c2e-8f1a-3d5b7c9e1f2a", "customerId": "2f4a6c8e-0b1d-4e3f-a5c7-9e1b3d5f7a9c", "accountId": "8c0e2a4f-6b8d-4a1c-9e3f-5b7d9f1c3e5a", "creationDate": "2026-11-03T14:22:00Z", "commentingUser": "buyer_4821", "commentText": "Parcel arrived late.", "commentType": 2, "amazonRating": 0, "itemTitle": "Ceramic mug, set of 4", "itemPrice": 24.5, "itemCurrency": "GBP", "unread": true } ]}Read pages up to pagesCount. A page past the end answers 200 with an empty data list and a totalRecords of 0, so
take the totals from a page that has data. One user can call this operation 15 times a minute. See Rate limits.
To work on a complaint, find its tickets. Pass the id to GET /openapi/thread/byfeedback/{feedbackId}, or the
orderId to GET /openapi/thread/byorder/{orderId}. See Tickets.
Operations
Section titled “Operations”| Method | Path | Summary | Scopes |
|---|---|---|---|
| POST | /openapi/feedback/paged |
Search feedback | — |
Errors
Section titled “Errors”| Status | Meaning | Returned by |
|---|---|---|
| 400 | Invalid paging or date range. The response body carries the reason in its ‘error’ field | POST /openapi/feedback/paged |
| 401 | User is not authenticated or authorized | POST /openapi/feedback/paged |
| 403 | User does not have the Feedbacks view permission | POST /openapi/feedback/paged |
Related
Section titled “Related”- Tickets: the conversations behind a piece of feedback.
- Orders: the orders feedback is linked to.
- Pagination and filtering: how paged lists work.