Manual Adjust Metric Limit

POST /merchant/metric/limit_adjust

Manual Adjust Metric Limit

cURL

curl --request POST \
  --url https://api.unibee.dev/merchant/metric/limit_adjust \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "amount": 123,
  "metricCode": "<string>",
  "reason": "<string>",
  "productId": 123,
  "subscriptionId": "<string>",
  "userId": 123
}
'

200

{
  "code": 123,
  "data": {
    "success": true
  },
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Endpoint Overview

POST https://api.unibee.dev/merchant/metric/limit_adjust

Manual Adjust Metric Limit

---

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
amount	integer	Yes	Adjustment amount (positive to increase, negative to decrease, cannot be 0)
metricCode	string	Yes	Metric Code
productId	integer	No	Product ID, default 0 for default product
reason	string	Yes	Reason for adjustment
subscriptionId	string	No	Subscription ID (priority, use this if you know the subscription)
userId	integer	No	User ID (alternative to subscriptionId)

---

Request examples

cURL

curl -X POST "https://api.unibee.dev/merchant/metric/limit_adjust" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "amount": 0,
  "metricCode": "",
  "productId": 0,
  "reason": "",
  "subscriptionId": "id_example",
  "userId": 0
}'

Sandbox

curl -X POST "https://api-sandbox.unibee.top/merchant/metric/limit_adjust" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "amount": 0,
  "metricCode": "",
  "productId": 0,
  "reason": "",
  "subscriptionId": "id_example",
  "userId": 0
}'

---

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.success	boolean
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

amount · integer<int64> · required

Adjustment amount (positive to increase, negative to decrease, cannot be 0)

metricCode · string<string> · required

Metric Code

reason · string<string> · required

Reason for adjustment

productId · integer<int64>

Product ID, default 0 for default product

subscriptionId · string<*string>

Subscription ID (priority, use this if you know the subscription)

userId · integer<*int64>

User ID (alternative to subscriptionId)

Response

200 - application/json

code · integer<int>

data · object

Show child attributes

merchantId · integer<int64>

message · string<string>

redirect · string<string>

requestId · string<string>