Katana Integration Guide for Production Scheduling with SkyPlanner APS

Katana is one multi-tenant cloud product, so every customer runs the same API. It is a REST API, version v1, at https://api.katanamrp.com/v1, with an OpenAPI 3.0 spec at https://api.katanamrp.com/v1/openapi.json. Documentation lives in the Katana Developer Hub.

The endpoints a scheduler needs:

• Master data: /products, /materials, /variants, /recipe_rows, /bom_rows, /product_operation_rows.
• Orders: /manufacturing_orders, /manufacturing_order_operation_rows, /manufacturing_order_recipe_rows, /manufacturing_order_productions.
• Sequence: /manufacturing_order_rerank.
• Supply and demand: /inventory, /purchase_orders, /purchase_order_rows, /sales_orders, /sales_order_rows.

There is no /resources endpoint. Resources appear as resource_id and resource_name on product operation rows and MO operation rows.

Register a webhook with POST /webhooks, an HTTPS URL and the events you need. (source) The useful events for scheduling:

• manufacturing_order.created, .updated, .deleted, .in_progress, .blocked, .done
• manufacturing_order_operation_row.created, .updated, .in_progress, .paused, .completed
• current_inventory.material_updated, .material_out_of_stock
• purchase_order.* and purchase_order_row.*, including received
• product.*, product_recipe_row.* and sales_order.*

Payloads are thin: the resource type, action and an href. The receiver fetches the full object from the href. Each delivery carries an x-sha2-signature header (HMAC SHA-256) for verification. Your endpoint must answer 20X within 10 seconds, and Katana retries three times, at 30 seconds, 2 minutes and 15 minutes.

1. Initial master data load. Page through products, materials, variants, recipe rows and product operation rows, throttled under the rate limit. Build SkyPlanner workstations from the distinct resources on the operation rows and keep a 1:1 key. Set shifts, leave and overtime in SkyPlanner per workstation, since Katana has no resource calendar.

2. Order sync. Subscribe to MO, operation row, inventory and purchase order events. On each event, fetch the object from its href and update the job. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is received. A nightly reconciliation with updated-date filters catches any missed event.

3. Schedule write-back. Two calls put the plan into Katana:

• POST /manufacturing_order_rerank “moves one or more manufacturing orders to an exact place in the production schedule”. It takes up to 250 open MOs per request, placed at the top, bottom, or before or after a given MO. (source)
• PATCH /manufacturing_orders/{id} sets production_deadline_date. Katana accepts it only when automatic deadline calculation for that factory location is off. (source)

The rerank matters beyond the list. In Katana, “higher-priority MOs reserve required materials and subassemblies first”, so the SkyPlanner sequence also decides which MO gets stock in Katana.

4. Shop-floor confirmations. Operators log work with SkyPlanner Mobile Confirmations, Production Timer or Quick Log Mode. SkyPlanner writes status and actual time to the MO operation row. If a plant keeps the Katana Shop Floor App instead, SkyPlanner reads the operation row events. Pick one reporting channel per plant.

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

• Deadline mode wipes dates. “Once automatic mode is enabled, all manual deadlines will be overwritten and cannot be restored.” Decide the mode once, at kickoff.
• No resource calendar. Do not derive shifts from the single Weekly throughput value. Build them per workstation in SkyPlanner.
• Resources only on operation rows. Keep resource names stable in Katana, because they are the key to SkyPlanner workstations.
• Time units. planned_time_parameter is in seconds, per unit for per-unit operations and in total for process, setup and fixed types. Map the type correctly, or durations are off by the quantity.
• Make-to-order groups. In a rerank, MOs linked to the same sales order stay together, so sequence them as a group.
• Rerank semantics changed. Since October 7, 2026, the rerank endpoints place orders exactly where asked. Integrations written for the older behavior need a retest. (source)