# Developer Integrations Virusis may support approved developer integrations for customers or partners who need the platform inside a broader workflow. ## Typical use cases * pulling results into dashboards or review portals * connecting Virusis findings to broader security workflows * supporting automation around reporting and review * extending internal analyst experiences with approved product data ## Public documentation guidance Public docs should describe the outcome of an integration, not the private implementation details behind it. ## What to avoid in public docs * do not publish private package names unless they are intentionally distributed * do not expose internal route names or auth internals * do not describe hidden operational tooling as public integration surface ## Recommended positioning If developer access is offered, public help content should route readers toward approved onboarding and supported integration paths. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.virusis.com/integrations/typescript-sdk.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.