Develop Integrations with Web Services | APIs

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! 

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?

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!

Hi Acumatica Community!I’m releasing Acumatica Knowledge MCP, a free, read-only knowledge server for AI tools that support MCP.It gives AI assistants searchable Acumatica reference context across Help Wiki documentation, DACs and fields, OData entities, Contract-Based REST API entities, and Generic Inquiry XML examples.It does not require an Acumatica tenant connection. It is safe to use because it is read-only and does not write anything back to Acumatica.Setup is simple: add a single MCP URL to any agent or AI tool that supports MCP.Website with connection details and how it works:https://knowledge.acutools.netThis is the first public release, so feedback is very welcome. I’d especially appreciate hearing where the search results are useful, where they miss, and what Acumatica knowledge areas or tools you would like to see added next.I’m also happy to help anyone get it set up or answer questions.  

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

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 :-)

Trying to re-publish customisation as I am missing endpoint in copied Tenants.  Was hoping the missing endpoints will get created during the republish of customisation.  I am getting the following error.  Any idea what access level I need for my user. 

We are trying to use a push notification to send inventory data from a GI to an outside system. We have created several other push notifications that are working as expected but our inventory push is not.We are currently using px.objects.in.inventoryItem as our table.Results tab: InvenotryID, SiteID, LastModifiedDateTime, & QtyOnHand.Nothing is hitting the push when inventory updates. Thanks,

We are using Acumatica 2025 R2 and the contract-based REST API.We created a custom endpoint exposing:Shipment → ShipmentDetail → AllocationsWe need to split one component of a non-stock kit across two warehouse locations while keeping everything on one shipment line.Example:Shipment line: KIT-001, Shipped Qty. 2 COMPONENT-A requirement: 4 units at BIN-A COMPONENT-B requirement: 2 units at BIN-BDesired result:COMPONENT-A: 2 units at BIN-A and 2 units at BIN-C COMPONENT-B: 2 units at BIN-B, either as one allocation or two allocations of 1 each Kit shipment line remains at Shipped Qty. 2The equivalent operation works manually on the Shipments screen.Non-kit control testUsing the custom endpoint, we successfully split a regular stock-item shipment line by:Reducing the existing allocation quantity. Inserting a second allocation. Updating the newly assigned SplitLineNbr to the desired location in a second PUT.The request uses:PUT /entity/WMS/24.200.001/Shipment?$expand=ShipmentDetail/Allocat

I work in a furniture business and looking at ways to reduce manual entry of Sales Orders. We have many small sized customers who do not have advance tech ability and often send their order either as a PDF attachment or in the body of an Email.  They are not too interested in EDI.  I’m looking for a system can read these PDF/emails as they are the same format each time and automatically import and create a SO.  Currently only found Artsyl but I’d like to review a few.Does anyone use a system like this already?  I am very interested in you experiences and suggestions.Thanks

PaycomConnector — Paycom ↔ Acumatica Integration================================================Hi all,I've built a native Acumatica customization that integrates Paycom HR/Payroll with Acumatica 2025R2, and I'm gauging interest from the community before polishing it up for wider release.What it does------------   Employee sync — Bulk + per-employee API sync from Paycom. Creates/updates EPEmployee records with compensation, contact info, supervisors, departments, and GL codes. Automatic user login creation.   Reference data sync — Labor items, earning codes, tax codes, projects, tasks, and locations pulled from Paycom categories.   Labor cost import — Drag-and-drop CSV import from Paycom labor cost exports. Smart resolution of Paycom codes to Acumatica references. Custom cost engine preserves Paycom rates through time card submit/release.   Real-time webhooks — Inbound webhook receiver with HMAC signature validation, deduplication, and debouncing for live HR event processing.   Audit l

