Create a dynamic sub-account

POST /open-api/v1/dynamic/accounts

Base URL: https://api.ipfbs.com/gin.

Authentication

Send your key in the X-API-Key request header.

JSON request body

Field	Type	Required	Constraints	Meaning
request_no	string	Yes	minLength: 1; maxLength: 64; pattern: ^[A-Za-z0-9_-]{1,64}$	Caller request number for duplicate protection.
sub_account	string	Yes	—	Sub account.
limit_traffic_gb	string	No	—	Limit traffic gb.

Request example

curl --request POST \
  --url 'https://api.ipfbs.com/gin/open-api/v1/dynamic/accounts' \
  --header 'Accept: application/json' \
  --header 'X-API-Key: <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
  "request_no": "req_20260824_001",
  "sub_account": "team_a_01"
}'

Success response data

Responses use code, msg, data, and next. HTTP 200 can also contain a nonzero business error code; check code first.

Field	Type	Required	Constraints	Meaning
data.id	string	No	—	Id.
data.sub_account	string	No	—	Sub account.
data.password	string	No	—	Password.
data.limit_traffic_gb	string	No	—	Limit traffic gb.
data.lifetime_used_gb	string	No	—	Lifetime used gb.
data.resource_status	string	No	enum: ACTIVE, REMOVED	Resource status.
data.user_enabled	boolean	No	—	User enabled.
data.flow_blocked	boolean	No	—	Flow blocked.
data.available	boolean	No	—	Available.
data.control_pending	boolean	No	—	Control pending.
data.last_usage_sync_time	string	No	format: date-time	Last usage sync time.
data.create_time	string	No	format: date-time	Create time.
data.update_time	string	No	format: date-time	Update time.

Related conventions

Request conventions · Response structure · Error codes · API reference index