Home
Events
Groups
Members

01 Watercooler
02 Bugs
02 Starting with Clay
Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
Gtm Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Powered by Tightknit

Bug Report: Issue with Saving Custom Rate Limit in HTTP API | Clay

Bug Report: Issue with Saving Custom Rate Limit in HTTP API

·

·

Noticed a bug in HTTP API — when I set 'Custom rate limit' here, and click Save — it's not saved. As a result, I often get API errors, and have to re-launch action multiple times

Loading attachments

2 comments

· Sorted by Oldest

Channeled
APP
·
·
The rate limit setting in HTTP API is an optional configuration that helps control API request frequency. When setting it up, you need to specify two components: 1. Request Limit: The maximum number of allowed requests 2. Duration (in ms): The time window in millisecondsIf you're experiencing saving issues, make sure both fields are properly filled out. The duration must be specified in milliseconds (e.g., 1000 ms = 1 second).This rate limiting helps prevent exceeding API provider limits and reduces errors. If you continue experiencing API errors, you may need to adjust these values based on your API provider's specific rate limits.If the issue persists after ensuring both fields are correctly filled, please request human support to investigate the saving functionality. Sources: HTTP API integration overview | Clay University HTTP API with JWT authentication | Clay University
Channeled
APP
·
·
Hi Pavel P.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: