Skip to main content
PUT
Set integration visibility
  • Business accounts only; their integrations start private.
  • An Owner or Admin changes every tool your team created there; a member changes only their own. Other accounts’ tools in a public integration stay public.
  • The tools may join the site’s existing integration of that visibility, so the response names the integration that now holds them.
  • Callers: an API key, an MCP OAuth token or a Dashboard session.
  • Permission: tools:build.
  • Effect: Creates or changes something.
  • Errors: not_found, integration_tool_name_taken, and the errors any request can get.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

an integration ID: int_ and 32 lowercase hex digits

Example:

"int_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190"

Body

application/json
visibility
enum<string>
required

public: published on Pomerado for every account to find and use. private: only your team sees, uses and edits it

Available options:
public,
private

Response

The integration that now holds your team's tools, and its visibility

id
string
required

an integration ID: int_ and 32 lowercase hex digits

Example:

"int_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190"

visibility
enum<string>
required

public: published on Pomerado for every account to find and use. private: only your team sees, uses and edits it

Available options:
public,
private