Set My Chat Spend Limit
Set the CALLER's own per-chat spend cap - or, with a null body value, set it to EXPLICIT "no cap" (TOS-2393; review finding #2).
A null value does NOT clear the caller's entry - it is a durable statement that this payer has opted out of any cap, and it beats the legacy room-wide scalar fallback (unlike an absent entry). To remove the entry entirely and revert to "no preference stated" (falls back to whatever the room's legacy scalar says), use DELETE .../my-spend-limit instead - the two routes are deliberately NOT equivalent any more. See ChatService.set_my_chat_spend_limit's docstring for the full rationale.
The payer is always identity.id - the request's resolved principal, which get_identity (not get_real_identity) allows to be an AUTHORIZED IMPERSONATION target via X-Impersonate-Identity-Id, not only the human at the keyboard. There is no field on this route through which a caller could freely NAME a payer (see ChatService.set_my_chat_spend_limit's docstring for why that is an authorization guarantee, not an impossibility one). Requires ACTIVE participation (ChatService.get_chat's gate), not the relaxed any-status membership check get_chat_detail uses, so a removed participant cannot set a budget in a room they no longer belong to.
Request
- Base URL: https://app.thinqos.com (the document declares no server; this is the origin it was published from)
- URL: https://app.thinqos.com/api/chats/{chat_id}/my-spend-limit
- Auth: none declared
Path parameters
Headers
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 2 revisions of this API.