Skip to content

fix(listing): require an authenticated session on sponsor utility endpoints - #1468

Open
rajanpanth wants to merge 1 commit into
SuperteamDAO:mainfrom
rajanpanth:pr4-gate-utility
Open

fix(listing): require an authenticated session on sponsor utility endpoints#1468
rajanpanth wants to merge 1 commit into
SuperteamDAO:mainfrom
rajanpanth:pr4-gate-utility

Conversation

@rajanpanth

Copy link
Copy Markdown

check-slug, email-estimate and featured-posts under /api/sponsor-dashboard/listing are only called from the authenticated listing builder but had no session check. Adds a getUserSession gate to each, matching the other sponsor-dashboard routes, so they aren't callable anonymously.

Checked all call sites before changing:

  • featured-posts / email-estimate — relative fetch from React Query, browser-side, cookies sent.
  • check-slugfetchSlugCheck uses plain axios rather than @/lib/api, so no Authorization header; getPrivyToken falls back to the privy-token cookie, so this still authenticates.

Happy to adjust if any of these are intended to be public.

pnpm check-types and pnpm lint pass.

…points

check-slug, email-estimate and featured-posts under
/api/sponsor-dashboard/listing are only used from the authenticated
listing builder but had no session check. Add a getUserSession gate to
each so they aren't callable anonymously, matching the other
sponsor-dashboard routes.
@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown

@rajanpanth is attempting to deploy a commit to the Superteam Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@rajanpanth, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 026ba41b-9a43-44f3-8876-83355dee9461

📥 Commits

Reviewing files that changed from the base of the PR and between af39bd1 and b6c0163.

📒 Files selected for processing (3)
  • src/app/api/sponsor-dashboard/listing/check-slug/route.ts
  • src/app/api/sponsor-dashboard/listing/email-estimate/route.ts
  • src/app/api/sponsor-dashboard/listing/featured-posts/route.ts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant