The Epicor Kinetic connector is a Palantir-provided driver for Epicor Kinetic.
To create a new Epicor Kinetic source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Epicor Kinetic-specific configuration and networking. For the complete property reference, see the official Epicor Kinetic driver documentation ↗.
The properties below are mandatory or recommended.
| Property | Required? | Description | Default |
|---|---|---|---|
AuthScheme ↗ | Mandatory | The type of authentication to use when connecting to Epicor Kinetic. | Basic |
ERPInstance ↗ | Mandatory | The name of the installed ERP application. | — |
Service ↗ | Mandatory | Specify the service you want to retrieve data from. | BaqSvc |
URL ↗ | Mandatory | Set this to the URL of the server where ERP instance is hosted. | https://myServer.EpicorSaaS.com |
ApiVersion ↗ | Recommended | Specify the version of Epicor Kinetic API. | v1 |
InitiateOAuth ↗ | Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | REFRESH |
OAuthClientId ↗ | Recommended | Specifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. | — |
OAuthClientSecret ↗ | Recommended | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server. | — |
Password ↗ | Recommended | Specifies the password of the authenticating user account. | — |
User ↗ | Recommended | Specifies the user ID of the authenticating Epicor Kinetic user account. | — |
The table below lists the domains that the source needs to be able to access in order to successfully run.
For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.
| Domain | Required |
|---|---|
| <URL> | Always |
| login.microsoftonline.com | If AuthScheme=AzureADOpenID |