I'm looking for a way to manage a tenant's configuration as code — declarative files in a git repo I can review in a pull request, version, and re-apply to rebuild a tenant reproducibly.By "configuration" I mean setup data, not customization code: enabled features, company/branch structure, chart of accounts, ledgers, GL preferences, currencies, credit terms, financial calendars, and the like.The workflow I want is basically infrastructure-as-code — capture a tenant's setup into source files, edit them in git, apply to another tenant, then diff to catch drift.Customization Projects cover code but not this setup data. Snapshots are reproducible but are whole-database blobs — not human-readable or diffable in a PR. The REST API can push data, but it's a building block, not a desired-state workflow.Is there an existing tool or established pattern for this — a community tool, an ISV product, or something people have built in-house? Curious how others handle it.Thanks!

I’m trying to ship a sales order via the REST API.  This involves…Creating the shipment record Updating the quantities on the shipment Confirming the shipment Updating INThe actual quantity to ship comes from our internal custom WMS site, outside of and integrated with Acumatica.  Typically, the SO line item will have a linked Production Order.  When recording multiple Move transaction on the Prod order, the resulting Shipment will have multiple lines for the same item.  We rarely ever ship exact.  Depending on how production was recorded whether we had some extra pieces in stock already, the actual quantity to ship will frequently be different than the quantity ordered or allocated or produced.Admittedly, I don’t fully understand how the “allocated” calculations fit into all of this, or how they are determined based on quantity ordered and production quantities.  No matter what I try via the API, I run into the error of “quantity shipped is greater than the quantity allocated” when tr

