> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation-1/account-management/account-admin/integrations-and-webhooks/integrations-api.md). # Integrations (API) The integrations page provides the status of each API integration and the ability to connect new integrations (if licensed) or edit existing connections. If an integration is available but not set up, the user will see a "Connect" button. A "License required" label will be displayed if an integration is not licensed. {% hint style="info" %} [Visit this page](/plextrac-documentation/product-documentation-1/integrations-and-file-imports.md) for a list of all third-party tools PlexTrac integrates with, including scanner files and CSV templates. {% endhint %} ## Included API Integrations The following integrations are included with every PlexTrac instance:


Remediation	jira.jpg	Jira
Remediation	service.jpg	ServiceNow

## Licensed API Integrations The following integrations require an additional cost/license to access (one license covers all tools):


Findings/Reports	cobalt.jpg	Cobalt	field mappings
Findings/Reports	edgescan new.jpeg	Edgescan	field mappings
Findings/Reports	hackerone.jpg	HackerOne
Findings/Reports	snyk.jpg	Snyk	field mappings
Findings/Reports	VM-VRT-DRK (1).png	Tenable Vulnerability Management
Findings/Reports	SC-VRT-DRK (1).png	Tenable Security Center

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.plextrac.com/plextrac-documentation/product-documentation-1/account-management/account-admin/integrations-and-webhooks/integrations-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.