Call page.set_password
Put a password in front of a published site — 'password-protect this page', 'only people with the password should see it', 'lock this site down'. Put one shared password in front of a page that is already published. Anyone with the address must type it to get in. Setting or changing it immediately kills every private link and every visitor's saved unlock, so say that. Never repeat the password back in your reply, and never suggest one — use exactly what the member gave you. Not for letting one person in without the password — that is page.mint_access_link. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.
Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/page.set_password
- Auth: HTTP bearer
Headers
Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.
Request body
Response
The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.
Changes
No recorded changes to this operation across all 4 revisions of this API.