# JD Edwards API Documentation: AIS REST, Orchestrator, BSSV and Connector Options > Source: https://netray.co/erp-help/jd-edwards-api-documentation-integration-options > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer JD Edwards EnterpriseOne exposes integration through the Application Interface Services (AIS) REST server, Orchestrator for no-code flows, older business services (BSSV, SOAP) for published business functions, and batch interfaces such as Z-files and UBEs. Third-party tools like Concur typically connect through these, often via an integration platform rather than directly. ## Kind advanced ## System jd-edwards ## Erp Oracle JD Edwards EnterpriseOne ## Module Integration / AIS, Orchestrator, Business Services ## Query jd edwards api documentation ## Alternate Queries - jd edwards erp system integration - concur integration with jd edwards - jde ais rest api - jde integration options ## Applies To JD Edwards EnterpriseOne 9.1 and later; AIS and Orchestrator are most complete on 9.2 and later tools releases. ## Steps ### Choose and use an integration option **Items:** - List the integration need: read data, create a transaction, trigger a process, or exchange files in batch. - For REST or JSON needs, deploy the AIS Server (it fronts the Enterprise Server) and confirm the base URL and token or basic authentication for a service account. - For no-code flows, build an orchestration in Orchestrator Studio that calls a form, a business function or a data request, and publish it as a REST endpoint through AIS. - For existing SOAP integrations, review the published business services (BSSV) in your environment and their WSDLs. - For bulk loads, use the Z-file interface: load the Z table, run the processor UBE, and review the error table for rejected rows. - Use a dedicated integration user with the minimum JDE security needed, and test in a non-production environment. - Document the endpoint, versions and fallback so upgrades do not break the integration silently. ## Sections ### Where the documentation actually lives **Body:** There is no single public API reference like a typical SaaS product. The AIS REST services (form service, data service, orchestrator service) are documented in the Oracle JD Edwards EnterpriseOne documentation for your tools release, and Orchestrator Studio shows the contract of each orchestration you publish. BSSV contracts come from the generated WSDLs in your own environment. Treat your own AIS server as the source of truth: it can show which services are enabled, and your orchestration definitions are the API you actually publish. Document those for consumers. ### Choosing between AIS, Orchestrator, BSSV and Z-files **Body:** AIS form and data services are quick for reads and for scripted use of existing applications. Orchestrator wraps logic into a named, versionable endpoint that other systems can call without knowing JDE forms, which is better for stable integrations. BSSV is the legacy route and still common where it was built years ago. Z-files remain the right choice for large batch loads and transactions that need the standard edit and error handling of the interface tables. **Code:** - POST https:///jderest/v2/tokenrequest { "username": "INTEGRATION_USER", "password": "***", "deviceName": "integration-1" } - POST https:///jderest/v2/dataservice { "targetName": "F0101", "targetType": "table", "dataServiceType": "BROWSE", "maxPageSize": "10" } ### Third-party connectors such as Concur **Body:** Expense and spend platforms usually integrate by exporting an accounting file or journal that JDE imports, through a vendor or partner connector, or through an integration platform that maps their API to a JDE interface. Which pattern you get depends on the connector vendor and your JDE version. Ask what the connector writes to (voucher batches, journal entry Z-files, address book) and who handles rejected records. Most operational pain comes from error handling, not from the happy path. ## Pitfalls - Exposing AIS to the internet without a gateway, TLS and a restricted integration user. - Using a named human's credentials for an integration, so password rotation breaks it. - Calling form service for high-volume work, which is slow compared with batch interfaces. - Not versioning orchestrations, so a change for one consumer breaks another. - Ignoring the Z-file error table, so rejected rows never get corrected. ## Ai Angle Because JDE publishes read and write surfaces through AIS and Orchestrator, a private AI layer can query your data through read-only orchestrations or data services and answer in plain language. Netray designs these with approval before any write-back and deploys on-prem so AIS and the model stay inside your network. ## Faq ### Does JD Edwards have a REST API? **Answer:** Yes. The Application Interface Services (AIS) server provides REST services for forms, data and orchestrations. Orchestrator lets you publish your own named endpoints on top of JDE logic without writing code in the application. ### Where is the JD Edwards API documentation? **Answer:** In the Oracle JD Edwards EnterpriseOne documentation for your tools release (AIS and Orchestrator guides), plus the contracts generated in your own environment: orchestration definitions and BSSV WSDLs. There is no single public reference for custom integrations. ### How does Concur connect to JD Edwards? **Answer:** Typically through a connector or integration platform that maps Concur expense or accounting extracts to JDE interfaces such as vouchers or journal entries. Details depend on the connector and JDE version, so confirm the supported pattern with the vendor. ### Should I use BSSV or Orchestrator for a new integration? **Answer:** For new work prefer Orchestrator and AIS, which are the direction Oracle has invested in. Keep BSSV only where existing integrations depend on it. ## Search terms jd edwards api documentation, jde ais rest api, jde orchestrator api, jd edwards erp system integration, concur integration with jd edwards, jde bssv web services, jde integration options, jde aisserver jderest, jde third party integration, jde rest endpoint --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json