> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/enterprise-features/integrations-and-api.md).

# Integrations & API

Protege offers enterprise integration options for teams that want to connect document review and compliance workflows to their own systems, automations, or agent frameworks.

## What Is Available

* **External Review API**: Submit text and file-based document reviews, poll asynchronous jobs, and retrieve structured review findings.
* **Reference Data Access**: Discover tenant-scoped brands, policies, policy groups, and document evaluation types required to drive integrations.
* **Monitoring Workflows**: Manage scanner jobs and retrieve report data for ongoing web and content monitoring use cases.
* **Implementation Support**: Enterprise customers can receive sandbox access, sample requests, and enablement support during setup.

## Access and Enablement

If you need an API key, help selecting a `documentEvaluationTypeId`, or sample requests for your environment, contact the Protege team through your shared enterprise support channel or email <support@tryprotege.com>.

The detailed endpoint reference for document reviews remains available in the Document Review section:

{% content-ref url="/pages/wH4eclB0efC3ka5ulg6i" %}
[API Reference](https://docs.tryprotege.com/review/review-tool-concepts/document-review/api-reference.md)
{% endcontent-ref %}


---

# 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.tryprotege.com/review/enterprise-features/integrations-and-api.md?ask=<question>&goal=<user_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.
