# SYSPRO API Documentation: e.net Business Objects and REST > Source: https://netray.co/erp-help/syspro-api-documentation-rest-and-enet-business-objects > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SYSPRO's integration layer is e.net Solutions: a set of business objects (queries, transactions and setup objects) that take and return XML, reachable through a COM or .NET interface or through web services hosted by the e.net components. The documentation ships with the product help and the schema (XSD) files for each business object; a typical call is Logon, then Query or Transaction Post, then Logoff. ## Kind how-to ## System syspro ## Erp SYSPRO e.net Solutions ## Module Integration / e.net business objects / REST ## Query syspro api documentation ## Alternate Queries - syspro rest api - syspro e.net business objects - syspro web services api - syspro api authentication logon ## Applies To SYSPRO 7 and 8. The exact web-service and REST endpoints depend on release and how e.net Communications Load Balancer and web services are installed. ## Steps ### How to make your first SYSPRO API call **Items:** - Install and licence e.net Solutions on the application server and confirm the e.net Communications Load Balancer service is running. - Create a dedicated SYSPRO operator for the integration with only the program access it needs, and use a strong password stored in a secrets store. - Call the Logon business object with operator, company, company password and language. It returns a session identifier (a GUID) that every later call must pass. - Call a Query business object (for example a stock or customer query) with the session ID and an XML parameter block. Start read-only. - For writes, use the Transaction Post call for a transaction business object, with an XML parameters block and an XML data block that match the object's XSD. - Always call Logoff when finished so you do not leak licence sessions. Handle errors by parsing the returned error XML, not by checking only the transport status. ## Sections ### Where the documentation is **Body:** The authoritative reference is the SYSPRO e.net help in the product, the SYSPRO developer and partner resources, and the schema files installed with SYSPRO. Each business object has an input and an output XSD and sample XML, so the schema files are often the fastest way to see exactly which fields a transaction expects. Business object names are short codes that follow SYSPRO's program naming, for example a sales order transaction object. The existing page on creating a sales order through the SORTOI business object shows the shape of a real transaction call. ### e.net versus REST **Body:** The long-standing pattern is XML in, XML out through the e.net interface. Newer releases add web service and REST-style access layered on the same business objects, which is convenient for cloud and JSON consumers. Because endpoints and availability depend on release and installation, confirm them in your release documentation rather than copying a URL from another site. Whichever door you use, the same rules apply: one session per integration, validated XML against the XSD, and idempotent design. SYSPRO will not stop you posting a purchase order twice, so your integration must record what it has already sent. **Code:** - A100 ### Security and operations **Body:** API access runs under a SYSPRO operator, so role and program access control what the integration can do. Use a separate operator per integration so audit trails and licence use are clear, and avoid sharing the interactive user of a person. Plan for licence cost and concurrency. Each active session consumes a licence slot, and a loop that logs on per record is slow and wasteful. Log on once, process a batch, log off. ## Pitfalls - Logging on for every record instead of reusing a session, exhausting licences and slowing the integration. - Skipping Logoff after errors, leaving orphaned sessions. - Trusting only HTTP or transport success; SYSPRO returns business errors inside the XML. - Hardcoding an endpoint copied from a forum; endpoints differ by installation. - Posting transactions without idempotency, creating duplicates on retry. ## Ai Angle Netray adds a private AI layer to the SYSPRO you already run, including on-prem installs where the SQL Server and application server never leave your network. ERPray answers questions over live SYSPRO data with read-only SQL or e.net queries it shows you, under the operator's own SYSPRO security, so a planner or accountant can ask the question in plain language and see exactly which tables or business objects produced the answer. Any write-back, such as posting a transaction, goes through a human approval step. The model is open-weight and runs on your own GPUs, so company data is not sent to a public AI service. ## Faq ### Does SYSPRO have a REST API? **Answer:** SYSPRO exposes its business objects through e.net and, in newer releases, web service and REST-style access over the same objects. Availability and endpoints depend on your release and installation, so check the documentation for your version before designing against a URL. ### What is an e.net business object? **Answer:** It is a SYSPRO component that performs a query or transaction using XML input and output, for example creating a sales order or reading stock levels. Each has an XSD describing the XML, which you can use to validate requests. ### How does authentication work? **Answer:** You call a Logon object with an operator, company and passwords. SYSPRO returns a session GUID, which you pass on every later call, and you end the session with Logoff. Permissions are those of the SYSPRO operator you used. ### Where do I find the field definitions? **Answer:** In the e.net help and the XSD and sample XML files installed with SYSPRO. The schemas show required and optional fields for each business object, and are the quickest way to debug a rejected call. ## Search terms syspro api documentation, syspro rest api, syspro e.net, syspro business objects, syspro web services, syspro api logon, syspro integration xml, syspro xsd --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json