Portal settings

Portal settings apply to the whole workspace. They are available through REST and MCP to API tokens, OAuth connections and the Operator. Chat and voice agents can’t use them.

Operation	REST	MCP	Permission
Get settings	`GET /v1/workspaces/{workspace_id}/portal-settings`	`get_portal_settings`	`Access Portals`
Update settings	`PATCH /v1/workspaces/{workspace_id}/portal-settings`	`update_portal_settings`	See below

Every method also requires Portals access for the workspace.

What you can change

Field	What it does	Permission
`default_stay_template_id`	The active template new stay portals start from. `null` restores the built-in default.	`Manage Portals`
`auto_provision_stay_portals`	Creates a stay portal for every booked reservation.	`Manage Portals`
`default_stripe_connection_id`	The Stripe account for payments no routing rule matches.	`Manage Portal Payments`
`stripe_routing_rules`	Sends payments for stays at the listed listings or listing groups to a Stripe account. The first matching rule wins.	`Manage Portal Payments`

Omitted fields stay unchanged. stripe_routing_rules replaces every rule; send [] to remove them all. Sending only one of the two Stripe fields keeps the other.

Stripe accounts

For callers with Manage Portal Payments, the response lists the connected Stripe accounts in stripe_connections. Use an account’s id as stripe_connection_id in routing rules or on an offer. Without that permission, stripe_connections is null.

Getting started

Workspaces

Contacts

Conversations

Tickets

Tasks

Helpdesk tickets

Calls

Reservations

Appointments

Custom attributes

Knowledge base

Agents

Inbox types

Skills

Reviews

Custom tools

Escalations

Workflows

Portals

Insights

Portal settings

What you can change

Stripe accounts

​What you can change

​Stripe accounts

What you can change

Stripe accounts