Infor SyteLine

SyteLine Web Service Creation and Integration Guide

SyteLine's integration architecture exposes business logic through both SOAP and REST web services built on the IDO layer. Every IDO in SyteLine is automatically available as a web service endpoint, but building production-grade integrations requires understanding authentication, payload optimization, error handling, and the nuances of the Mongoose web service stack. This guide covers creating, securing, and consuming SyteLine web services.

IDO Web Services: SOAP and REST Exposure

SyteLine exposes IDOs as web services through two mechanisms. The legacy SOAP interface is provided by the IDORequestService.svc endpoint, which accepts XML-formatted IDO requests and returns XML responses. The newer REST interface, available in CloudSuite Industrial 10.x+, is exposed through the Mongoose REST API gateway at /IDORequestService/MGRestService.svc/. Both interfaces accept the same core operations: LoadCollection for queries, UpdateCollection for inserts/updates/deletes, and InvokeMethod for custom method calls. The REST API uses JSON payloads and supports OData-style query parameters including $filter, $select, $orderby, and $top. Configure web service access through the Web Service Configuration form and control which IDOs and methods are exposed through the Web Service Security form.

  • SOAP endpoint: /IDORequestService/IDORequestService.svc with XML request/response payloads
  • REST endpoint: /IDORequestService/MGRestService.svc/ with JSON payloads and OData query support
  • Both endpoints support LoadCollection, UpdateCollection, and InvokeMethod operations on any registered IDO
  • Control IDO and method exposure through Application > Web Service Security configuration form

Authentication and Token Management

SyteLine web services support multiple authentication modes configured in the Mongoose web service configuration. Token-based authentication is the recommended approach: clients POST credentials to the CreateSession endpoint, receive a session token, and include that token in subsequent request headers. The token references a server-side session entry in the SessionInfo table with configurable timeout (default 20 minutes). For service-to-service integration where no interactive user exists, create a dedicated SyteLine service account with minimal permissions and use the non-interactive authentication endpoint. Implement token refresh logic in your integration code to handle session expiration gracefully—a common mistake is to cache tokens indefinitely and handle the resulting 401 errors reactively rather than proactively refreshing.

  • Use CreateSession endpoint to obtain authentication tokens for subsequent API calls
  • Session tokens map to SessionInfo table entries with configurable timeout (default 20 minutes)
  • Create dedicated service accounts with minimal permissions for system-to-system integrations
  • Implement proactive token refresh logic to avoid 401 errors during long-running integration jobs

Integration Patterns and Error Handling

Production integrations against SyteLine require robust error handling because the Mongoose web service layer returns errors in multiple formats depending on the failure type. Authentication failures return HTTP 401 with no body. IDO validation failures return HTTP 200 with error details in the response payload's ErrorMessage property. Unhandled server exceptions return HTTP 500 with a SOAP fault or JSON error object. Your integration client must handle all three patterns. For high-volume integrations (e.g., EDI processing), use the bulk UpdateCollection pattern that sends multiple rows in a single request rather than individual calls per record. Implement idempotency by including unique external reference keys and checking for existing records before inserts. Log every request and response payload for troubleshooting—SyteLine's error messages are often generic, and the request payload is essential for diagnosis.

  • Handle three error patterns: HTTP 401 (auth), HTTP 200 with ErrorMessage (validation), HTTP 500 (server)
  • Use bulk UpdateCollection with multiple rows per request for high-volume integrations like EDI
  • Implement idempotency with external reference key checks to prevent duplicate record creation
  • Log complete request and response payloads—SyteLine error messages alone are insufficient for diagnosis

Building SyteLine integrations? Our team has delivered hundreds of web service integrations for manufacturing—let us architect yours.

Talk to an ExpertSee a Demo

Related Resources

Infor SyteLine

SyteLine REST API Integration Guide

Integrate SyteLine via REST APIs. IDO web services, authentication, payload design, and integration patterns for CloudSuite Industrial.

Infor SyteLine

SyteLine EDI Integration Complete Guide

Integrate EDI with SyteLine CloudSuite Industrial. Trading partner setup, transaction mapping, AS2 configuration, and EDI compliance for manufacturers.

Infor SyteLine

SyteLine IDO Custom Property and Method Creation

Create custom IDO properties and methods in SyteLine. Property mapping, method signatures, stored procedures, and .NET method development guide.

Back to All Resources