# SYSPRO API integration: e.net business objects, REST, EDI and Office > Source: https://netray.co/erp-help/syspro-api-integration-e-net-rest-edi-office > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SYSPRO integrates mainly through e.net Solutions, a set of business objects that take and return XML, exposed through COM, .NET and web service interfaces including a REST style service in recent SYSPRO 8 releases. EDI and Office integration cover document exchange and spreadsheet work. Pick the route by direction, volume and who owns the code. ## Kind advanced ## System syspro ## Erp SYSPRO 8 ## Module e.net Solutions / Integration ## Query syspro api integration ## Alternate Queries - syspro erp integration - syspro erp api - syspro 8 api - syspro edi integration - syspro 8 office integration ## Applies To SYSPRO 7 and 8. REST availability and exact service names depend on the SYSPRO 8 release, so confirm with the e.net documentation for your build. ## Steps ### Choose and build a SYSPRO integration **Items:** - Write down the job: direction (in, out, both), volume, latency and who triggers it. - Use the table below to pick between business objects, web services, EDI, Office integration or direct read-only SQL. - Create a dedicated integration operator in SYSPRO with only the program rights the objects need. - Start with a query object (for example INVQRY or ARSQRY) to prove logon and parameters, then move to a transaction object such as SORTOI. - Build the XML parameters and document from the object's published schema, and validate before you send. - Handle the XML result: check for error nodes, log the full response and make writes idempotent so a retry cannot create duplicates. - Test in a copy company with realistic data, including bad input. - Monitor the integration operator, the service and failures after go-live. ## Sections ### Which route fits which job **Body:** There is no single SYSPRO API. Business objects handle transactional writes with full business logic. Query objects read data the way SYSPRO sees it. EDI handles trading partner documents. Office integration serves finance and planning users who live in Excel. Direct SQL is for read-only reporting. A common mistake is writing straight to SYSPRO tables. That skips validation, stock movement and GL posting, and corrupts data in ways that surface months later. Use business objects for every write. **Code:** Job Best route Create or change orders, receipts e.net business objects (SORTOI, PORTOI ...) Read a customer, stock, order Query objects (ARSQRY, INVQRY, SORQRY ...) Call from web or cloud app e.net web service / REST service Trading partner documents SYSPRO EDI, or middleware mapping to objects Excel based entry and reporting Office Integration Bulk read-only reporting SQL views or replica, never writes ### How an e.net call works **Body:** Every call has three parts: a logon to get a session id, a business object call with a parameter XML and a document XML, and a logoff. The object returns XML with the result or error nodes. Reuse sessions for batches rather than logging on per record, as logons are expensive and consume licences. Business objects respect the same rules as the user interface, so a locked period, missing GL setup or invalid stock code returns an error in the XML. That is a feature: your integration inherits the checks. **Code:** PO-1001 CUST001 ### EDI and Office integration **Body:** SYSPRO has EDI capability, and many sites also use a VAN or middleware that maps partner formats (X12, EDIFACT) to business object calls. Decide where mapping lives and keep acknowledgements and error queues visible to the business, not only to IT. Office Integration lets users work in Excel and Word against live SYSPRO data. It suits ad hoc analysis and structured data entry, but it is not a replacement for a controlled integration. Treat it as a user tool with the same rights as the operator. ## Pitfalls - Writing directly to SYSPRO tables instead of using business objects. - Logging on and off for every transaction, exhausting licences and time. - Using a personal operator for an unattended integration. - Ignoring error nodes in the XML and assuming success. - No idempotency key, so a retry creates a duplicate order. ## Ai Angle Netray adds a private AI layer above SYSPRO: ERPray answers questions from live data through read-only query paths, and agents can draft business object calls for a person to approve before anything is written. Models run on your own servers, so order and customer data stay inside your network. ## Faq ### Does SYSPRO have a REST API? **Answer:** Recent SYSPRO 8 releases expose e.net business objects through a REST style web service in addition to the older COM, .NET and SOAP interfaces. Check the e.net documentation for your exact release before you design around it. ### Can I just query the SQL database? **Answer:** For read-only reporting, yes, ideally against a replica or views so you do not slow production. For anything that changes data, no. Use business objects so validation and GL postings run. ### How do I handle EDI with SYSPRO? **Answer:** Either use SYSPRO's EDI capability or a middleware or VAN that maps partner documents to business object calls. Whichever you choose, keep an error queue and acknowledgement trail that operations staff can see. ### What licence does an integration need? **Answer:** Integrations consume e.net sessions and may need specific licence entitlements. Confirm with your SYSPRO partner before you design high volume calls. ## Search terms syspro api integration, syspro erp api, syspro 8 api, syspro e.net business objects, syspro rest api, syspro edi integration, syspro office integration, syspro erp integration, syspro web services --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json