Introducing Acumatica Cloud ERP: 2026R2
Technical discussions focused on Web Services and APIs for developers
Recently active
hello all,Can anyone guide me from where I can override the “From” mail id under the “Email Invoice” button of Invoices (SO303000) screen ?
Hi,I am trying to automate the generation of a SEPA XML file by executing the Export action on the Batch Payments screen in Acumatica (for example, batch 000435).To achieve this, I have: Created a custom REST API entity named BatchPayment in the endpoint DefaultExtended, version 24.200.001, including the Batch Summary fields. Added the Export action to this entity. Configured the action parameters corresponding to the Settings dialog that normally appears when clicking the Export button in the Acumatica interface. I am calling the following REST API endpoint:Method: POSTEndpoint:/entity/DefaultExtended/24.200.001/BatchPayment/ExportRequest body:{ "entity": { "id": "efd710ef-cb9b-f111-a84a-000d3ae74153" }, "parameters": { "BatchbookingBtchbookgtag": { "value": "Unity (False)" }, "Executiondate": { "value": "2026-11-13T00:00:00+00:00" }, "PaymentInformation": { "value": "One level per Batch" }, "PriorityInstrPrtytag": { "value": "None"
Hi Acumatica Support Team,We are facing an issue while uploading attachments to a Bill of Material (BOM) using the Acumatica REST API.Scenario:We need to upload a file to the following BOM record: BOM ID: BOM000023 Revision: * File Name: AACOMPUT01.jpg We are using the following API URL for uploading the attachment:http://localhost/AcumaticaQMS26R1/entity/ABPManufacturing/25.100.001/BillOfMaterial/BOM000023/*/files/AACOMPUT01.jpgWhen we execute the API request, we receive the following error:A potentially dangerous Request.Path value was detected from the client (*)Questions: What is the correct REST API URL and HTTP method (PUT) for uploading an attachment when the BOM Revision value is *? Does Acumatica support * as a valid Revision key in the attachment upload URL? Can we use %2A instead of * to avoid the ASP.NET request-path validation error? Is there any alternative supported approach for uploading attachments to a BOM with Revision *? Expected Result:We want to successf
Hello all,I have been struggling to create an import scenario where I’d like to delete the existing vendor records from the Non Stock items screen & add a new vendor & set it up as a default.
Goal: Create an appointment via the API.The stock API version 26 seem to allow setting of the appointment start date via the field ActualStartDate. However the End Date and Time can only be set via fields having the _Date and _Time suffixes. The Web Services management UI shows an error that the fields shouldn’t be hooked up this way, even on the default endpoint.Using the default endpoint, I’ve tried setting the date and time in various ways, but it’s not clear what format it accepts, and I’m getting inconsistent results. Timezone errors seem common.I cannot seem to create a custom endpoint. The UI does not appear to allow access to the end date fields, they aren’t in any of the mapped objects (what are those things anyway?), even though they are present in the DAC browser.Currently I can set an Actual Start Date and Duration via the default endpoint. I would have expected this to populate the End Date but it does not. I cannot set the scheduled dates reliably, sometimes it works
We are using the Acumatica 2026 R1 contract-based REST API (25.200.001) to create Stock Items and configure warehouse-specific Inventory Planning settings.Our goal is to create a stock item with two warehouses configured as follows:Warehouse Source Source Warehouse A001 Manufacturing B004 Transfer A001 The stock item uses the MRP planning method.BackgroundInitially, we attempted to create both warehouse records through StockItem.WarehouseDetails. However, the replenishment source values were being inherited or overwritten, resulting in both warehouses having the same source.We subsequently moved to the dedicated ItemWarehouse REST entity (IN204500 / INItemSiteMaint), using separate PUT requests for each warehouse.We also determined that, for MRP items, the standard ReplenishmentSource and ReplenishmentWarehouse fields do not appear to control the Inventory Planning settings correctly. Instead, the manufacturing-specific fields and their individual override flags must
Acumatica REST API vs ODataWhen to use what? A practical guide for integration developersI just wanted to share a few points to explain the difference between REST APIs and OData, as it might be helpful to understand how they differ and when to use each.QUICK TAKEAWAY Use REST API when an external application needs to interact with Acumatica business entities and perform supported business operations. Use OData when the requirement is to query and extract data exposed through Generic Inquiries.1. Understand the two approachesREST API exposes Acumatica business entities through endpoints. Depending on the entity and supported operations, an external application can retrieve, create, update, or delete records. Entity operations use Acumatica business logic and validations applicable to the exposed entity.OData (Open Data Protocol) provides a query interface for data exposed through Acumatica Generic Inquiries (GIs). It is designed primarily for reading structured data and supports query
Hi, we finally upgraded from 2023 to Build 2026.101.301.174 [26.101.0225.3]. Where can I find what Acumatica Report version is compatible with this version and where can I download it from?
Hello - Via an API, we are trying to update the 7th row under the Details section on the Numbering Sequencing screen but only the first row seems to update even though the NumberingSEQ ID is being referenced. Is there something we are missing?Thank you,Ashley
When using the REST API to get ProjectTransaction data, the detail items don’t seem to have a line number, where as the detail for JournalTransaction does have a line number. Does anyone know a good way to determine the unique key for the detail items of a project transaction as obtained using the REST API client? I’m trying to determine a unique key based on the key of the parent transaction (Module, ReferenceNbr) and information from the detail items. I’m assuming that the GUID value of the detail items is not persistent in the same manner as for top-level entities.I would prefer not to develop a customization for this; having sufficient key fields in the API data should be part of the system already.
Has anyone figured out how to Automatically create Sales Orders from Dynamics CRM and push that order information to an Acumatica Sales Order Record? I am trying to put together a Power Automate Flow that takes order information from Dynamics and push it to Acumatica. Issue I am running into seems to be finding the right trigger (I would like it to trigger when an order goes from a Quote to an Order in CRM, user pushes the button, create Order.) Then that newly created Order in CRM is then pushed to Acumatica as a new SO record.
Hello. Is it possible to create the Active directory user via API or Import scenario. The import doesn't create the user, even though it completes the import. Failing on the API side as well - I can create the native user but not API
In 25R2 I have an admin user account that has access to the AR Invoices and Memos, yet when I try to access the odata for the DAC, I get a 403 after entering my credentials.https://url.acumatica.com/t/tenant/api/odata/dac/ARTaxTran?$top=1The same user works on other DAC level odata endpoints. I also tried the odata4 url string:https://url.acumatica.com/ODatav4/tenant/ARTaxTran?$top=1I assume I’m missing something simple :-)
We are using the Acumatica contract-based REST API (25.200.001) to create Stock Items and their Warehouse Details.We need to create two warehouse detail records for a new stock item:Warehouse Replenishment Source Replenishment Warehouse A001 Manufacturing B004 Transfer A001 Our custom endpoint exposes WarehouseDetails under StockItem.The relevant fields are mapped to the Warehouses detail object, including: WarehouseID → Warehouse Source / ReplenishmentSource → Replenishment Source RepWhs / ReplenishmentWarehouse → Replenishment Warehouse The screen field was verified with Element Inspector as: Data Class: INItemSite Data Field: ReplenishmentSource View Name: itemsiterecords Business Logic: InventoryItemMaint ProblemIf we PUT a single WarehouseDetails record, the Replenishment Source is set correctly.For example, creating only A001 as Manufacturing works:{ "InventoryID": { "value": "TESTITEM" }, "WarehouseDetails": [ { "WarehouseID": { "v
Hello Team,I found the following error with payments.1. I have created a payment via API. The payment is being created successfully.2. Then I use a payment to allocate with invoice or credit memo via API to pay it.3. Send the payment with allocation to the invoice or credit memo to Acumatica via API.Acumatica returns the following error message:Payment update request returns the error message - "exceptionMessage": "An error occurred during processing of the field Reference Nbr.: Reference Nbr. 'AR.......' cannot be found in the system.\nPX.Data.PXOuterException: An error occurred during processing of the field Reference Nbr.: Reference Nbr. 'AR......' cannot be found in the system."When I repeat the same Payment update request after a period of time (in 1,5,10,20 minutes), Acumatica creates a payment successfully.Could you clarify what is the reason of this behavior?
For building an ETL pipeline to warehouse Acumatica data, are there any approaches to detect deleted records besides the traditional primary key comparison method?
Since upgrading from 24R1 to 26R1, I’ve been getting the following errors from the RESTAPI using the SO301000 screen:{"message":"A long operation is running for this screen in the current session. Please try again later."} This didn’t happen at all in 24R1 and the small number long running processes that I’ve found on the System Monitor screen only run for a couple of seconds at the most. Is there a way to prevent this error from occurring since I have no control over which schedules use PXLongOperation.StartOperation()?
Hello all,I have been trying to use the “Copy Order” action, present under QT order type - SO301000 screen via endpoint, however unable to do so: This is what I’m trying:Which is giving me 500 internal Server error. What is it that I’m missing? Would really appreciate guidance/help on this.
Hello Community,I’d like to know if there is an AcumaticaESignIntegration package currently available that I can download and install. I’ve seen references to eSign integration in the Marketplace and GitHub, but I’m not sure if there’s an official or updated package that can be directly applied to my Acumatica environment.Could anyone confirm if such a package exists, and if so, share the proper download link or installation guidance?Thanks in advance for your help!
I have created a Bill using PUT /Bill REST API endpoint and it created below data, the process also includes releasing the bill but I am encountering a “The document is out of balance” error. It seems the bill header total figures were not calculated correctly. For this bill, I created its own PO and PO Receipt with vendor’s Allow AP Bill Before Receipt unticked (3way match)On second screenshot, I checked the PO Receipt linked to the Bill and based on the Billing tab, it shows Billed Amount as 550 which is correct and matched with the Bill line’s Amount. I am not sure what needs to be added on the payload when calling /Bill API endpoint but when I used UI to create Bill from PO receipt, I don’t encounter the “The document is out of balance” error.Thanks!
Hi,We recently upgraded to 2021R2 and I am now unable to apply invoices to a payment via the API.The invoice can be applied manually without issue. I am seeing this error message:"An error occurred during processing of the field Reference Nbr.: Reference Nbr. 'IN150421' cannot be found in the system.\nPX.Data.PXOuterException: An error occurred during processing of the field Reference Nbr.: Reference Nbr. 'IN150421' cannot be found in the system.", This is the PUT command, using Default/17.200.001/Payment { "ReferenceNbr":{"value":"013185"}, "DocumentsToApply":[ { "AmountPaid": {"value" : "641.99" }, "DocType": {"value": "Invoice" }, "ReferenceNbr": {"value" : "IN150421" } } ]} Thanks in Advance for any help.
Hi everyone!Wanted to see if anyone in the community has experience using Appify alongside Acumatica, specifically connecting or integrating the two systems in any way.We’re working with a company that currently uses/has experience with Appify, and I’d love to hear if anyone has successfully connected it with Acumatica, what that integration looked like, and any lessons learned along the way.Any experience or insight would be greatly appreciated. Thanks!
In case we have:A store on eBay that we connect to from Shopify using Shopify Marketplace Connect App. Our Shopify Online store Acumatica ERP.Will we be able to connect to our eBay Store via the native Shopify Connector and synchronize our product listings between both Shopify and eBay stores i real-time using Shopify Connector for integration with the ERP?
If you've built an inbound webhook with PX.Api.Webhooks.IWebhookHandler, you've hit the same wall we (Claude and I) did: the platform hands you the request and leaves authentication entirely to you. The official sample compares a bearer token with != — no HMAC, no timing safety, no replay protection, and a secret hardcoded next to it. Every team ends up re-implementing signature verification, and most of the common mistakes (verifying re-encoded text instead of raw bytes, short-circuiting comparisons, distinguishable error responses) are invisible until someone exploits them.So we built it once, properly, and we're open-sourcing it under MIT:https://github.com/AISI-Dev-Co/AISI.AcumaticaWebhookAuthenticatorA complete, authenticated GitHub webhook is this:public class PushEventHandler : AuthenticatedWebhookHandlerBase{ protected override IWebhookAuthenticator CreateAuthenticator(IWebhookSecretProvider secrets) => new HmacAuthenticator(WebhookAuthPresets.GitHub(secrets));
Does anyone know how processing data with the Push Notifications (SM302000) screen impacts licensing restrictions?As we all know, when developing external solutions that integrate with Acumatica, we need to keep in mind licensing constraints since Acumatica is licensed on transactions and not on users.With that in mind, I know that the following are best practices:When reading data from Acumatica, use OData instead of an API endpoint because OData calls are not subjected to the Maximum Number of Web Services API Requests per Minute limitation on the License Monitoring Console (SM604000) screen that API calls are subjected to. OData calls are essentially free, at least until the private equity firm that owns Acumatica decides to monetize them 😀 Keep in mind that any data you write back into Acumatica using the API is subject to the same Maximum Number of Commercial Transactions and Maximum Number of ERP Transactions limitation on the License Monitoring Console (SM604000) screen that yo
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.