TBBN Developers

post/v1/reputation/seller-reviews

Review the other trader after a person-to-person trade

curl -X POST https://api.tbbnetwork.com/v1/reputation/seller-reviews \
  -H "Authorization: Bearer <session access token>" \
  -H "Idempotency-Key: 5f2f...b91" \
  -H "Content-Type: application/json" \
  -d '{
  "tradeSessionId": "a1b2c3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
  "rating": 1,
  "comment": "comment",
  "tags": [
    "accurate"
  ]
}'

Request body

Field	Type	Required
tradeSessionId	string (uuid)	yes
rating	integer	yes
comment	string	—
tags	string[]	—

Possible errors

Any other failure (validation, auth, rate limiting, a resource that doesn't exist) returns this same envelope with a non-2xx status — error.code is stable and safe to branch on; error.requestId is worth logging and including in a support request.

Example error response

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "A human-readable description of what went wrong.",
    "requestId": "req_01hxyz..."
  }
}

get/v1/reputation/seller-reviews/trades/{tradeSessionId}

Your view of a trade's reviews

curl -X GET https://api.tbbnetwork.com/v1/reputation/seller-reviews/trades/{tradeSessionId} \
  -H "Authorization: Bearer <session access token>" \

Parameters

tradeSessionId

path

required

Possible errors

Any other failure (validation, auth, rate limiting, a resource that doesn't exist) returns this same envelope with a non-2xx status — error.code is stable and safe to branch on; error.requestId is worth logging and including in a support request.

Example error response

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "A human-readable description of what went wrong.",
    "requestId": "req_01hxyz..."
  }
}

post/v1/reputation/seller-reviews/{id}/reply

Reply once, publicly, to a published review of you

curl -X POST https://api.tbbnetwork.com/v1/reputation/seller-reviews/{id}/reply \
  -H "Authorization: Bearer <session access token>" \
  -H "Idempotency-Key: 5f2f...b91" \
  -H "Content-Type: application/json" \
  -d '{
  "reply": "reply"
}'

Parameters

id

path

required

Request body

Field	Type	Required
reply	string	yes

Possible errors

Any other failure (validation, auth, rate limiting, a resource that doesn't exist) returns this same envelope with a non-2xx status — error.code is stable and safe to branch on; error.requestId is worth logging and including in a support request.

Example error response

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "A human-readable description of what went wrong.",
    "requestId": "req_01hxyz..."
  }
}