Update a dynamic sub-account traffic limit

PATCH /open-api/v1/dynamic/accounts/{id}

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

Authentication

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

Path and query parameters

Field	In	Type	Required	Constraints	Meaning
id	path	string	Yes	—	Id.

JSON request body

Field	Type	Required	Constraints	Meaning
limit_traffic_gb	string	Yes	—	Limit traffic gb.

Request example

curl --request PATCH \
  --url 'https://api.ipfbs.com/gin/open-api/v1/dynamic/accounts/1912345678901234567' \
  --header 'Accept: application/json' \
  --header 'X-API-Key: <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
  "limit_traffic_gb": "10.0"
}'

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.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.update_time	string	No	format: date-time	Update time.

Related conventions

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