The Reckon Accounts Hosted connector is a Palantir-provided driver for Reckon Accounts Hosted.
To create a new Reckon Accounts Hosted source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Reckon Accounts Hosted-specific configuration and networking. For the complete property reference, see the official Reckon Accounts Hosted driver documentation ↗.
The Reckon Accounts Hosted connector is in the beta phase of development and may not be available on your enrollment. Functionality may change during active development.
| Capability | Status |
|---|---|
| Exploration | 🟡 Beta |
| Batch syncs | 🟡 Beta |
| Incremental | 🟡 Beta |
| OAuth 2.0 authentication | 🟡 Beta |
| Table exports | 🟡 Beta |
The properties below are mandatory or recommended.
| Property | Required? | Description | Default |
|---|---|---|---|
Password ↗ | Mandatory | The company file's password. | — |
SubscriptionKey ↗ | Mandatory | The subscription key used to authenticate to Reckon Accounts Hosted. | — |
User ↗ | Mandatory | The company file's username. | — |
CompanyFile ↗ | Recommended | The path to the company file. | — |
CountryVersion ↗ | Recommended | To connect to a Hosted company file, you will need to pass the appropriate value in the CountryVersion. | 2021.R2.AU |
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. | — |
The table below lists the domains that the source must be able to access to 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 |
|---|---|
| api.reckon.com | Always |
| identity.reckon.com | Always |
This connector supports OAuth 2.0 authentication. Follow the OAuth 2.0 guidance for Palantir-provided drivers to configure and authorize the connection.
This connector supports table exports. Learn how to set up a table export.