Adding components to rate limit

[dannyroosevelt]

WHY

Summary by CodeRabbit

• Documentation
  • Updated API documentation to correct the endpoint from POST /tokens to POST /token.
  • Added rate limit information for the /components endpoint, specifying a limit of 300 requests per minute per project, covering all related endpoints.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		May 13, 2025 9:02pm
pipedream-docs	⬜️ Ignored (Inspect)			May 13, 2025 9:02pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			May 13, 2025 9:02pm

[coderabbitai]

Walkthrough

The documentation for Pipedream Connect's API was updated to correct the endpoint from POST /tokens to POST /token and to introduce a new rate limit entry for the /components endpoint, specifying a collective limit of 300 requests per minute per project.

Changes

File(s)	Change Summary
docs-v2/pages/connect/api.mdx	Corrected endpoint from POST /tokens to POST /token and added a new rate limit for /components endpoints.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant API Documentation

    User->>API Documentation: Reads rate limits for endpoints
    API Documentation-->>User: Shows corrected endpoint and new /components rate limit

Loading

Possibly related PRs

• adding info on developer rate limits for Connect #15399: Updates rate limits documentation for the Pipedream Connect API, introducing broader sections on Pipedream and developer rate limits, related due to enhancements in the same documentation area.

Poem

In the docs a change was spun,
From tokens to token, the fix is done.
Components now have a limit to see,
Three hundred per minute—clear as can be!
With every endpoint neat and bright,
The docs now shine with info right.
🐇✨

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs-v2/pages/connect/api.mdx (1)

151-151: New /components rate limit entry looks good
The addition of a 300 rpm limit per project for all /components/* endpoints (including /components, /actions, and /triggers) provides necessary clarity. Consider adding the HTTP method (e.g., GET) for consistency with other table entries or a brief note on which operations the limit applies to if they vary.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d82722 and 0902477.

📒 Files selected for processing (1)

• docs-v2/pages/connect/api.mdx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: validate-links
• GitHub Check: Lint Code Base

🔇 Additional comments (1)

docs-v2/pages/connect/api.mdx (1)

149-149: Endpoint correction approved
The change from POST /tokens to POST /token accurately reflects the actual API and aligns with upstream usage.