Acumatica Installation Instructions

Search for Connected Applications from the Acumatica portal and create a new Application using the Authorization Code flow type.

Set Mode to Sliding Expiration. It is not recommended to configure the application with absolute expiration; otherwise, reconfiguration and reauthorization will be required after expiration.
To use Password Flow authentication, select the Resource Owner Password Credentials (ROPC) from the Flow drop-down.
This method will require iPaaS to have the subscription updated whenever the Acumatica user password is changed.

In the Secrets tab, click Add Shared Secret.

Copy the Value and keep it in a safe place. You will use it when configuring the integration.

When you save the Connected Application Record, the Client ID is generated. Copy and keep this in a safe place for later use.

Record the following settings to use in configuring the subscription:

Go to Subscriptions Management > Subscriptions and click Search Certified Integration Marketplace and Subscribe.

Click the Acumatica Integration title.

On the Subscription Detail page, click the Subscribe button.

Enter the Name of the subscription and select a version from the Versions drop-down. It can be set to any relevant and unique subscription name within the company where this subscription is created. The version is unique to each Acumatica instance.

Select Create Default Mappings (recommended).
​NOTE: If you don’t want to create default mappings and want to create all mappings from scratch by yourself, then uncheck this box.

Provide the API URL endpoint for your Acumatica instance.

Enter the Username and Password. These are the same username and password as used by your Acumatica instance.

Enter the Client ID, copied from the Acumatica Connected Application with Flow of Resource Owner Password Credential.

Enter the Client Secret, copied from new Secret Key added to Acumatica Connected Application with Flow of Authorization Code

Enter the Scope, for OAuth Flow, this is api offline_access.

Enter the Grant Type, for OAuth Flow, this is api offline_access.

Enter the Acumatica Version. use 22.200.001.

Enter the Redirect URL, which is different depending on the iPaaS environment.

Set the Transaction Tracking Number Poll Search Days. This setting determines how far back the system looks for shipment data during its initial scan. If you don't provide a number, the system will default to 4 days. For example, if you set the value to 100, the system will retrieve shipment records from the last 100 days. This feature helps ensure you don't miss any historical transactions, which is helpful during the initial setup or after a system outage.

Enter the Time Zone Offset. This is a required setting for a subscription preset because it ensures shipment records are retrieved based on your local business time, not the system's UTC time. This ensures you receive tracking updates aligned with your region's working hours.

Set Sales Order Duplicate Checking to True or False. Setting this preset to True in your subscription settings enables the system to check for duplicate sales orders using the iPaaS transaction number before they are transferred. If you don't set this value, no duplicate validation will be performed. This gives you the flexibility to turn this feature on or off based on your specific business needs.

Enter the API Throttle Limit. This setting prevents any single integration or user from overwhelming the system with too many requests. It protects system performance by controlling the number of API requests that can run simultaneously, ensuring fair usage.

Enter the API Throttle Seconds. This defines the time window during which the API Throttle Limit is measured. If an integration makes too many requests within this time window, additional requests are rejected until the window resets.

Enter the number of Concurrent Connections. This specifies the maximum number of simultaneous API connections that (Undefined variable: Integrations.placeholder) can process for a user or integration. If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.

Enter the number of Concurrent Batch Executions. This specifies the maximum number of simultaneous batch executions that can be processed by an integration at any given time. If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.

Click Apply to save the settings.

Go to the Acumatica Subscription that was created

Click the Authentication icon found in the toolbar

A new browser window will open, requesting permission for the application.

Click Yes, Allow.

After the confirmation page appears, click Allow, then close the page.

Refresh the subscription page in (Undefined variable: General.CompanyName).
The access token values should now be present if successful:

If an error occurs, verify that the provided settings meet the requirements described above.

Initiate a sample data pull. (To iPaaS.com)

Initiate a sample data push. (From iPaaS.com)

Run an end-to-end business process.

Validate key features like field mappings, workflow triggers, and logging.

Review integration logs in iPaaS.com.