Integrate iPaaS.com with Epicor Prophet 21 to enable seamless data synchronization for customers, customer and company addresses, locations, products, product inventory, transactions (orders), and transaction tracking numbers.
This article is the standalone reference for connecting an Epicor Prophet 21 instance to iPaaS.com: what credentials and settings are required, how authentication works, and how the integration's polling and throttling behave. Use it when you first connect the integration as well as later — when rotating credentials, changing environments, or onboarding new team members. For the first-time, step-by-step setup journey (subscribing in the marketplace, creating default mappings, and post-installation checks), see the Installation Instructions.
How to Connect
Prerequisites
Before configuring the integration in iPaaS.com, have the following ready from your Epicor Prophet 21 environment:
An Epicor Prophet 21 instance with the REST/OData services enabled and reachable over the network from iPaaS.com.
A Prophet 21 service account (user name and password) with permission to read the data you want to bring into iPaaS.com and to write orders back into Prophet 21. Subscribers or their MiSP should confirm the account's permissions with their Epicor administrator.
The API URL for the Prophet 21 environment you are connecting (see the example values below).
Configuration Details
You will need the following values when you configure the subscription:
API Url: The base URL of your Epicor Prophet 21 REST/OData instance. Test/Sandbox environments use a vendor-hosted URL such as
https://sandbox-test.epicordistribution.com; your Production URL is provided by the client (your Epicor environment owner).UserName: The user name of the Prophet 21 service account the integration authenticates with. Example:
ipaas_service.Password: The password paired with that user name. Example:
••••••••(entered securely; never shared in plain text).Time Zone Offset: The UTC offset for your location, applied to the date filters the integration uses when polling Prophet 21. Example:
-05:00.
Configure Subscription Settings
Enter these values on the integration's subscription settings page in iPaaS.com. The per-entity Poll Search Days fields and the concurrency fields are pre-populated with the integration's defaults; you only need to change them to widen a look-back window or adjust concurrency.
Field | Description | Required | Example |
API Url | Base URL of the Epicor Prophet 21 REST/OData instance the integration connects to. | Yes |
|
UserName | User name of the Prophet 21 service account. Combined with Password to obtain an access token. | Conditional — required together with Password to authenticate. |
|
Password | Password for the Prophet 21 service account. Paired with UserName. | Conditional — required together with UserName to authenticate. |
|
Time Zone Offset | UTC offset for your location, applied to the date filters used when polling Prophet 21 for recently changed records. | Yes |
|
Customer Poll Search Days | Look-back window, in days, for how far back the scheduled poll searches for changed customer records. Defaults to 4 days when left blank. | No |
|
Product Poll Search Days | Look-back window, in days, for the scheduled product poll. Defaults to 4 days when left blank. | No |
|
Company Poll Search Days | Look-back window, in days, for the scheduled company poll. | No |
|
Product Inventory Poll Search Days | Look-back window, in days, for the scheduled product inventory poll. | No |
|
Invoice Poll Search Days | Look-back window, in days, for the scheduled invoice poll. | No |
|
Transaction Poll Search Days | Look-back window, in days, for the scheduled transaction (order) poll. | No |
|
Transaction TrackingNumber Poll Search Days | Look-back window, in days, for the scheduled shipment tracking-number poll. Defaults to 4 days when left blank. | No |
|
Concurrent Batch Executions | Maximum number of batch transfers the integration runs at the same time. A default applies when the field is left blank. | No |
|
A larger Poll Search Days value is useful during initial setup or after downtime, to capture records that changed while the integration was not running. Increasing Concurrent Batch Executions lets more batches process in parallel; see Throttling below before changing it.
Authentication Methods
Epicor Prophet 21 uses a token-based (OAuth-style) authentication flow. You do not manage the token yourself — the integration handles it for you:
Enter the API Url, UserName, and Password on the subscription settings page and save.
On the first transfer, the integration exchanges your UserName and Password for an access token at your Prophet 21 API URL.
The integration caches that token and reuses it for subsequent calls.
Access tokens expire after roughly 24 hours. When the token expires, the integration automatically requests a new one — no action is required from subscribers or their MiSP.
Because the token is generated on the first transfer, there is no separate connect-and-verify button that confirms reachability at the moment you save your settings. If your credentials or API URL are incorrect, the issue surfaces when the first transfer runs; review the results in Dashboard / Integration Monitoring / Error Logs. To rotate credentials, update UserName and Password on the subscription settings page and save — the integration obtains a fresh token on the next transfer.
Initialization Support
Currently, initialization (a bulk historical import on first connect) is not supported for Epicor Prophet 21 in iPaaS.com. Data synchronization is poll-based: the integration picks up changed records on its scheduled poll, and you can also trigger transfers on demand from the iPaaS.com Manual Sync page.
To widen the initial catch-up window for a given entity, increase that entity's Poll Search Days value (see Configure Subscription Settings) so the first poll reaches further back in time. To load a large historical dataset, follow the canonical bulk-sync procedure: Syncing a large dataset using iPaaS.com and Postman Runner.
Throttling
The integration paces its work against Epicor Prophet 21 using two controls, both pre-populated with the integration's defaults:
Per-entity Poll Search Days: Each entity (Customer Poll Search Days, Product Poll Search Days, Company Poll Search Days, Product Inventory Poll Search Days, Invoice Poll Search Days, Transaction Poll Search Days, and Transaction TrackingNumber Poll Search Days) has its own look-back window, so the scheduled poll only requests records changed within that window rather than scanning the full history on every run. Keeping these windows no larger than needed limits how much data each poll pulls.
Concurrent Batch Executions: Bounds how many batch transfers run at the same time. Raising it increases throughput but also increases simultaneous load on your Prophet 21 instance; lower it if you see contention. A default applies when the field is left blank.
These fields are pre-populated from the integration's settings, so most subscribers do not need to change them. For details on editing subscription settings, see the Subscription Configuration – Edit article.