Sylob ERP Integration Guide for Production Scheduling with SkyPlanner APS

Sylob documents two public REST APIs: “L’ERP Sylob expose deux types d’API REST publiques (autrement nommées \”webservices\”) qui autorise la lecture et l’écriture de données.” (Forterro knowledge base)

1. API REST Système d’information (read). It runs a saved query (requête) built in the activity “Interroger le système d’information”. The query’s own call URL comes from “Autres actions” > “Afficher le web service”, in the form /rest/query/{identifiantQuery}/resultat. Parameters set the result limit, number formatting, query variables and the result structure. Results come as XML by default, or as JSON with the header Accept: application/json. This API is included with the ERP.
2. API REST Action (read and write). It runs an action defined in the activity “Gérer les actions web service”, the Sylob action catalogue. It exposes two operations: GET /rest/v2/action/{code}/describe returns the data schema of an action, and POST /rest/v2/action/{code}/execute runs it with a JSON body. Action types include:

– Modification de données: changes one or more fields of a record through Sylob’s quick-edit mechanism. Describe lists the editable fields. – Message EDI: creates, changes or deletes records through an EDI message. – Scénario de saisie: runs an entry scenario, question by question. Sylob’s own example is “Déclarer un début ou une fin”, declaring the start or end of an operation (Sylob_Action_006). – Publication, upload and download of documents.

1. EDI messages. The Sylob EDI engine handles exports and imports. A standard message, Sylob_Recup_Decl_Pro, retrieves production declarations. (Forterro)
2. Files and ETL. Sylob ERP Cloud offers “Intégration de fichiers via SFTP pour une migration facile des intégrations existantes.” (Sylob) Query results can also be exported to Excel, which is the fast path for the SkyPlanner trial.

Sylob’s public knowledge base documents no outbound webhook subscription. Changes reach SkyPlanner by polling saved queries that filter on open OFs and recent changes, on a schedule you set.

Sylob protects the ERP against heavy querying. Since release 2025.Q2 a company parameter, “Protection des API”, turns on throttling per user and paging of large results, and Sylob announces it as systematic from release 2026.Q2. Responses carry RateLimit headers, and a call over the quota returns HTTP 429 Too Many Requests with a Retry-After value. (Forterro) Design the sync for it: incremental queries, paging, and backoff on 429.

On the other side, SkyPlanner sends webhooks when state or the schedule changes, so the write-back to Sylob is event-driven.

1. Initial master data load. Build one saved query per object (articles, nomenclatures, gammes, work centers, employees) and read them through the Système d’information API, or load them once from an Excel export. Map work centers deliberately. A Sylob centre de charge is a group of resources, so a center with three machines usually becomes a workstation group with three workstations in SkyPlanner.

2. Order sync. Read firm OFs with their operations, plus stock and open purchase orders. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is marked Delivered. So the schedule checks both stock and incoming purchases.

Schedule firm OFs, not CBN suggestions. Suggestions change with the next net requirements run.

3. Schedule write-back. For every operation the engine placed or moved, the integration calls a Modification de données action on the OF operation (Opération d’ordre de fabrication) with planned start, planned end and work center. The action runs through Sylob’s own quick-edit logic, the same as a planner editing the operation. Describe returns the editable fields, so the integration validates its payload before the first call. A record being edited by a user returns a planned failure; retry it on the next change.

4. Shop-floor declarations. Operators log work with SkyPlanner Mobile Confirmations or the Production Timer. Start and finish go back through the “Déclarer un début ou une fin” scenario. Timelogs and quantities become production declarations on the same OF operation: setup time, run time, quantity made, scrap and operation finished. If your plant already declares through Sylob Apps or shop-floor terminals, keep one channel for declarations to avoid double entries.

5. Ownership and conflict rules. Write them down before go-live:

SkyPlanner does not need CADPLAN or Sylob’s finite planning activities. Let SkyPlanner own operation dates, because two planners writing the same dates overwrite each other. Once SkyPlanner owns them, Autopilot reschedules automatically on every meaningful change and the new dates go back to Sylob.

• Action API license. Reading through saved queries is included. Writing through the action catalogue needs the Sylob “Webservice” module, or an API license on MyForterro. Plan it with your Sylob contact before the write-back phase.
• Queries are your contract. The read side depends on saved queries. Name them clearly, pass filters as variable attributes at run time, and version the queries with the integration.
• Work center groups. One Sylob work center can hold several machines. Decide per center whether SkyPlanner sees one workstation group or individual machines.
• Backward scheduling and load runs. Sylob schedules backward to need dates, and a scheduled load calculation can replan late OFs. Agree which activity, if any, still writes operation dates once SkyPlanner owns them.
• Setup and run time units. Check units and whether setup is per OF or per piece before import. Wrong units distort every duration.
• Calendars. Work center week patterns and exceptions must cover the scheduling horizon, or capacity disappears from the plan.
• Throttling. Sylob limits calls per user and pages large results. Incremental polling stays well inside the quota.
• CORS and browsers. Server-to-server calls avoid CORS. Browser clients need allowed origins configured on the Sylob side.