Connect API

Detect frontend HTTP calls and match them to backend route definitions, creating API_ENDPOINT edges in the knowledge graph.

How It Works

The connector scans frontend files for HTTP calls and backend files for route definitions, normalizes URL paths, and matches them using a multi-strategy algorithm:

1. Exact match — normalized paths identical
2. Prefix-augmented — prepends routePrefix to frontend path
3. Suffix match — strips routePrefix from backend, matches remainder
4. Deep strip — strips leading {param} segments from backend (handles class-level {companyId} routes)
5. Controller resolution — resolves .NET [controller] placeholder to actual class name

Zero-Config Auto-Detection

No configuration needed. The connector auto-detects frameworks by scanning for marker files:

Auto-Run Behavior

The connector runs automatically in these situations:

You almost never need to run this manually. The graph CLI handles it automatically.

Custom Config (Optional)

For projects with custom HTTP patterns (e.g., base class API service), add to docs/project-config.json:

{
    "graphConnectors": {
        "apiEndpoints": {
            "enabled": true,
            "frontend": {
                "framework": "angular",
                "paths": ["src/app/"],
                "customPatterns": ["this\\.\\s*(get|post|put|delete|patch)\\s*[<(]\\s*['\"]([^\"']+)"]
            },
            "backend": {
                "framework": "dotnet",
                "paths": ["src/Api/Controllers/"],
                "routePrefix": "api",
                "customPatterns": []
            }
        }
    }
}

Custom patterns extend (not replace) built-in framework patterns. Explicit config overrides auto-detected config for paths.

Manual Run

python .claude/scripts/code_graph connect-api --json

Steps (when manually invoked)

1. Run connector via Bash:
   bashCopy

   python .claude/scripts/code_graph connect-api --json
   

2. Report results: Frontend calls found, backend routes found, matches created, edge count

Matching Strategies

The connector tries 5 strategies in order (highest confidence first):

See Also

• Implicit Connections — For event buses, entity events: graphConnectors.implicitConnections[] in project-config.json. CLI: connect-implicit --json

Related Skills

• /graph-build — Build/update the knowledge graph (prerequisite)
• /graph-trace — Trace full system flow (API_ENDPOINT edges enable frontend-to-backend tracing)
• /graph-blast-radius — Analyze structural impact of changes
• /graph-query — Query code relationships in the graph

Closing Reminders

• MUST break work into small todo tasks using TaskCreate BEFORE starting
• MUST search codebase for 3+ similar patterns before creating new code
• MUST cite file:line evidence for every claim (confidence >80% to act)
• MUST add a final review todo task to verify work quality