Camel Internal Routes (APIM)

Service-to-service calls between Camel's own cm-* apps. Every inter-service call routes through the APIM gateway — services never dial each other's pods directly.

The pattern

https://integration-{nonprod|prod}.popsockets.com/{env}/cm-<service>/<path>

• integration-nonprod.popsockets.com for dev / qa / stage; integration-prod.popsockets.com for prod.
• {env} is the profile segment: dev, qa, stage, or prod.
• cm-<service> is the callee app; the rest is that service's route path.

So the same logical route differs across environments only in the {nonprod|prod} host and the {env} segment — everything after cm-<service>/ is stable.

Representative live routes

Shown as cm-<service>/<path> (the stable suffix). Prepend https://integration-nonprod.popsockets.com/<env>/ for dev/qa/stage, or https://integration-prod.popsockets.com/prod/ for prod.

Caller → callee	Route suffix
order-prc → osor-sys (NAV release)	cm-osor-sys/order/nav-release
order-prc → osor-sys (Cirro confirm)	cm-osor-sys/order/cirro-confirmation
order-prc → printprod (create)	cm-printprod-sys/order/create
edi-prc → cirro-sys (B2B create)	cm-cirro-sys/order/edi-940-create-b2b-order
edi-prc → int-service-sys (FT lookup)	cm-int-service-sys/fulfillment-tracking/by-cirro-order-code
product-prc → cirro-sys (inventory)	cm-cirro-sys/inventory/list

Full URL, worked example

prod order-prc → osor-sys NAV release → https://integration-prod.popsockets.com/prod/cm-osor-sys/order/nav-release

qa, same route → https://integration-nonprod.popsockets.com/qa/cm-osor-sys/order/nav-release

---

Related: Camel topology · Endpoint map home