Community setup guide · Customer guide
Legacy Migration
Existing two-digit community area codes were preserved as aliases and padded with a leading zero: 00 becomes 000. Existing owners, portals, local branches and block credentials remain intact. Network federation uses /v1/route with 10 digits and a new cen_net_ key. Old cen_live_ block keys are accepted only by /v1/legacy/route (7-digit Local Number) and the retained /v2/route (7 digits or legacy two-digit area + 7 digits). Update old v1 clients to /v1/legacy/route while migrating. The old v2 endpoint is a compatibility API, not a newer federation protocol. Existing two-digit portal links redirect to the same published portal. Configure each member Routing API and a network key before switching integrations.