[Bug] Event routes have a double /api prefix — all event endpoints return 404 in production

[MehtabSandhu11]

Summary

eventRoutes is registered in app.ts with the prefix /api/events. However, every route handler inside apps/backend/src/routes/event.ts also hard-codes /api/events as the path prefix. The result is that all event endpoints resolve to /api/events/api/events/..., which is unreachable by any client.

Root Cause

apps/backend/src/app.ts line 100:

await app.register(eventRoutes, { prefix: '/api/events' });

apps/backend/src/routes/event.ts lines 39, 101, 135, 175, 214:

app.post('/api/events', ...)           // actual path: /api/events/api/events
app.get('/api/events/:slug', ...)      // actual path: /api/events/api/events/:slug
app.post('/api/events/:slug/join', ...) // etc.

Every other route file (e.g. cards.ts, profiles.ts) correctly uses relative paths like '/' and '/:id'. Only event.ts duplicates the prefix.

Expected Behaviour

• POST /api/events → create event
• GET /api/events/:slug → get event
• POST /api/events/:slug/join → join event

Proposed Fix

In apps/backend/src/routes/event.ts, change all absolute route paths to relative ones:

// Before
app.post('/api/events', ...)
app.get('/api/events/:slug', ...)
app.post('/api/events/:slug/join', ...)
app.delete('/api/events/:slug/leave', ...)
app.get('/api/events/:slug/attendees', ...)

// After
app.post('/', ...)
app.get('/:slug', ...)
app.post('/:slug/join', ...)
app.delete('/:slug/leave', ...)
app.get('/:slug/attendees', ...)

Acceptance Criteria

• All 5 event routes respond at their documented paths under /api/events
• The double-prefix pattern does not appear in any other route file
• Existing event tests pass after the fix

Please assign this issue to me under GSSoC

[Nightkilller]

Hi @MehtabSandhu11,

I would like to work on this issue under GSSoC'26.

I reviewed the reported bug and understand that the event routes are being registered with the /api/events prefix in app.ts while the route definitions in event.ts also include the same prefix, resulting in paths such as /api/events/api/events/... and causing all event endpoints to return 404.

My plan is to:

• Update all event route definitions in apps/backend/src/routes/event.ts to use relative paths (/, /:slug, /:slug/join, etc.) instead of hard-coded /api/events prefixes.
• Verify that all event endpoints are accessible through their intended routes under /api/events.
• Review other route files to ensure similar double-prefix issues do not exist elsewhere.
• Run the existing test suite and confirm event-related functionality continues to work as expected.
• Keep the change focused and avoid unrelated modifications.

Please assign this issue to me. Thank you!

[Harxhit]

@MehtabSandhu11 I have assigned this issue to you.

[Pcmhacker-piro]

Hi @Harxhit,

I’m interested in contributing to this project and would love to work on this issue. I have experience working on open-source contributions and would be happy to implement the required changes.

Could you please assign this issue to me? Thanks!

[github-actions]

Hey @ShantKhatri (Project Admin) and @Harxhit (Maintainer),

This issue (previously assigned to @MehtabSandhu11) has been automatically unassigned because no linked pull request was found after the scheduled check.

If work is in progress, please open a PR and link it to this issue to keep the assignment.

[Harxhit]

@Pcmhacker-piro I have assigned this issue to you.