> ## Documentation Index > Fetch the complete documentation index at: https://onecli.sh/docs/llms.txt > Use this file to discover all available pages before exploring further. # Activate or add an organization blocklist entry > Provide either `{ hostId }` to activate a predefined blocklist host, or `{ name, hostPattern }` to add a custom rule — at the organization level. Requires admin role. Cloud only. ## OpenAPI ````yaml /openapi.yaml post /org/apps/{provider}/blocklist openapi: 3.1.0 info: title: OneCLI API version: '1.0' description: > The OneCLI API lets you manage agents, secrets, policy rules, app connections, and user settings programmatically. **Base URL:** `https://api.onecli.sh/v1` (Cloud) or `http://localhost:10254/v1` (self-hosted) ## Authentication All endpoints require authentication via one of: - **API Key** — `Authorization: Bearer ` header. Generate keys in the dashboard or via `GET /v1/user/api-key`. - **Session** — Cookie-based session from the web dashboard. For organization-scoped API keys, include the `X-Project-Id` header to specify which project to operate on. servers: - url: https://api.onecli.sh/v1 description: OneCLI Cloud - url: http://localhost:10254/v1 description: Self-hosted (Docker) security: - bearerAuth: [] tags: - name: Agents description: Manage agents and their access tokens, secrets, and configuration. - name: Secrets description: Manage credentials that the gateway injects into outbound requests. - name: Rules description: >- Manage policy rules that control how agents interact with external services. - name: User description: Manage your user profile and API keys. - name: Projects description: >- Manage projects within your organization. Requires admin role for create/update and owner role for delete. Cloud only. - name: Team description: Provision team members programmatically. Requires admin role. Cloud only. - name: Apps description: >- Manage app connections (OAuth and direct credentials), BYOC configuration, permission catalogs, and blocklists. - name: Connections description: App connections as a top-level resource. - name: Utility description: Health check and project resource summaries. - name: Agent Setup description: >- Endpoints agents and orchestrators use to bootstrap gateway access (container config, credential stubs, gateway skill). - name: Migration description: Migrate data from a self-hosted instance to OneCLI Cloud. - name: Organization Settings description: Organization-wide policy settings. Cloud only. - name: Organization Secrets description: >- Manage secrets at the organization level. Organization secrets apply across all projects. Cloud only. - name: Organization Rules description: >- Manage policy rules at the organization level. Organization rules apply across all projects. Cloud only. - name: Organization Connections description: Manage app connections at the organization level. Cloud only. - name: Organization App Config description: Manage BYOC app configuration at the organization level. Cloud only. - name: Partner Organizations description: >- Create and manage customer organizations as a partner. Requires a Partner API key. Cloud only. - name: Partner Projects description: Manage projects within an unclaimed partner organization. Cloud only. - name: Partner Secrets description: >- Manage partner-level secrets inherited by every organization you manage. Cloud only. - name: Partner Budgets description: >- Cap how much an organization can spend on a partner LLM key. Owner or admin only. Cloud only. - name: Partner Members description: >- Manage who can sign in to your partner portal. Owner or admin only. Cloud only. - name: Organization Partner description: Inspect and detach an organization's partner relationship. Cloud only. paths: /org/apps/{provider}/blocklist: post: tags: - Organization App Config summary: Activate or add an organization blocklist entry description: > Provide either `{ hostId }` to activate a predefined blocklist host, or `{ name, hostPattern }` to add a custom rule — at the organization level. Requires admin role. Cloud only. operationId: addOrgBlocklistEntry parameters: - $ref: '#/components/parameters/provider' requestBody: required: true content: application/json: schema: oneOf: - type: object title: Activate predefined host required: - hostId properties: hostId: type: string - type: object title: Add custom rule required: - name - hostPattern properties: name: type: string hostPattern: type: string responses: '201': description: Blocklist entry created or activated content: application/json: schema: $ref: '#/components/schemas/BlocklistHostState' '400': description: Invalid request body content: application/json: schema: $ref: '#/components/schemas/Error' components: parameters: provider: name: provider in: path required: true schema: type: string description: App provider identifier (e.g., `gmail`, `github`, `jira`) schemas: BlocklistHostState: type: object description: State of one blocklist entry — a predefined host or a custom rule. properties: hostId: type: string ruleId: type: string nullable: true description: >- The backing rule ID, or null when a predefined host has never been activated. enabled: type: boolean custom: type: boolean description: True for custom rules, false for the app's predefined hosts. name: type: string hostPattern: type: string scope: type: string nullable: true enum: - project - organization - null Error: description: | Error responses take one of two shapes depending on the failing layer: route-level validation returns the flat shape (`{ "error": "..." }`), while authentication failures (401/403) and service errors (not-found, conflict, and service-level validation) return the envelope (`{ "error": { "message": "...", "type": "..." } }`). oneOf: - $ref: '#/components/schemas/ErrorFlat' - $ref: '#/components/schemas/ErrorEnvelope' ErrorFlat: type: object description: Flat error shape used by route-level validation. properties: error: type: string required: - error ErrorEnvelope: type: object description: >- Envelope error shape used for authentication failures and service errors. properties: error: type: object properties: message: type: string type: type: string description: Error category (e.g. `authentication_error`). securitySchemes: bearerAuth: type: http scheme: bearer description: API key obtained from the dashboard or `GET /user/api-key` ````