Skip to content
Vocapable Developers

Set the mobile monthly/daily spend guardrail after fresh browser confirmation

PUT
/v1/mobile/billing/budget
curl --request PUT \
  --url https://api.vocapable.com/v1/mobile/billing/budget \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "expected_version": 1, "amount_minor": 1 }'

CAS one displayed cap, preserving the wallet’s non-mobile threshold and period.

A mobile retry with a lost response cannot replay the state change: the one-use grant is consumed and the revision has advanced. The client receives a conflict on retry, reloads the live value, and asks for a fresh browser proof rather than guessing.

Authorizations

Section titled “Authorizations”

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
MobileBillingBudgetUpdateRequest

One displayed spend-cap edit bound to a browser step-up grant and a revision.

The server preserves the wallet’s existing low-balance threshold and known period. This keeps the small native editor from silently clearing a browser-configured setting.

object
expected_version
required
Expected Version
integer
>= 1
amount_minor
required
Any of:
integer
>= 1
Examplegenerated
{
  "expected_version": 1,
  "amount_minor": 1
}

Responses

Section titled “Responses”

200

Section titled “200”

Successful Response

Media typeapplication/json
MobileBillingBudget

The current spend guardrails; no payment method or provider data is representable.

object
amount_minor
Any of:
integer
>= 1
currency
required
Currency
string
>= 3 characters <= 12 characters
period
Any of:
string
Allowed values: daily monthly
low_balance_threshold_minor
Any of:
integer
version
required
Version
integer
>= 1
updated_at
required
Updated At
string format: date-time
Example
{
  "period": "daily"
}

422

Section titled “422”

Validation Error

Media typeapplication/json
HTTPValidationError
object
detail
Detail
Array<object>
ValidationError
object
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string
input
Input
ctx
Context
object
Examplegenerated
{
  "detail": [
    {
      "loc": [
        "example"
      ],
      "msg": "example",
      "type": "example",
      "input": "example",
      "ctx": {}
    }
  ]
}