OMS Endpoints¶
Camel → OMS. cm-osor-sys is the only OMS caller — every OMS call in the mesh goes through it.
Host per environment¶
The path is identical across environments; only the host changes.
| Environment | OMS host |
|---|---|
| dev | oms-sandbox.popsockets.com |
| qa | oms-qa.popsockets.com |
| stage | popsockets-merged-staging.diffagency.com |
| prod | popsockets-oms.diffagency.com |
Endpoints¶
Prepend the per-env host above to each path. All are under /api/v3.
| Call | Path |
|---|---|
| Base (osor_order) | /api/v3/osor_order |
| Order confirm (fulfill) | /api/v3/osor_order/fulfill_orders |
| NAV release status | /api/v3/osor_order/status |
| PrintStation batches | /api/v3/print_station/batches |
| Item delete | /api/v3/item_master/products |
| Gladly customers | /api/v3/customers |
| Gladly orders | /api/v3/osor_order/orders |
Full URL, worked example
prod order-confirm = host popsockets-oms.diffagency.com + path /api/v3/osor_order/fulfill_orders
→ https://popsockets-oms.diffagency.com/api/v3/osor_order/fulfill_orders
Related: OMS system overview · NAV order release · Endpoint map home