docs(docs): migrate POST /api/stripe/portal/create#182
docs(docs): migrate POST /api/stripe/portal/create#182arpitgupta1214 wants to merge 2 commits intomainfrom
Conversation
Documents the new POST /api/subscriptions/portal-sessions endpoint that pairs with the existing POST /api/subscriptions/sessions for chat's stripe-outbound migration (group 4).
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Review rate limit: 0/1 reviews remaining, refill in 23 minutes and 11 seconds.Comment |
Per CHAT_API_MIGRATION_FINDINGS REST cleanup section, update paths and nav group to align with the dedicated API: /api/subscriptions/sessions -> /api/stripe/checkout-sessions /api/subscriptions/portal-sessions -> /api/stripe/portal-sessions Subscriptions nav group -> Stripe
There was a problem hiding this comment.
1 issue found across 6 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="api-reference/stripe/portal-sessions-create.mdx">
<violation number="1" location="api-reference/stripe/portal-sessions-create.mdx:3">
P2: The OpenAPI route in frontmatter targets `/api/stripe/portal-sessions`, but this migration is for `/api/subscriptions/portal-sessions`. Update the route so this page documents the correct endpoint.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| @@ -0,0 +1,4 @@ | |||
| --- | |||
| title: 'Create Billing Portal Session' | |||
| openapi: '/api-reference/openapi/accounts.json POST /api/stripe/portal-sessions' | |||
There was a problem hiding this comment.
P2: The OpenAPI route in frontmatter targets /api/stripe/portal-sessions, but this migration is for /api/subscriptions/portal-sessions. Update the route so this page documents the correct endpoint.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At api-reference/stripe/portal-sessions-create.mdx, line 3:
<comment>The OpenAPI route in frontmatter targets `/api/stripe/portal-sessions`, but this migration is for `/api/subscriptions/portal-sessions`. Update the route so this page documents the correct endpoint.</comment>
<file context>
@@ -0,0 +1,4 @@
+---
+title: 'Create Billing Portal Session'
+openapi: '/api-reference/openapi/accounts.json POST /api/stripe/portal-sessions'
+---
</file context>
Documents the new `POST /api/subscriptions/portal-sessions` endpoint that pairs with the existing `POST /api/subscriptions/sessions` to complete chat's stripe-outbound migration (group 4 of the chat→api migration plan).
Test plan