Check if /api/v1 route is required or not.

[ketankauntia]

What went wrong?

list what services are using it. or we can remove support for it.

Steps to reproduce

description says it all.

Expected behavior

No response

Environment

No response

[linisha15]

@ketankauntia hi i would like to work on this , can you assign me this issue .

[ketankauntia]

@linisha15 i have assigned it to you.

I do support the use of ai tools. but make sure you understand what you write. incase you are using ai to reply, plz dont. you can just give a thumbs up emoji and it will work.

all the best.

[anirudhskk]

Hey! I would like to work on this. Could you please assign this issue to me? Thank you!

[anirudhskk]

Currently the services that use the api/v1 are:

1. Year detail web page service:

• The api is used to fetch a full org list for that year with pagination loop (100 limit) (/api/v1/years/${year}/organizations )

• The api is used to fetch the aggregate metrics like total orgs/projects/students, technologies and topics.

• Both of these calls go through lib/api.server.ts, which constructs same-origin absolute URLs and forwards cookies. So this is first-party internal API usage in production SSR.

2. External project sync script (this is ingestion from an another service)

• in scripts/fetch-external-project.ts api fetches page 1 from https://www.gsocorganizationsguide.com/api/v1/projects to discover pagination and then the script fetches the remaining pages in chunks.

3. Local API pagination test (dev validation):

• scripts/test-pagination.js sets BASE_URL to http://localhost:3000/api/v1. It verifies pagination behaviour by calling health, organizations, and projects endpoints. Only for manual dev testing.

4. Local API smoke test (dev QA script):

• scripts/test-api.sh sets BASE_URL to http://localhost:3000/api/v1. It curls many v1 endpoints and checks expected status codes (eg /health, /meta, /organizations etc)

Thank you!