Confirm Active Plan Price Change

Confirm and apply price change for an active plan.

POST /merchant/plan/active_price_change/confirm

Confirm Active Plan Price Change

cURL

curl --request POST \
  --url https://api.unibee.dev/merchant/plan/active_price_change/confirm \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "confirmOldAmount": 123,
  "newAmount": 123,
  "planId": 123,
  "reason": "<string>"
}
'

200

{
  "code": 123,
  "data": {
    "activeAffectedSubscriptions": 123,
    "newAmount": 123,
    "oldAmount": 123,
    "planId": 123,
    "totalAffectedSubscriptions": 123
  },
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Endpoint Overview

POST https://api.unibee.dev/merchant/plan/active_price_change/confirm

Confirm and apply price change for an active plan.

---

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
confirmOldAmount	integer	Yes	Old amount expected by caller, used for optimistic locking
newAmount	integer	Yes	New amount (in smallest currency unit, e.g. cents)
planId	integer	Yes	Target planId, must be active
reason	string	No	Reason or note for this price change

---

Request examples

cURL

curl -X POST "https://api.unibee.dev/merchant/plan/active_price_change/confirm" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "confirmOldAmount": 0,
  "newAmount": 0,
  "planId": 0,
  "reason": ""
}'

Sandbox

curl -X POST "https://api-sandbox.unibee.top/merchant/plan/active_price_change/confirm" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "confirmOldAmount": 0,
  "newAmount": 0,
  "planId": 0,
  "reason": ""
}'

---

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.activeAffectedSubscriptions	integer	Active/processing subscriptions whose future billing will be affected
data.newAmount	integer	New amount after change
data.oldAmount	integer	Old amount before change
data.planId	integer	Target planId
data.totalAffectedSubscriptions	integer	Total subscriptions that have used or are using this plan (by status set)
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

Confirm and apply price change for an active plan.

confirmOldAmount · integer<int64> · required

Old amount expected by caller, used for optimistic locking

newAmount · integer<int64> · required

New amount (in smallest currency unit, e.g. cents)

planId · integer<int64> · required

Target planId, must be active

reason · string<string>

Reason or note for this price change

Response

200 - application/json

code · integer<int>

data · object

Show child attributes

merchantId · integer<int64>

message · string<string>

redirect · string<string>

requestId · string<string>