This article walks you through connecting your Acumatica instance to iPaaS.com. You will create authentication credentials in Acumatica, install and configure the Acumatica subscription in iPaaS.com, authorize the connection, and verify that data can move in both directions.
The integration communicates with Acumatica over its Contract-Based REST API using OAuth 2.0. The Acumatica company it works in is set by the connected application's Client Id, which Acumatica generates in the form <GUID>@<Company>. Two authentication flows are supported, described below.
Before You Begin
Before installing the integration, you need to create and copy several authentication values from Acumatica. Have administrative access to your Acumatica instance available, because creating a connected application and a shared secret requires it.
You will collect the following from Acumatica during the steps below:
The API Url of your Acumatica instance.
The Client Id generated by the connected application.
The Client Secret (the shared secret value) created for the connected application.
For the password flow only, the Username and Password of the Acumatica user the integration will act as.
Use an Acumatica user dedicated to the integration. Acumatica limits how many API sessions can be open at once, both for each user and across the license. The integration normally uses one API session per subscription, which stays open until its access token expires (about one hour); people and other tools signing in through the API as the same user use up that user's sessions and can cause the integration's sign-ins to be refused. See the Acumatica Known Limitations article.
The integration works through Acumatica's standard web service endpoint (Default), so no Acumatica customization is needed. With the shipped filters, Acumatica customer accounts are captured as iPaaS.com Customers unless they are in a customer class named COMPANY, which makes them iPaaS.com Companies. To capture companies, create that class in Acumatica (Customer Classes, screen AR201000) with the defaults Acumatica requires on its accounts, such as a statement cycle, and assign it to the company accounts; see Acumatica Known Limitations.
For background on the Acumatica side of this setup, see the Connected Applications and OAuth 2.0 topics in the Acumatica Contract-Based REST API documentation at help.acumatica.com (accessed 2026-06-26).
Choosing an Authentication Method
Two methods can be used to configure authentication between Acumatica and iPaaS.com:
OAuth flow (Authorization Code): The recommended and more secure method. You authorize the connection once through your browser, and iPaaS.com stores a refresh token that is used to renew access automatically.
ROPC flow (Resource Owner Password Credentials): This method requires saving the Acumatica Username and Password in your subscription settings, which may be visible to other users in your iPaaS.com company. Because the credentials are stored, you must update the subscription in iPaaS.com whenever the Acumatica user password changes.
The OAuth flow is recommended due to its enhanced security. The main difference between the two is the Grant Type you set in the subscription (and the matching flow type you select on the Acumatica connected application): authorization_code for OAuth, password for ROPC.
Create the Acumatica Connected Application
Sign in to the Acumatica company the integration should use. From the Acumatica portal, search for Connected Applications and create a new application. Set the flow type to Authorization Code for the OAuth flow, or to Resource Owner Password Credentials (ROPC) if you intend to use the password flow.
Set Mode to Sliding Expiration. Configuring the application with absolute expiration is not recommended; otherwise the application will require reconfiguration and reauthorization after it expires.
On the Secrets tab, click Add Shared Secret.
Copy the secret Value and keep it in a safe place. Acumatica displays it only once. You will enter it as the Client Secret when configuring the subscription.
For the OAuth (Authorization Code) flow only: on the Redirect URIs tab, add the iPaaS.com Redirect Url for your environment, exactly as shown:
Staging:
https://stagingportal.ipaas.com/customer/subscription-mgmt/subscriptions/authorization/appProduction:
https://portal.ipaas.com/customer/subscription-mgmt/subscriptions/authorization/app
Acumatica compares this value with the authorization request character for character. Without it, authorization fails with the message "Sorry, there was an error : unauthorized_client". The ROPC flow does not use a redirect URI.
Save the connected application record. Saving generates the Client Id. Copy and keep this value in a safe place for later use.
Record the following values to use when configuring the subscription:
API Url: the address of your Acumatica instance.
Client Id: generated on the connected application after saving, shown above the application name.
Client Secret: the shared secret value you copied in step 4.
Install the Integration and Configure the Subscription
In iPaaS.com, go to Subscriptions Management > Subscriptions and click Search Certified Integration Marketplace and Subscribe.
Click the Acumatica integration title.
On the Subscription Detail page, click Subscribe.
Enter a Name for the subscription and select a Version. The name can be any relevant, unique value within the company where the subscription is created.
Format: [Product Name] - [Environment/Purpose]
Example: Acumatica - Release
Select Create Default Mappings (recommended).
Note: If you would rather build all mappings from scratch yourself, leave this box unchecked.
Configure the subscription settings. The settings below are presented as Required and Optional preset settings, followed by advanced settings. Enter the values you collected from Acumatica and the values appropriate for your iPaaS.com environment.
Required Settings
API Url: The address of your Acumatica instance (for example, your test or sandbox site address). This is the base address the integration uses for all requests.
Client Id: The Client Id copied from the Acumatica connected application.
Client Secret: The shared secret value copied from the Acumatica connected application.
Scopes: The OAuth scopes requested. For both flows, this is
api offline_access.Grant Type: The OAuth grant type. For the OAuth (Authorization Code) flow, this is
authorization_code. For the ROPC (password) flow, this ispassword.Version: The Acumatica endpoint version your instance supports (for example,
22.200.001). The version is unique to each Acumatica instance.Time Zone Offset: Your time zone's offset from UTC, as a whole number of hours (for example,
-5). The integration shifts the start time of the shipment tracking number poll by this many hours. The setting is used only by that poll; the customer, company, contact, stock item, and sales order polls work in UTC. Enter a whole number only: a value with minutes, such as-05:00, or a fractional value, such as5.5, is read as 0 and no offset is applied. Enter0if no offset is needed.
Optional Settings
Username: Required only for the ROPC (password) flow, and used only when Grant Type is
password. The same username used to sign in to your Acumatica instance.Password: Required only for the ROPC (password) flow. The same password used to sign in to your Acumatica instance. Because this value is stored in the subscription, update it here whenever the Acumatica user password changes.
Redirect Url: Required for the OAuth (Authorization Code) flow, and must be the same value you added to the connected application's Redirect URIs tab. This value differs by iPaaS.com environment:
Staging:
https://stagingportal.ipaas.com/customer/subscription-mgmt/subscriptions/authorization/appProduction:
https://portal.ipaas.com/customer/subscription-mgmt/subscriptions/authorization/appTransaction Tracking Number Poll Search Days: Determines how far back the integration looks for shipment and tracking data during its initial scan. If left blank, the integration defaults to 4 days. For example, a value of 100 retrieves shipment records from the last 100 days. A larger value helps avoid missing historical transactions during initial setup or after a system outage.
Sales Order Duplicate Checking: Set to True or False. When set to True, the integration checks for duplicate sales orders using the iPaaS.com transaction number before they are transferred into Acumatica. If left unset, no duplicate validation is performed.
Advanced Settings
These settings tune request throughput and are optional. Leave them at their defaults unless you have a specific reason to change them.
Concurrent Batch Executions: The maximum number of batch executions the integration processes at one time. Requests beyond the limit are queued until an active execution finishes. Subscribers should validate an appropriate value in a staging environment before relying on it in production.
Note: Your subscription view may also expose general platform throughput controls (for example, request-rate and concurrent-connection limits). Leave these at their platform defaults unless directed otherwise by iPaaS.com Support.
Click Apply to save the settings.
Authorize the Connection
How you complete authorization depends on the flow you chose.
OAuth Flow
With the subscription settings saved, initiate the OAuth flow to generate an access token for communicating with Acumatica.
Open the Acumatica subscription you just created.
Click the Authenticate icon in the toolbar. A new browser window opens, requesting permission for the application.
Click Yes, Allow.
When the confirmation page appears, click Allow, then close the page.
Refresh the subscription page in iPaaS.com. If authorization succeeded, the access token values are now present.
If an error occurs, verify that the settings you entered meet the requirements described above, then reauthorize. If the browser window shows "Sorry, there was an error : unauthorized_client" instead of the Acumatica sign-in page, check the connected application: Flow is Authorization Code, Active is selected, the Redirect URIs tab contains the Redirect Url exactly as entered in the subscription, and the subscription's Client Id (including its
@<Company>suffix) belongs to this application.
Note: Acumatica OAuth 2.0 access tokens expire after a period of time and are removed from the subscription's stored data. The stored Refresh Token is used to regenerate the access token automatically, and the integration also reconnects on its own after an Acumatica restart. If the refresh token has expired, click the Authenticate icon again to reauthorize.
ROPC (Password) Flow
For the password flow, no browser authorization step is required. After you save the subscription with the Username, Password, Client Id, Client Secret, Scopes, and a Grant Type of password, the integration requests an access token directly using those credentials. Transfers may then be performed without additional authorization.
Post-Installation Verification
After completing the installation, perform these checks to confirm the connection works.
Data sync test:
Initiate a sample data pull (to iPaaS.com), for example a Manual Sync of one sales order by its order type and number (for example SO|000080). The first scheduled sales order poll only records its start time and does not pull orders that already exist in Acumatica.
Initiate a sample data push (from iPaaS.com).
Functionality test:
Run an end-to-end business process.
Validate key behavior such as field mappings, trigger subscriptions, and logging.
Review the integration's activity under Dashboard / Integration Monitoring / Error Logs in iPaaS.com.
Note: A successful save of the subscription does not by itself confirm that Acumatica accepted the credentials. Confirm the connection by running the data sync test above and reviewing the results under Dashboard / Integration Monitoring / Error Logs.
Support and Troubleshooting
Click the Help button on any iPaaS.com page to contact Support or to search the documentation.
Documentation: Search the documentation from the search bar at the top of this article.
Support Portal: Click the Help and Support button at the lower-right of the window.
Contact Information: Contact iPaaS.com.