> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall-for-anthropic-claude/nightfall-for-claude-enterprise-compliance-api.md).

# Nightfall for Claude Enterprise (Compliance API)

Nightfall connects to your Claude Enterprise organization through Anthropic's Compliance API and treats Claude Enterprise as a monitored SaaS surface, the same way it treats Slack, Microsoft 365, Google Workspace, and the rest of your connectors. Together with Nightfall's runtime Claude controls (covered in [Comprehensive Claude Coverage](/nightfall-for-anthropic-claude/comprehensive-claude-coverage.md)), it gives your team both inline prevention and a complete server-side audit record.

* Scans Claude Enterprise chat conversations and uploaded files for sensitive data: PII, PHI, PCI, secrets, source code, and any custom detector you have already built.
* Surfaces violations in the standard Detection & Response page using existing policies and detection rules. No new console.
* Monitor-only on this surface. Admin alerts (Slack, email, webhook, SIEM), optional end-user notification, and a full audit trail. The Compliance API is post-hoc, so no inline block is possible on this channel. Inline block on Claude happens through [Claude Inference Hooks](https://help.nightfall.ai/data-exfiltration-prevention/ai-agent-security/ai-governance/auditability-and-control/claude-inference-hooks) (across claude.ai, Cowork, Claude Desktop, mobile, Slack, and Claude Code), at the endpoint (Claude Desktop and the Claude web tab), and at the device hooks layer (Claude Code IDE and CLI). See [Comprehensive Claude Coverage](/nightfall-for-anthropic-claude/comprehensive-claude-coverage.md).
* Coverage scope of *this* integration, explicitly: Claude Enterprise chat conversations and uploaded files only. Not Claude Team. Not Claude on Bedrock or Vertex AI. Not model-inference content delivered through the Claude Platform. (Nightfall's runtime Claude coverage, listed in [Comprehensive Claude Coverage](/nightfall-for-anthropic-claude/comprehensive-claude-coverage.md), handles the surfaces this integration does not.)

### Prerequisites

* Claude Enterprise plan with admin access to the Claude admin console.
* A Nightfall account with Detection & Response enabled.
* A Compliance Access Key generated from the Claude admin console. See [Anthropic's guide for generating one](https://support.claude.com/en/articles/15167101-get-started-with-claude-compliance-api-integrations).


---

# 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://help.nightfall.ai/nightfall-for-anthropic-claude/nightfall-for-claude-enterprise-compliance-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.