I am getting a 406 Not Acceptable Error when trying to POST to {AcumaticURL}/24.200.001/Email endpoint.  My Payload is:{ "Subject": { "value": "Draft Email for Opportunity"}, "Body": {"value": "This is the body of the draft email."}, "MailStatus": { "value": "Draft" }, "ClassID": { "value": "Email" }, "IsIncoming": { "value": false }, "RelatedEntityNoteID": { "value": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx" }, "To": { "value": "recipient@somecompany.com" }, "From": { "value": "sender@mycompany.com" },}I have tried “NoteID”, “RelatedEntitiyNoteID” with the Note ID of the Opportunity, that I get from a GET I am out of ideas, good ole google hasn’t help either.   Any guidance would be helpful.   I also tried using the \activity endpoint as well, same 406. Headers have Content-Type:  application/json & Accept:  application/jsonAny help would be appreciated.

Hi everyone, I have created a community n8n node for the Acumatica REST API.n8n-nodes-acumatica - npmlekker-solutions/n8n-nodes-acumatica: Acumatica n8n NodeThere are 3 nodes you can use: Default / 25.200.001 Default / 24.200.001 Custom (You enter the Name / Version)On each defined resource on the endpoint, the following operations are allowed:Get List (GET) Get by ID/Keys (GET) Create/Update (PUT) Delete by ID/Keys Invoke Action Attach File Download File Custom API CallOther Notes:Custom fields are not handled yet on the DEFAULT endpoints, so just use the Custom Endpoint node.   For auth, only OAuth Authorization code flow is supported, but setting up a credential is very easy (There is a built in ‘Acumatica Credential’)If you are unsure how to use a community node:Using community nodes | n8n DocsHopefully this helps speed up your integrations using n8n! 

Hi all,I'm trying to create a prepayment invoice via the Acumatica Contract-Based REST API. I'm POSTing to:/entity/BDP/24.200.001/SalesOrder/CreatePrepaymentInvoiceOKWith payload:{  "entity": {    "OrderType": {"value": "SA"},    "OrderNbr": {"value": "0001170"}  },  "parameters": {    "PrepaymentPct": {"value": 100.00},    "CuryID": {"value": "GBP"}  }}I'm getting a 500 error: "The Create button is disabled" (PXActionDisabledException). The SO status is fine — I can create the prepayment invoice manually without issue in SO301000 and SO501000.My understanding is that the Acumatica commerce connector creates prepayment invoices via the API successfully — so there must be a way to do this. Has anyone solved this, or can point me to how the commerce connector achieves it?Thanks, James

We are an engineer to order environment with an external, non-Acumatica product configurator. The output of the configuration tool is a JSON collection of operations, phantom sub assemblies, and materials. We are looking for an API based solution to create Production Orders linked to a Sales Order Line with a custom BOM. We're able to create the Production Order, but are running into difficulties identifying the correct method of providing the Operation collection along with their associated Materials [Stock Items]. We’ve tried using ProductionOrder, ProductionOrderDetail, and the CreateProductionOrder/CreateProductionOrderProcess[All] Action and have not had any success getting the Operations collection to populate.For example, in ProductionOrderDetail, we’ve supplied the Operations like below:{        "AllowPreassigningLotSerialNumbers": {        "value": true    },    "Branch": {        "value": "PRODWHOLE"    },    "CostingMethod": {        "value": "Actual"    },    "Hold": {     

According to this article, /entity is the way to get a site’s build number from the API. When will this also include the patch segment (e.g. 26.100.0175.2)?

For building an ETL pipeline to warehouse Acumatica data, are there any approaches to detect deleted records besides the traditional primary key comparison method?

Hi everyone,I'm currently working with Acumatica Cloud ERP 2024 R1 and using the REST API to manage file attachments on various documents (e.g., Sales Orders, Invoices, etc.).What I can already do:I’m successfully attaching files to entities using the files endpoint like this:PUT /entity/Default/24.200.001/files/PX.Objects.AR.CustomerMaint/BAccount/{entityID}/{filename}This works well — the file is successfully attached and visible under the Files tab on the customer screen.What I want to do next:I would like to add a comment to this file — just like you can do manually in the UI by entering a comment when attaching a file.My assumption so far:From what I understand, this may require two separate REST calls: PUT — attach the file (already working ✅) Some second request to update the file record and add a comment (❓) But I haven't found a working REST example for that.My Questions: Is it possible to attach a comment to a file via REST API in Acumatica 2024 R1? If yes — what is the r

We’re having an issue where Acumatica 2025R2 is not respecting the dates that we are sending through the API (MANUFACTURING/23.200.001) when creating Move Entries.  It seems to always default to the system date.  Here is the JSON we’re sending and the date is 2026-06-01 but the resultant Move Entry in the web interface shows today’s date.  Any thoughts or suggestions?{"Document" : {"Date" : {"value" : "2026-06-01T00:00:00+00:00"},"ProductionNbr" : {"value" : "00137227"},"Hold" : {"value" : false},"ControlQty" : {"value" : 8},"OrderType" : {"value" : "RO"},"PostPeriod": {"value": "062026"}},"Details" : [{"Quantity" : {"value" : 8},"ProductionNbr" : {"value" : "00137227"},"UOM" : {"value" : "EA"},"OrderType" : {"value" : "RO"},"OperationNbr" : {"value" : "0010"},"InventoryID" : {"value" : "301238"}}]}

I am creating a Payment/Prepayment through the Acumatica Contract-Based REST API and applying it to a Sales Order using the OrdersToApply detail.The same API payload structure works for several Sales Orders, but it fails for some specific orders with the following error:An error occurred during processing of the field Order Nbr.:The order cannot be applied, the specified combination of the order type and order number cannot be found in the system.Sample request structure:{ "CashAccount": { "value": "XXXXX" }, "CurrencyID": { "value": "USD" }, "CustomerID": { "value": "CXXXXXXXXXXX" }, "Description": { "value": "Shopify Payment XXXXX" }, "Hold": { "value": false }, "OrdersToApply": [ { "AppliedToOrder": { "value": 69.08 }, "OrderNbr": { "value": "ES88832" }, "OrderType": { "value": "ES" } } ], "PaymentAmount": { "value": 69.08 }, "PaymentMethod": { "value": "SHOPPAY" }, "PaymentRef": { "val