# Bugzilla

<!-- BEGIN GENERATED:intro -->

The Bugzilla connector is a [Palantir-provided driver](../../data-integration/foundry-provided-drivers/index.md) for Bugzilla.

To create a new Bugzilla source, follow the [standard setup flow for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#setup), then use the sections below for Bugzilla-specific configuration and networking. For the complete property reference, see the [official Bugzilla driver documentation ↗](https://cdn.cdata.com/help/SBK/jdbc/pg_connectionj.htm).

<!-- END GENERATED:intro -->

<!-- BEGIN GENERATED:capabilities -->

:::callout{theme="neutral" title="Beta"}
The Bugzilla connector is in the [beta](../../platform-overview/development-life-cycle/index.md) phase of development and may not be available on your enrollment. Functionality may change during active development.
:::

## Supported capabilities

| Capability | Status |
|---|---|
| Exploration | 🟡 Beta |
| Batch syncs | 🟡 Beta |
| Incremental | 🟡 Beta |

<!-- END GENERATED:capabilities -->

<!-- BEGIN GENERATED:configuration -->

## Configuration

The properties below are mandatory or recommended.

| Property | Required? | Description | Default |
|---|---|---|---|
| [`APIKey` ↗](https://cdn.cdata.com/help/SBK/jdbc/RSBBugzilla_p_APIKey.htm) | Mandatory | An ApiKey to authenticate to your account. API keys can be created in the Preferences > API Keys section. | — |
| [`URL` ↗](https://cdn.cdata.com/help/SBK/jdbc/RSBBugzilla_p_URL.htm) | Mandatory | The URL to the Bugzilla server used for logging in. | `https://<BugzillaURL>` |

<!-- END GENERATED:configuration -->

<!-- BEGIN GENERATED:networking -->

## Networking

The table below lists the domains that the source must be able to access to run.

For each domain, add a corresponding [egress policy](../../administration/configure-egress/index.md). If the source is hosted on-premises and not directly reachable from Foundry, use an [agent proxy egress policy](../../administration/configure-egress/index.md#agent-proxy-egress-policies) instead. The agent host itself must also be able to reach the listed domains. See [using an agent as a proxy](../../data-connection/agent-proxy/index.md) for details.

| Domain  | Required |
|--- |--- |
| \<URL> | Always |

<!-- END GENERATED:networking -->