Skip to main content

updatePayment

BooleanWrapper updatePayment(QuantityRequestDto)

PUT /api/2.0/portal/payment/update

Change the subscription quantity

Changes how many units of the plan the portal is paying for - the number of administrators it covers - and lets the payment provider bill the difference against the payment method already on file. The portal must have a billing customer and a plan bought through PUT api/2.0/portal/payment/url, and while the portal is on a priced plan the product name in quantity has to be that same plan, which GET api/2.0/portal/payment/quota reports, because a subscription is changed here and not swapped. Only the payer - the portal user whose e-mail is the billing customer's e-mail - may call it. The call is mutating and charges money, and it is guarded against a double submission: once the new quantity is in effect, repeating the same request fails with 400 because that quantity is already set. The result is true when the provider accepted the change and false when it declined it without an error. Exactly one product per call is accepted, the operation is limited to ten requests a minute per user by default and answers 429 above that, and wallet services are not bought here - use PUT api/2.0/portal/payment/updatewallet for those.

Parameters​

NameInTypeDescriptionNotes
QuantityRequestDtobodyQuantityRequestDto[optional]

Responses​

Status codeDescriptionTypeResponse headers
200true when the provider accepted the new quantity, false when it declined itBooleanWrapperX-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
400The request body cannot be read or has no quantity, quantity does not hold exactly one product, the product is not a subscription plan or not the plan currently paid, or the quantity is already the one in effect--
402The portal already has more administrators, users, rooms or AI agents, or stores more data, than the plan in the new quantity allows--
403The caller is not the payer of this portal, or the portal has no billing service configured--
404This portal has no billing customer yet--
401UnauthorizedErrorApiResponse-
429Too Many Requests.ErrorApiResponseRetry-After
500Internal Server Error.ErrorApiResponse-
502Bad Gateway. Returned by the reverse proxy, response body may be HTML and not JSON.--
503Service Unavailable. Returned by the reverse proxy, response body may be HTML and not JSON.--

Return type​

BooleanWrapper

Authorization​

Basic, OAuth2 (scopes: read, write), ApiKeyBearer, asc_auth_key, Bearer, OpenId

HTTP request headers​

  • Content-Type: application/json
  • Accept: application/json