SupplyOn SCC APIs are based on a clear separation of responsibilities:
| API Type | Purpose | Typical Usage |
| GET API | Business object retrieval | Reading data from SupplyOn |
| POST API | Business object creation | Sending data into SupplyOn |
This design closely follows the logic of standard EDIFACT processes:
- POST APIs are used to actively push business data into SupplyOn.
GET APIs are used to pull business data from SupplyOn.
In simple terms:
- POST = "I want to create or send something"
- GET = "I want to retrieve or read something"
Business object overview (direction shown as Buy-side Customer / Sell-side Customer ( Supplier ) relative to SupplyOn ):
| Description | Message | Direction | Method | Mode |
|---|---|---|---|---|
| Send business objects | Orders | Buy-side Customer → SupplyOn | POST | Asynchronously |
| Delivery Schedules | Buy-side Customer → SupplyOn | |||
| Kanbans | Buy-side Customer → SupplyOn | |||
| Stock Movements | Buy-side Customer → SupplyOn Sell-side Customer ( Supplier ) → SupplyOn |
|||
| Goods Receipts | Buy-side Customer → SupplyOn | |||
| Demand Responses | Sell-side Customer ( Supplier ) → SupplyOn | |||
| Advanced Shipping Notifications / Forwarder Pickup Advices |
Sell-side Customer ( Supplier ) → SupplyOn |