Remotehost Docs
API ReferenceAdd-ons

Allow or forbid an add-on in an organization

PUT
/orgs/{orgId}/addons/{listingId}/policy

allowed: false forbids the listing: nothing installs it, and existing installs stop being delivered. allowed: true allows it, even a community listing while community add-ons are off. Needs integrations.manage (owners and admins). Audited.

Authorization

bearerAuth
AuthorizationBearer <token>

A RemoteHost API key (rh_sk_...) or a user session token.

In: header

Path Parameters

orgId*string
listingId*string

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X PUT "https://example.com/orgs/string/addons/string/policy" \  -H "Content-Type: application/json" \  -d '{    "allowed": true  }'
{  "addon": {    "id": "string",    "slug": "skill/code-review",    "kind": "app",    "name": "string",    "summary": "string",    "publisher": "string",    "provenance": "first_party",    "status": "listed",    "attachLevels": [      "org"    ],    "pricing": "free",    "iconUrl": "string",    "held": true,    "holding": "held_free",    "policy": {      "setting": "allow",      "allowed": true    }  }}

Return an add-on to the organization's default DELETE

Removes the org's allow or forbid: the listing is then allowed, unless it is a community listing and the org has not opted in. Needs `integrations.manage`. Audited.

Opt an organization in to community add-ons, or out PUT

Community add-ons are unreviewed third-party code and servers that run beside the org's secrets, so they are off until an owner or admin opts in. Needs `integrations.manage`. Audited.