# Integration Access ## What public documentation should say Public documentation can describe integration access in terms of capabilities, not raw internal route names. ## Typical integration capabilities Depending on product packaging and customer approval, external integrations may focus on areas such as: * submitting supported input types * checking result availability * reading structured findings and report data * exporting or sharing reports * supporting workspace or administrative workflows where enabled ## What should stay out of public docs The public help center should not expose: * raw internal route names * operational health endpoints * internal admin surfaces * private workflow or infrastructure details ## Recommended wording If external integration access exists, public docs should point readers toward approved onboarding, commercial packaging, or developer enablement rather than listing internal endpoints. --- # 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/api-reference/endpoints.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.