Get Subscription Note List

POST /merchant/subscription/admin_note_list

Get Subscription Note List

cURL

curl --request POST \
  --url https://api.unibee.dev/merchant/subscription/admin_note_list \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "subscriptionId": "<string>",
  "count": 123,
  "page": 123
}
'

200

{
  "code": 123,
  "data": {
    "noteLists": [
      {
        "createTime": 123,
        "email": "<string>",
        "firstName": "<string>",
        "id": 123,
        "lastName": "<string>",
        "mobile": "<string>",
        "note": "<string>",
        "subscriptionId": "<string>",
        "userName": "<string>"
      }
    ]
  },
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Endpoint Overview

POST https://api.unibee.dev/merchant/subscription/admin_note_list

Get Subscription Note List

---

Authorization

All UniBee Merchant API requests require authentication via API key.

Header	Required	Description
Authorization	Yes	Bearer <your_api_key>
Content-Type	Yes	application/json (for request body)

---

Parameters

Parameters for this endpoint are listed below. The schema is also shown in the Try it panel.

Request body

Name	Type	Required	Description
count	integer	No	Count Of Page
page	integer	No	Page, Start With 0
subscriptionId	string	Yes	SubscriptionId

---

Request examples

cURL

curl -X POST "https://api.unibee.dev/merchant/subscription/admin_note_list" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "count": 0,
  "page": 0,
  "subscriptionId": "id_example"
}'

Sandbox

curl -X POST "https://api-sandbox.unibee.top/merchant/subscription/admin_note_list" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "count": 0,
  "page": 0,
  "subscriptionId": "id_example"
}'

---

Response

Success responses return a JSON envelope with code, data, message, redirect, and requestId. code 0 indicates success.

Field	Type	Description
code	integer	Response code. 0 = success
data	object	Response payload
data.noteLists	array
message	string	Human-readable message
requestId	string	Request ID for support

---

Error handling

HTTP status	Meaning
400	Bad request — invalid or missing parameters. Check message in the body.
401	Unauthorized — missing or invalid API key.
404	Not found — invalid path or resource.
500	Server error — retry with backoff.

When code in the response body is non-zero, check message for details. Use requestId when contacting support.

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

subscriptionId · string<string> · required

SubscriptionId

count · integer<int>

Count Of Page

page · integer<int>

Page, Start With 0

Response

200 - application/json

code · integer<int>

data · object

Show child attributes

merchantId · integer<int64>

message · string<string>

redirect · string<string>

requestId · string<string>