Replace the whole portfolio
Clears the signed-in owner’s rows and writes the body in their place, in one transaction. This is here for the worked example, putting it away, resetting it or loading it into a team that holds nothing yet, and nothing else: a normal edit is POST /portfolio/changes. Only an owner of the team may call it, and a portfolio that holds the owner’s own records is never replaced. Every collection has to be named, and one you send empty is emptied: a replace is a replace, but an omission is a mistake and is refused rather than acted on. The body names the schema it was built against for the same reason. Every row is written at rev 1, whatever revision it arrived carrying, so the next GET /portfolio hands back rows a client can edit from.
Request
- Base URL: http://localhost:5180
- URL: http://localhost:5180/api/v1/portfolio
- Auth: API key in cookie better-auth.session_token
Request body
Response
The portfolio was replaced.
Changes
No recorded changes to this operation across all 1 revision of this API.