API - api/spotify/album - migrate to vercel

[sweetmantech]

Summary by CodeRabbit

• New Features
  • Added a new Spotify album API endpoint that enables retrieval of complete album information by ID, with optional market-specific data filtering for localized results. The endpoint includes automatic Spotify service authentication, comprehensive input validation, detailed error handling with appropriate HTTP status codes, and full CORS support to facilitate secure cross-origin requests from web and mobile clients.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
recoup-api	Ready	Preview	Dec 4, 2025 6:29am

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Walkthrough

A new Spotify album API endpoint is implemented with GET and OPTIONS handlers, including query validation for album ID and optional market parameters, access token generation, and integration with the Spotify API wrapper for error handling.

Changes

Cohort / File(s)	Summary
Spotify Album API Route app/api/spotify/album/route.ts	Implements GET and OPTIONS handlers to serve Spotify album requests, delegating to getSpotifyAlbumHandler and managing CORS preflight responses.
Spotify Album Request Handler lib/spotify/getSpotifyAlbumHandler.ts	Processes Spotify album requests by validating query parameters, generating access tokens, calling getAlbum, and returning responses with appropriate HTTP status codes and CORS headers.
Spotify Album Client lib/spotify/getAlbum.ts	Fetches album data from Spotify API by ID with optional market parameter, handling authentication via Bearer token and returning normalized response with album data or error.
Query Parameter Validation lib/spotify/validateSpotifyAlbumQuery.ts	Defines Zod schema for album query parameters (required id, optional market), validates URLSearchParams, and returns either validated data or a 400 error response with CORS headers.

Sequence Diagram

sequenceDiagram
participant Client
participant Route as API Route<br/>(route.ts)
participant Handler as Handler<br/>(getSpotifyAlbumHandler)
participant Validator as Validator<br/>(validateSpotifyAlbumQuery)
participant TokenGen as Token Generator<br/>(generateAccessToken)
participant SpotifyClient as Spotify Client<br/>(getAlbum)
participant SpotifyAPI as Spotify API
Client->>Route: GET /api/spotify/album?id=...&market=...
Route->>Handler: forward request
Handler->>Validator: validate query params
Validator->>Validator: parse & schema check
alt Validation fails
Validator-->>Handler: 400 error response
Handler-->>Route: return error
Route-->>Client: 400 error
else Validation succeeds
Validator-->>Handler: validated params
Handler->>TokenGen: generate access token
alt Token generation fails
TokenGen-->>Handler: error
Handler-->>Route: 500 error response
Route-->>Client: 500 error
else Token generated
TokenGen-->>Handler: access token
Handler->>SpotifyClient: getAlbum(id, market, token)
SpotifyClient->>SpotifyAPI: GET /v1/albums/{id}
alt API request fails
SpotifyAPI-->>SpotifyClient: error response
SpotifyClient-->>Handler: { album: null, error }
Handler-->>Route: 502 error response
Route-->>Client: 502 error
else API request succeeds
SpotifyAPI-->>SpotifyClient: album data
SpotifyClient-->>Handler: { album, error: null }
Handler-->>Route: 200 success response
Route-->>Client: album data + CORS headers
end
end
end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

• Error handling consistency: Verify error handling is uniform across validation, token generation, and Spotify API call stages
• CORS header implementation: Confirm getCorsHeaders is correctly applied to all response types (success, 400, 500, 502)
• Access token expiration: Validate that token generation and caching strategy (if any) is appropriate
• API client robustness: Check that getAlbum properly handles network errors, malformed responses, and rate limiting scenarios

Poem

🐰 A Spotify burrow we've built with delight,
Albums now fetch through API so tight!
Validation and tokens, all in their place,
CORS headers grace every response with grace.
Hop-hop, the endpoint now ready to play! 🎵

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'API - api/spotify/album - migrate to vercel' accurately describes the main change: adding a new Spotify album API route with CORS handlers and validation logic.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch sweetmantech/myc-3608-api-apispotifyalbum-migrate-to-vercel

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (4)

app/api/spotify/album/route.ts (1)

5-15: Route wiring and CORS handling look good; consider a small export simplification

OPTIONS correctly returns a 200 with shared CORS headers, and GET cleanly delegates to getSpotifyAlbumHandler, matching the pattern you likely use elsewhere. As an optional cleanup, you could re-export the handler directly:

export{getSpotifyAlbumHandlerasGET}from"@/lib/spotify/getSpotifyAlbumHandler";

This keeps the route file even thinner, but your current implementation is perfectly fine if you prefer explicit functions here.

Also applies to: 17-31

lib/spotify/getSpotifyAlbumHandler.ts (1)

57-66: Consider wrapping album data instead of spreading into the root

Right now the success payload flattens the Spotify album object into the top-level response next to status. That can make it harder to evolve the API later (e.g., adding your own metadata) without risking key collisions with Spotify’s fields. Consider returning something like:

returnNextResponse.json({status: "success",
album,},{status: 200,headers: getCorsHeaders()},);

This is a non-breaking internal tweak if consumers are new, but it’s fine to keep as-is if you’re matching an existing contract.

lib/spotify/getAlbum.ts (1)

1-35: Album fetch logic is correct; consider enriching error information

The URL construction, optional market handling, and Bearer auth are all correct, and the { album, error } contract is straightforward. As an incremental improvement, you might capture more context on failures:

if(!response.ok){constbody=awaitresponse.text().catch(()=>"");return{album: null,error: newError(`Spotify API request failed (${response.status}): ${body}`),};}

Optionally, you could also give the function an explicit return type that’s shared with the handler to keep typing consistent across the module boundary.

lib/spotify/validateSpotifyAlbumQuery.ts (1)

5-8: Validation is sound; response shape naming could be clearer

The Zod schema and safeParse usage over URLSearchParams look good, and returning a 400 NextResponse with CORS on failure cleanly isolates validation concerns. One small nit: the field name missing_fields may be misleading when the error is due to an invalid value rather than an absent param. If you don’t have consumers depending on this shape yet, something like invalid_fields (or a more general fields) would better reflect all Zod issues.

If you later need stricter market validation, you can easily extend the schema with a regex for 2‑letter country codes without changing the rest of this flow.

Also applies to: 18-37

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d25bc6f and d2c177f.

📒 Files selected for processing (4)

• app/api/spotify/album/route.ts (1 hunks)
• lib/spotify/getAlbum.ts (1 hunks)
• lib/spotify/getSpotifyAlbumHandler.ts (1 hunks)
• lib/spotify/validateSpotifyAlbumQuery.ts (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (1)

lib/spotify/validateSpotifyAlbumQuery.ts (1)

lib/networking/getCorsHeaders.ts (1)

• getCorsHeaders (6-12)

🔇 Additional comments (1)

lib/spotify/getSpotifyAlbumHandler.ts (1)

17-38: Control flow and error mapping look solid

The handler’s flow (validate → get token → call Spotify → map to 500/502/200 with CORS) is clear and defensive, and returning the validator’s NextResponse early keeps concerns nicely separated. Nothing blocking here from a correctness standpoint.

Also applies to: 40-55, 67-78