Reference · built on requestConnectorERP & finance

Acumatica Cloud ERP

Customers, sales orders, shipments, invoices, and stock items from Acumatica through its contract-based REST API and push notifications.

Request accessPricing ↗

About

Acumatica Cloud ERP is a mid-market ERP. Its contract-based REST API works with business objects defined by an endpoint contract, so customization or renamed screen fields do not break clients. The system endpoint is named Default; its URL carries the version, for example /entity/Default/25.200.001. Push notifications, configured on the Push Notifications (SM302000) form, send JSON to a webhook, message queue, or SignalR hub when a generic inquiry's results change.

An operator on Fibric reads sales orders with their shipments, stock items with quantities by warehouse, and invoices, and proposes new orders, shipments, or tracking numbers for your approval. You get a receipt with each one: the change, the reason, and how to undo it.

This is a reference listing. It documents what Fibric would read from Acumatica Cloud ERP and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Customers, including tax zone assignments
  • Sales orders with detail lines and related shipments, retrievable in batches
  • Shipments with tracking numbers, freight cost, and the invoice prepared from them
  • Stock items with attributes, unit conversion rules, prices, and quantities by warehouse, including modified-since lists
  • Sales invoices and payments, with or without a linked order
  • Opportunities, plus push notifications for any generic inquiry whose result set changes

Proposed actions

  • Target capability: propose a sales order, with unit of measure, discounts, allocations, or tax parameters set
  • Target capability: propose a shipment for one or more sales orders and its confirmation
  • Target capability: propose writing a tracking number or updating freight cost on a shipment
  • Target capability: propose preparing an invoice for a shipment or a payment against an invoice
  • Target capability: propose a note or attachment on a stock item

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Ship what the warehouse can actually pick

    Read open sales orders and stock by warehouse, then propose one shipment per order with allocations already set.

    With Short Pick, Split Shipment

  • Push the tracking number back the moment the label prints

    Take the carrier's tracking number and propose writing it to the Acumatica shipment so customer notices match.

    With Tracking Sync, Missed Delivery

  • Notice a stock-out before the storefront does

    Subscribe to a push notification on item quantities and flag SKUs whose available quantity crosses your floor.

    With Oversell Watch, Stockout Forecast

Requirements

  • An Acumatica ERP instance with the Default system endpoint, or a custom endpoint from the Web Service Endpoints (SM207060) form
  • A registered OAuth 2.0 or OIDC client application, or a user type set aside for API sign-in
  • License capacity for API users, concurrent requests, and requests per minute, shown on the License Monitoring Console (SM604000)
  • A generic inquiry and a push notification definition on the Push Notifications (SM302000) form for change feeds
Authentication
OAuth 2.0 or OpenID Connect through an application registered in Acumatica; direct sign-in with POST /entity/auth/login and name, password, tenant, and branch still works but is slated for removal.

Limits

  • The license caps API users, concurrent requests, and requests per minute; a trial license allows two API users
  • Once the past minute reaches half the per-minute limit, new requests are delayed; the queue declines a request after 20 waiting or 10 minutes
  • Sessions that are never signed out count against the API user limit and can block other applications
  • The endpoint contract fixes which entities, fields, and actions exist; anything else needs a custom endpoint

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Acumatica Cloud ERP ↗

Questions and answers

What does contract-based mean?
Each endpoint has a contract that fixes the entities, fields, actions, and methods available through it. The contract does not change with customization or localization, so a renamed screen element still maps to the same field name in the API.
How does Acumatica notify an external system of changes?
Through push notifications. You define a data query (a generic inquiry or a built-in query) and a destination: webhook, message queue, SignalR hub, or a custom type. Acumatica sends JSON with the inserted and deleted rows when the query results change.
What limits does the license impose on the API?
Three: the maximum number of web services API users, the maximum concurrent requests, and the maximum requests per minute, all visible on the License Monitoring Console (SM604000). A sign-in beyond the user limit fails with an error, and bursts beyond half the per-minute limit are delayed.
Ask about Acumatica Cloud ERP

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Acumatica Cloud ERP through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy