Create a plan
POST
/api/v1/profiles
prm_profiles_create
name and type are the only required fields; everything else has a schema default. A plan created with no enforce toggles on is an unlimited plan.
A quota limit does nothing until its enforce toggle is on. Setting combined_bytes_limit while enforce_combined_bytes is false leaves the plan unlimited on data, and the number sits there looking like a cap. The two always travel together.
At a glance
- Authentication
- Staff token or session
- Requires permission
-
prm_profiles_createCreate profiles - Rate limit
t_mutate
Parameters
| Parameter | Description |
|---|---|
namerequired
body · string
|
Display name. |
typerequired
body · enum
|
prepaid, postpaid, fup, extension or addon. |
base_fee
body · number
|
Wholesale price to the reseller, major units. |
end_user_price
body · number
|
Retail price, major units. |
expiration_value
body · integer
|
Period length, paired with expiration_unit. |
expiration_unit
body · enum
|
hours, days or months. |
Errors
| Code | When it is returned |
|---|---|
ERR_VALIDATION400
|
name or type missing, or an out-of-range value |