> ## Documentation Index > Fetch the complete documentation index at: https://docs.app.strix.ai/llms.txt > Use this file to discover all available pages before exploring further. # Connect a self-hosted Jira with a token > Connects a self-hosted Jira (Data Center or Server) with an instance URL and a personal access token. This route is available only on on-prem Strix installs and returns 404 on hosted Strix. The token must belong to an organization admin (parity with the dashboard). When the token has Jira administrator rights, Strix registers the status webhook. Otherwise the response carries the webhook URL for a Jira administrator to add by hand. ## OpenAPI ````yaml /openapi.json post /integrations/jira/server/connect openapi: 3.1.0 info: title: Strix API version: 1.0.0 description: >- Public REST API for the Strix autonomous penetration testing platform. Manage scans, vulnerabilities, assets, schedules, API tokens, and webhooks. servers: - url: /api/v1 description: Strix v1 API security: - BearerAuth: [] tags: - name: Scans description: Launch, monitor, and manage security scans. - name: Vulnerabilities description: View and triage discovered vulnerabilities. - name: Assets description: Domains and repositories registered for scanning. - name: Schedules description: Recurring scan schedules (Pro plan). - name: Tokens description: Manage API tokens for authentication. - name: Webhooks description: Configure webhook subscriptions for real-time event notifications. - name: Organization description: Workspace configuration for the authenticated organization. - name: Members description: Manage organization members and roles. - name: Invitations description: List and revoke organization invitations. - name: PR Reviews description: Automated security review of pull requests. - name: Connectors description: Network connectors for scanning internal/private targets. - name: Knowledge description: >- Organization knowledge base: documents, policies, and repo profiles that steer the agent. - name: Uploads description: Upload source/code/documentation archives for whitebox scans. - name: Integrations description: Third-party integrations (GitLab, Bitbucket, ticketing). - name: Chat description: Conversational agent sessions. - name: Analytics description: Aggregate dashboard analytics. - name: Test Users description: >- Per-domain test accounts (with optional MFA) the agent authenticates as during scans. - name: License description: Self-hosted license state, entitlements, and aggregate usage. - name: Supply Chain description: >- SBOM inventory, supply-chain findings, scans, and policy for connected repositories. - name: CLI description: >- Device authorization endpoints that let the Strix CLI and coding agents sign in and receive an API token. - name: Billing description: Credit balance, agent-payable top-ups, and automatic top-up settings. - name: Workspaces description: List, create, and switch workspaces. paths: /integrations/jira/server/connect: post: tags: - Integrations summary: Connect a self-hosted Jira with a token description: >- Connects a self-hosted Jira (Data Center or Server) with an instance URL and a personal access token. This route is available only on on-prem Strix installs and returns 404 on hosted Strix. The token must belong to an organization admin (parity with the dashboard). When the token has Jira administrator rights, Strix registers the status webhook. Otherwise the response carries the webhook URL for a Jira administrator to add by hand. operationId: connectJiraServer requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ConnectJiraServerRequest' responses: '200': description: Connected. content: application/json: schema: $ref: '#/components/schemas/ConnectJiraServerResponse' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalError' security: - BearerAuth: - integrations:write components: schemas: ConnectJiraServerRequest: type: object description: >- Connect a self-hosted Jira (Data Center or Server) with a personal access token. properties: instance_url: type: string description: >- Base URL of the Jira instance, for example https://jira.example.com or https://tools.example.com/jira. access_token: type: string description: Personal access token that the Jira user created on that instance. required: - instance_url - access_token ConnectJiraServerResponse: type: object properties: success: type: boolean webhook_registered: type: boolean description: True when Strix registered the status webhook on the Jira instance. webhook_url: type: string description: >- Webhook URL for a Jira administrator to add when webhook_registered is false. The URL contains a secret and is returned once. webhook_error: type: - string - 'null' description: Reason Jira refused the webhook registration, if any. server_title: type: - string - 'null' server_version: type: - string - 'null' required: - success - webhook_registered - webhook_url ErrorResponse: type: object properties: detail: type: string description: Human-readable explanation of the error. code: type: string description: >- Stable machine-readable error code. `insufficient_scope` means the token does not hold the scope that this endpoint requires. required_scope: $ref: '#/components/schemas/ApiV1Scope' description: >- Scope that the caller must add to the token. Returned with the `insufficient_scope` code. docs: type: string format: uri description: Documentation page that explains how to resolve the error. hint: type: string description: >- One instruction that resolves the error. For `insufficient_scope`, a CLI session gets the `strix cloud session scopes set full` or `strix cloud login --scope-profile full` command, and an API token gets the settings page where the user creates a token with the scope. When the owner's role cannot hold the scope, the hint asks for a role change instead. required: - detail ApiV1Scope: type: string enum: - scans:read - scans:write - vulnerabilities:read - vulnerabilities:write - dependencies:read - schedules:read - schedules:write - assets:read - assets:write - organizations:read - organizations:write - members:read - members:write - invitations:read - invitations:write - webhooks:read - webhooks:write - tokens:write - audit:read - pr_reviews:read - pr_reviews:write - connectors:read - connectors:write - knowledge:read - knowledge:write - uploads:write - integrations:read - integrations:write - chat:read - chat:write - scans:message - analytics:read - llm:read - llm:write - test_users:read - test_users:write - license:read - supply_chain:read - supply_chain:write - billing:read - billing:write responses: BadRequest: description: Bad request. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' Unauthorized: description: Missing or invalid API token. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' Forbidden: description: >- Insufficient permissions or missing scope. A missing scope returns the `insufficient_scope` code, the `required_scope` field, and a `hint` with the command or page that grants the scope, so a client can request the correct scope and retry. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' NotFound: description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' InternalError: description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: BearerAuth: type: http scheme: bearer description: >- API token obtained from the Tokens endpoint or CLI device login. Include as `Authorization: Bearer `. Requests made with a managed CLI session also include `X-Strix-Workspace: ` to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch. ````