Acumatica - Enable API Access

This article is for whoever connects an Acumatica order source inside DropStream — a fulfillment provider (3PL) or a merchant who manages their own DropStream account. You’ll add the store through DropStream’s Add Connection wizard. If a fulfillment provider is setting up DropStream for you, you don’t need this page — just gather your Acumatica API credentials and send them over.

Unlike many platforms, Acumatica does not use an “Authorize” sign-in popup. You type the credentials directly into the Store Setup step.

What you’ll need

• A DropStream account you can sign in to.
• Your Acumatica credentials from Acumatica - Get Your API Credentials: Instance URL, Client ID, Client Secret (Shared Secret), and the integration user’s Username and Password.
• Your Acumatica endpoint version (for example 24.200.001) if it differs from the default.

How DropStream connects to Acumatica

Every store connects through the same Add Connection wizard. For the full walkthrough of the wizard’s steps, see Add a Connection. This article covers only the Store Setup step, where you enter the Acumatica-specific details.

Enter your Acumatica details

1. In the Add Connection wizard, work through to the Store Setup step. Choose Create new store, give the store a Name, and select Acumatica as the Platform. The Acumatica credential fields appear below.

2. Fill in the connection credentials:

   Field	What it is	Example
   Instance URL	Base URL of your Acumatica instance	https://myerp.acumatica.com
   Client ID	The Connected Application’s Client ID (generated on save)	03539A80-…-7FBC92E9CD3F@MyCompany
   Client Secret	The Shared Secret value from the Connected Application	Ger2OU8nC58-R22…
   Username	Login of your Acumatica integration user	dropstream
   Password	Password for that integration user	••••••
   Tenant (Company)	Acumatica tenant/company name — only if your instance hosts more than one	MyCompany

   For where to find each value, see Get Your API Credentials.

3. Review the Endpoint & Order Settings. The defaults work for most instances — change them only if your Acumatica setup differs:

   Field	What it is	Default
   Endpoint Name	The contract-based API endpoint to use	Default
   Endpoint Version	The endpoint version matching your ERP build	24.200.001
   Order Type	The Acumatica order type to import	SO
   Default Warehouse ID	Optional — in shipment mode, restrict imported shipments to one warehouse (e.g. KNOX-01)	(blank)
   OAuth Scope	The token request scope; offline_access yields a refresh token	api offline_access
   Import orders via shipments	Import open Shipments as orders instead of open Sales Orders — see Sales-order mode vs. shipment mode below	Off
   Include package contents	Advanced — send per-package line allocation on tracking updates. Requires a tenant that exposes the packable-items pool.	Off

4. Click Add connection.

You can edit any of these values later by opening the store from Connections or Stores.

Sales-order mode vs. shipment mode

The Import orders via shipments toggle picks which Acumatica records DropStream imports — and, in turn, how it writes fulfillment back. Choose the mode that matches how your Acumatica workflow produces orders.

• Off — Sales-order mode (default). DropStream imports open Sales Orders (SO, or your configured Order Type). When the warehouse ships, DropStream creates a new Shipment in Acumatica from the fulfillment.
• On — Shipment mode. DropStream imports open Shipments instead — one per order. Use this when Acumatica already creates the Shipment itself (for example, when a sales order reaches the Shipping stage) and you only want DropStream to fulfill what Acumatica has staged. When the warehouse ships, DropStream updates that existing Shipment with the carrier, tracking number, and box details rather than creating a new one. In this mode, Default Warehouse ID (if set) limits the import to shipments for that warehouse.

If you’re unsure, leave it off — sales-order mode is the default and fits most setups. Switch to shipment mode only if your team confirms Acumatica generates the shipments you want DropStream to fulfill.

Notes

• Leave the defaults unless you have a reason to change them. Endpoint Name Default, Order Type SO, and Scope api offline_access match a standard Acumatica instance. Keep offline_access in the scope so DropStream receives a refresh token and can stay connected without re-entering the password.
• Import via shipments vs. sales orders. The Import orders via shipments toggle changes both what DropStream imports and how it writes tracking back — see Sales-order mode vs. shipment mode above before changing it.
• If authentication fails, the most common causes are a Shared Secret that has expired, a Client ID entered without its @<Tenant> suffix, or an integration user whose role lacks access to Sales Orders, Shipments, or Inventory — see Get Your API Credentials.