# Sage 300 The Sage 300 connector is a [Palantir-provided driver](../../data-integration/foundry-provided-drivers/index.md) for Sage 300. To create a new Sage 300 source, follow the [standard setup flow for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#setup), then use the sections below for Sage 300-specific configuration and networking. For the complete property reference, see the [official Sage 300 driver documentation ↗](https://cdn.cdata.com/help/GTK/jdbc/pg_connectionj.htm). :::callout{theme="neutral" title="Beta"} The Sage 300 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 | ## Configuration The properties below are mandatory or recommended. | Property | Required? | Description | Default | |---|---|---|---| | [`Password` ↗](https://cdn.cdata.com/help/GTK/jdbc/RSBSage300_p_Password.htm) | Mandatory | Specifies the password of the authenticating user account. | — | | [`URL` ↗](https://cdn.cdata.com/help/GTK/jdbc/RSBSage300_p_URL.htm) | Mandatory | Set the URL to the HTTP or HTTPS endpoint of your Sage 300 system. For example, http://localhost/Sage300WebApi/v1.0/-/. | `https://{host-application-path}/v{version}/{tenant}/` | | [`User` ↗](https://cdn.cdata.com/help/GTK/jdbc/RSBSage300_p_User.htm) | Mandatory | Specifies the user ID of the authenticating Sage 300 user account. | — | | [`Company` ↗](https://cdn.cdata.com/help/GTK/jdbc/RSBSage300_p_Company.htm) | Recommended | Determines the company. | — | ## 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 | |--- |--- | | \ | Always. URL connection property, in format {protocol}://{host-application-path}/v{version}/{tenant}/ (i.e., http://localhost/Sage300WebApi/v1.0/-/) |