Backend Modules

Canonical backend module root:

backend/core-api/app/modules

Current module domains:

• analytics_reporting
• circles
• escrow_chain
• feed_community
• groups
• identity_access
• integrations
• messaging_matrix
• notifications
• observability_ops
• payments_finance
• platform_admin
• plugins
• profiles_membership
• projects
• reputation
• teams
• work_management

Router composition

Main router composition lives in:

backend/core-api/app/api/v1/api.py

Important prefixes:

• /api/v1/auth
• /api/v1/roles
• /api/v1/api-keys
• /api/v1/members
• /api/v1/teams
• /api/v1/groups
• /api/v1/tasks
• /api/v1/tasks-v2
• /api/v1/reviews
• /api/v1/deliverables
• /api/v1/payments
• /api/v1/transactions
• /api/v1/tokens
• /api/v1/funding
• /api/v1/subscriptions
• /api/v1/escrow-chain
• /api/v1/webhooks
• /api/v1/notifications
• /api/v1/audit
• /api/v1/observability
• /api/v1/plugins/*
• /api/v1/external

Compatibility paths

backend/core-api/app/main.py includes compatibility aliases for escrow/web3 routes:

• /api/v1/chain
• /api/v1/blockchain
• /api/v1/escrows
• /api/v1/jobs
• /chain/v1

Legacy v1 routers are controlled by ENABLE_LEGACY_V1_ENDPOINTS, except compatibility paths that remain intentionally mounted.