-
-
Notifications
You must be signed in to change notification settings - Fork 304
Closed
Labels
Description
The bug
The contributing documentation references incorrect API endpoints (/api/v1/) for local development verification, but the backend only serves /api/v0/. Additionally, the production nginx configuration routes to /api/v1/ while both staging and the backend use /api/v0/, creating environment inconsistency.
To Reproduce
Steps to reproduce the behavior:
- Follow the contributing guide setup instructions in
CONTRIBUTING.mdordocs/contributing.md - Run
make runto start local development environment - Navigate to
http://localhost:8000/api/v1/as instructed in the documentation - See 404 Not Found error
Expected behavior
- Documentation should reference the correct API endpoint (
/api/v0/) that matches the actual backend implementation - All environments (local, staging, production) should have consistent API routing
Are you going to work on fixing this?
- Yes (Ready to send Pr)
- No
Additional context
Root Cause: After refactoring in commit ad007b7 (Sept 10, 2025) "Refactor API to a separate app, add v0 (#2245)"
What was updated:
- Backend:
backend/settings/urls.pychanged fromapi/v1/toapi/v0/ - Staging config:
proxy/staging.confchanged fromapi/v1toapi/v0
What was missed:
- Production config:
proxy/production.conf:30still hasapi/v1 - Documentation:
CONTRIBUTING.md:284,CONTRIBUTING.md:305 - Documentation:
docs/contributing.md:134,docs/contributing.md:148,docs/contributing.md:150
Current State:
- Backend serves:
/api/v0/ - Local: Direct access to
/api/v0/ - Staging: Routes
/api/v0/ - Production: Routes
/api/v1/ - Documentation: References
/api/v1/
Affected Files:
Screenshots
Testing locally shows:
http://localhost:8000/api/v0/→ Returns:{"message": "Welcome to the OWASP Nest API v0", "docs_url": "http://localhost:8000/api/v0/docs"}
http://localhost:8000/api/v1/→ Returns: 404 Not Found

Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done