Spares Part Master Sync: One Part per Request (billofmaterials/inbound_sync)

Last updated: November 4, 2026

Overview

Teams integrating an ERP (e.g., SAP/CPI) with L2L Spares often use billofmaterials/inbound_sync to create and sync part masters. This explains how to send multiple parts.

Does inbound_sync accept batches?

No. billofmaterials/inbound_sync accepts one part per POST request. It doesn't support an array or batch format. To send 100 parts, make 100 calls.

Recommended approach

  • Throttle your calls. Add a short delay between calls rather than sending them all at once.

  • Back off and retry on timeouts, HTTP 500 errors, or rate-limit responses.

  • Use a dedicated API user/key for the integration so its activity is easy to trace.

Initial load vs. ongoing delta feed

Scenario

Recommended method

Initial plant setup (bulk load of parts)

The spares import template (Setup → File Import) is usually easier.

Ongoing delta feed

Pull the parts changed in the ERP since the last run and POST each one to inbound_sync.

Related

  • Spares API Integration Workflow

  • API Best Practices and Guidelines

  • 429, 414, 499, 405 Errors - API call failure error messages

  • Spares File Import