|
2371
|
PostmanEditVIewWindowmelpHubSpot rate limit imple PostmanEditVIewWindowmelpHubSpot rate limit implementation strategyX-HubSpot-RateLimit-Secondly-RemainingDeprecated, ignoreSO Max=190, Interval=10000 means this portal is on a Pro/ Enterprise privately-distributedaoo aliyuius. I vousee max=110 .rs a oubnc VAutn nstal. max=250 means they nave uneAPI Limit Increase add-on.What vou cannot get via API• Search 5/sec limit - not exposed anywhere. Not in headers (search responses stripthem), not in any endpoint. It's a documented constant: vou assume it.• Daily usage broken out by app within a portal — the daily endpoint aggregates all privateapps. You can't tell from the API which app spent the budget.• Per-app burst limit programmatically — only inferred from Max in headers from a callthat app madePostman recide to fullv profile a vortallIhree calls in order.1. GET /account-info/v3/details →grab portalid. timeZone also notethe x-HunSnot-Rate imit-x resnonse neaders (this is vour burst nronle)2. GET /account-info/v3/api-usage/daily/private-apps → daily limit, current spend.reset time3. (Optional) Trigger a 429 deliberately on a sandbox to confirm policyName shape, but thisisn't necessary just for inspection.That gives vou evervthing HubSpot will tell vou about a specific portal's limits. Save the tworequests as a Postman collection with (faccess token}} and ((portal idi} ascollectionvariables and vou can profile anv portal in two clicks.Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..running and testing as it goesWrite a message…Opus 4.7 Adaptive v100% CThu 7 May 14:13:21Q SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaborationHITP https://api.hubapi.com/account-info/v3/api-usage/daily/private-appshttps://api.hubapi.com/account-info/v3/api-usage/daily/private-apps= DocsParamsGET Retrieve private app daily API usage • https://api.hubapi.com/account-info/2025-09/api-usage/daily/private-apps • HubSpot cAuth TypeBearer TokenGET Retrieve private apo daily APl usage • <baseUrl')/account-info/2026-03/api-usage/dailv/private-apos • HubSoot cGET Retrieve private app daily API usage • ((baseUrl)}/account-info/2025-09/api-usage/daily/private-apps • HubSpot elaloumdalaldtlalaGET Retrieve private app daily API usage • https://api.hubapi.com/account-info/2025-09/api-usage/daily/private-apps • HubSpot egenerated when ymore about Bearer Token authorization.$0# Support Daily - in 47 mGET httos://:No environmentvg Save4*AIVariables in requestG tokenCookies>All variablesv COLLECtIONscontacts› CRM ObjectseRM owners> CRM PipelinesDealsEngagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiePOST search tasksGET read call> Post search callsGET list callsPOST meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio> HubsnotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscrintionGET Journal earliestGET lournal latestGET httos:ubspot-webhooks-lournal-nal.s.GET neyt offcotpost get loken prodDEL DELSTE CURSCRIPTION PER PORTAI.GET DEAL WITH HISTORY pRODEptIcC vA©Authi> Properties> RESSARCHwCCADAUPOST search contact bv ohonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCSELOWS$ Connect Git @ Console TermCNeR-JHaMxlZoiNd.BodyJSONvPreviewp. Visualize v"portalld": 4392066"additionalCurrencies": (200 OK • 591 ms • 1.23 KB •(| .•FQl08Globals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2371
|
|
2370
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ahol§ Support Daily - in 47 m100% C 8DEV (docker)83Thu 7 May 14:13:21T81₴6DOCKERLast login: Thu MayDEV (docker)H82APP (-zsh)-zsh• 84screenpipe*•$5-zsh7 09:44:56 on ttys006Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2370
|
|
2369
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ahol§ Support Daily - in 47 m100% [DEV (docker)83Thu 7 May 14:13:18T81₴6DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)-zsh• 84screenpipe*•$5-zshPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2369
|
|
2368
|
PostmanEditVIewWindowmelpHubSpot rate limit imple PostmanEditVIewWindowmelpHubSpot rate limit implementation strategyX-HubSpot-RateLimit-Secondly-RemainingDeprecated, ignoreSO Max=190, Interval=10000 means this portal is on a Pro/ Enterprise privately-distributedaoo aliyuius. I vousee max=110 .rs a oubnc VAutn nstal. max=250 means they nave uneAPI Limit Increase add-on.What vou cannot get via API• Search 5/sec limit - not exposed anywhere. Not in headers (search responses stripthem), not in any endpoint. It's a documented constant; vou assume it.• Daily usage broken out by app within a portal — the daily endpoint aggregates all privateapps. You can't tell from the API which app spent the budget.• Per-app burst limit programmatically — only inferred from Max in headers from a callthat app madePostman recide to fullv profile a vortallIhree calls in order.1. GET /account-info/v3/details →grab portalld. timeZone also notethe x-HunSnot-Rate imit-x resnonse neaders (this is vour burst nronle)2. GET /account-info/v3/api-usage/daily/private-apps → daily limit, current spend.reset time3. (Optional) Trigger a 429 deliberately on a sandbox to confirm policyName shape, but thisisn't necessary just for inspection.That gives vou evervthing HubSpot will tell vou about a specific portal's limits. Save the tworequests as a Postman collection with (faccess token}} and ((portal idi} ascollectionvariables and vou can profile anv portal in two clicks.Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..running and testing as it goesWrite a message…Opus 4.7 Adaptive vhellQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.https://lapi.hubapi.com/account-info/v3/api-usaqe/daily/private-apps= DocsParamsAuthorization • Headers 9 Body ScriptsSettinasAuth TypeTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorizationGET httos://:{tokenl}"supoont Dally • In 47m100% L2Thu 7 May 14:13:18No environmentvg Save4* AIVariables in request> All variablesv COLLECtIONscontacts› CRM ObjectseRM owners> CRM Pipelines> DealsEngagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiePOST search tasksGET read call> Post search callsGET list callsPOST meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio> HubsnotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscrintionGET Journal earliestGET Journal latestGeT https:ubspot-webhooks-lournal-nal.s.GET neyt offcotpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY pRODEpTICC VA©Authi> Properties> RESSARCHwCCADAUPOST search contact bv ohonePOSt search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCSELOWSConnect Git E Console 2 TermirCNeR-JHaMxlZoiNd.CookiesBOdVJSONvPreview? Visualize"portalld": 4392066"additionalCurrencies": (200 OK • 591 ms • 1.23 KB •(| .•CQ108Globals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2368
|
|
2367
|
PostmanEditVIewWindowmelpHubSpot rate limit imple PostmanEditVIewWindowmelpHubSpot rate limit implementation strategyX-HubSpot-RateLimit-Secondly-RemainingDeprecated, ignoreSO Max=190, Interval=10000 means this portal is on a Pro/ Enterprise privately-distributedaoo aliyuius. I vousee max=110 .rs a oubnc VAutn nstal. max=250 means they nave uneAPI Limit Increase add-on.What vou cannot get via API• Search 5/sec limit - not exposed anywhere. Not in headers (search responses stripthem), not in any endpoint. It's a documented constant; vou assume it.• Daily usage broken out by app within a portal — the daily endpoint aggregates all privateapps. You can't tell from the API which app spent the budget.• Per-app burst limit programmatically — only inferred from Max in headers from a callthat app madePostman recide to fullv profile a vortallIhree calls in order.1. GET /account-info/v3/details →grab portalld. timeZone also notethe x-HunSnot-Rate imit-x resnonse neaders (this is vour burst nronle)2. GET /account-info/v3/api-usage/daily/private-apps → daily limit, current spend.reset time3. (Optional) Trigger a 429 deliberately on a sandbox to confirm policyName shape, but thisisn't necessary just for inspection.That gives vou evervthing HubSpot will tell vou about a specific portal's limits. Save the tworequests as a Postman collection with (faccess token}} and ((portal idi} ascollectionvariables and vou can profile anv portal in two clicks.Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..running and testing as it goesWrite a message…Opus 4.7 Adaptive v40Q SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.https://lapi.hubapi.com/account-info/v3/api-usaqe/daily/private-apps= DocsParamsAuthorization • Headers 9 Body ScriptsSettinasAuth TypeTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorizationGET httos://:{tokenl}# Support Daily - in 47 m100% L2Thu 7 May 14:13:17No environmentg Save4* AIVariables in requestG token> All variablesv COLLECtIONscontacts› CRM ObjectseRM owners> CRM PipelinesDealsEngagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiePOST search tasksGET read call> Post search callsGET list callsPOST meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio> HubsnotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscrintionGET Journal earliestGET Journal latestGeT https:ubspot-webhooks-lournal-nal.s.GET neyt offcotpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY pRODEpTICC VA©Authi> Properties> RESSARCHwCCADAUPOST search contact bv ohonePOSt search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCSELOWSConnect Git E Console 2 TermirCNeR-JHaMxlZoiNd.CookiesBodyJSONvPreview? Visualize"portalld": 4392066"additionalCurrencies": (200 OK • 591 ms • 1.23 KB •(| .•CQ108Globals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2367
|
|
2366
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ahol§ Support Daily - in 47 m100% [DEV (docker)83Thu 7 May 14:13:15T81₴6DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)-zsh• 84screenpipe*•$5-zshPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2366
|
|
2365
|
ClaudeFileEditVIewWindowmelt= HubSpot rate limit i ClaudeFileEditVIewWindowmelt= HubSpot rate limit implementation strategy vX-HubSpot-RateLimit-Secondly-RemainingDeprecated, ignoreSO Max=190, Interval=10000 means this portal is on a Pro/ Enterprise privately-distributedaoo aliyuius. I vousee max=110 .s a pubnc VAutn instal. max=250 means they nave theAPI Limit Increase add-on.What vou cannot get via API• Search 5/sec limit - not exposed anywhere. Not in headers (search responses stripthem), not in any endpoint. It's a documented constant: vou assume it.• Daily usage broken out by app within a portal — the daily endpoint aggregates all privateapps. You can't tell from the API which app spent the budget.• Per-app burst limit programmatically — only inferred from Max in headers from a callthat app madePostman recide to fullv profile a vortallIhree calis in order.1. GET /account-info/v3/details →grab portalid. timeZone also notethe x-HunSnot-Rate imit-x resnonse neaders (this is vour burst nronle)2. GET /account-info/v3/api-usage/daily/private-apps → daily limit, current spend.reset time3. (Optional) Trigger a 429 deliberately on a sandbox to confirm policyName shape, but thisisn't necessary just for inspection.That gives vou evervthing HubSpot will tell vou about a specific portal's limits. Save the tworequests as a Postman collection with (faccess token}} and (portal idi} ascollectionvariables and vou can profile anv portal in two clicks.Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..running and testing as it goesWrite a message…Opus 4.7 Adaptive v"supoont Dally • In 47m100% L2Thu 7 May 14:13:15Q Searchn. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.GET next off. •HTTP https:pi.hubapi.com/account-info/v3/detailsnttps://api.nubapi.com/account-info/vs/details= Docs Params Authorization • Headers 9 Body Scripts SettingsAuth TypeRearer TokenTokenine autnorization neader will oe automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorization{tokenl}hellGET httos://:No environmentv~ SaveCookies4* AIVariables in requestG token> All variablesCNeR-JHaMxlZoiNO.Body Cookies 1 Headers 20 lest ResultsJSONvPreviewe. Visualize v"portalld": 4392066"timeZone". "US/Eastern" .200 OK • 591 ms • 1.23 KB •(| .•CQ108Globals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2365
|
|
2364
|
Skip to content
Skip to content
Click to collapse
Skip to content
Skip to content
Click to collapse
⌘B
Drag to resize
Open sidebar
Chat
Cowork
Code
New chat ⌘N
New chat
⌘N
Projects
Artifacts
Customize
Pinned
Bulgarian citizenship application process for EU residents
More options for Bulgarian citizenship application process for EU residents
Dawarich location tracking project
More options for Dawarich location tracking project
Recents
View all
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Screenpipe retention policy code location
More options for Screenpipe retention policy code location
Viewing retention policy in screenpipe
More options for Viewing retention policy in screenpipe
Clean shot x video recording termination issue
More options for Clean shot x video recording termination issue
HubSpot rate limit handling with executeRequest
More options for HubSpot rate limit handling with executeRequest
Untitled
More options
💬 Screen pipe. Is there ability…
More options for 💬 Screen pipe. Is there ability…
SMB mount access inconsistency between Finder and iTerm
More options for SMB mount access inconsistency between Finder and iTerm
💬 What is the best switch I can…
More options for 💬 What is the best switch I can…
Permission denied on screenpipe volume
More options for Permission denied on screenpipe volume
Screenpipe sync database attachment error
More options for Screenpipe sync database attachment error
Last swimming outing with Dani
More options for Last swimming outing with Dani
Definition of incarcerated
More options for Definition of incarcerated
Chromecast remote volume buttons not working
More options for Chromecast remote volume buttons not working
Salesforce API errors with Organization and FieldDefinition queries
More options for Salesforce API errors with Organization and FieldDefinition queries
Daily activity summary from screenpipe data
More options for Daily activity summary from screenpipe data
MacBook unexpected restarts and kanji screen
More options for MacBook unexpected restarts and kanji screen
Security patch review and testing guidance
More options for Security patch review and testing guidance
Food calorie values reference
More options for Food calorie values reference
Tracking location history from last week
More options for Tracking location history from last week
Lukas Pro
Get apps and extensions
HubSpot rate limit implementation strategy, rename chat
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Share chat
Claude finished the response
You said: So just a solution for rate limit implementation.
You said: So just a solution for rate limit implementation.
So just a solution for rate limit implementation. The situation currently is that there are some daily and secondary limits for HubSpot. I would like to make sure I never reach a 429 error rate limit. The requests can come from any flow. It can be:
updating activity (engagement, meeting, call, note)
searching for a company or contact
updating deal
patching IDs
Review what the limit is at the moment in the HubSpot documentation and then think of the solution:
where to store it
how to read it
how to work with multiple jobs
how to work with paginated requests Let's consider a situation when there are 600 opportunities to sync. What would be the flow? How would the rate limit be recognized? How would it be handled? What are the potential issues? [API usage guidelines and limits - HubSpot docs](
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
). Example of such a error Client error:
POST https://api.hubapi.com/crm/v3/objects/contact/search
resulted in a
429 Too Many Requests
response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT","correlationId":"019dffc4-4 (truncated...). Think carefully about the implementation and potential issue and bottlenecks.
Show more
10:42
Retry
Edit
Copy
Claude responded: Current HubSpot limits (Apr 2026)
Claude responded: Current HubSpot limits (Apr 2026)
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Current HubSpot limits (Apr 2026)
Current HubSpot limits (Apr 2026)
For privately distributed apps (which is what Jiminny presumably uses with HubSpot), the limits are layered: a per-app burst window of 100/10s on Free/Starter, 190/10s on Pro/Enterprise, or 250/10s with the API Limit Increase add-on
, plus a per-account daily cap of 250k / 625k / 1M depending on tier — shared across all private apps in the account
. The burst window is per app; the daily quota is per portal.
hubspot
hubspot
hubspot
hubspot
The Search API is special: five requests per second per account, capped at 200 records per page, with a hard 10,000-result ceiling per query
. That's the limit the 429 in your example is hitting (
secondly limit
on
/crm/v3/objects/contact/search
). It's a separate bucket from the 190/10s, and critically, search responses do not include the
X-HubSpot-RateLimit-*
headers
— you can't read remaining capacity off the response, you have to track it yourself.
hubspot
hubspot
hubspot
hubspot
Non-search endpoints return
X-HubSpot-RateLimit-Remaining
,
-Max
, and
-Interval-Milliseconds
. The daily headers are not returned for OAuth-authenticated calls
, so for those you check the account-info endpoint or maintain your own counter. There's also a soft rule: errors should stay under 5% of total daily requests
— that's enforced for marketplace listing, but it's also a sane operational target.
hubspot
hubspot
hubspot
hubspot
So you have
four buckets
to track at minimum: app-burst (10s sliding), search-secondly (1s sliding), account-daily (24h fixed, midnight in HubSpot's TZ), and per-app daily share (your own budgeting on top of the account cap).
Where to store it
Where to store it
Redis. It's the only realistic option once you have multiple queue workers — DB-backed counters serialize too much, and in-process state can't coordinate across workers. Laravel already speaks Redis natively, and you get atomic
INCR
/
EXPIRE
plus Lua scripting for true CAS semantics.
Key layout I'd use:
Copy to clipboard
hubspot:rl:burst:{portalId}:{appId} ZSET (sliding 10s)
hubspot:rl:search:{portalId} ZSET (sliding 1s)
hubspot:rl:daily:{portalId} STRING + TTL to midnight TZ
hubspot:rl:meta:{portalId} HASH (last seen headers)
The two short-window buckets are sliding-window-log (Redis ZSET, score =
microtime
, member = unique request id). Lua script removes entries older than the window, counts remaining slots, and only adds the new one if there's room — all atomic. Fixed windows are simpler but allow 2× the limit at the boundary, which on a 5/s window is brutal.
The daily bucket is a plain
INCR
with TTL set to seconds-until-midnight in
HubSpot's account timezone
, not yours — Sofia is UTC+2/+3 but your portal might be set to US Eastern. Get this once and cache it.
How to read it
How to read it
Two-phase: optimistic pre-check, authoritative post-update.
Before a call, run the Lua acquire script. If it returns "denied," sleep until a slot frees up (the script can return ms-until-next-slot) or push the job back to the queue with a delay. Don't busy-loop.
After the call, parse
X-HubSpot-RateLimit-Remaining
/
-Max
/
-Interval-Milliseconds
and store them in
hubspot:rl:meta:{portalId}
. This is your reality check — if your local counter says 50 remaining but HubSpot's header says 5, you trust HubSpot and clamp your counter. This handles clock drift, missed accounting (e.g., crashed worker that took a token but never made the request), and other apps in the same account consuming the daily budget invisibly.
For search specifically, since headers don't come back, the local counter
is
the source of truth — meaning if you ever crash mid-flight, you've under-counted. Always release tokens on connection-level failure but
not
on 429 (you really did make that request).
How to work with multiple jobs
How to work with multiple jobs
The queue layer needs to enforce concurrency separately from the rate limiter. Both work together:
Concurrency cap
via
Queue::throttle()
or a Redis semaphore — limits how many sync workers run in parallel against HubSpot. Without this, you can have 50 workers all blocked waiting for tokens, which is wasteful and creates retry storms.
Per-tenant fairness
— if you sync many Jiminny customers into different HubSpot portals, each portal has its own bucket but you still want one slow portal not to starve others. Either separate queues per portal or a fair-share scheduler.
Priority lanes
— webhook-driven updates (user-visible latency) should outrank background batch syncs. Two queues:
hubspot-priority
and
hubspot-bulk
, with priority workers taking 70% of the burst budget and bulk taking 30% (enforce via separate sub-buckets if you really want hard separation, otherwise just pull from priority first).
Backoff on 429
— respect the
Retry-After
header. If absent, exponential with jitter (e.g.,
min(2^attempt * 250ms, 30s) ± 20%
). The jitter is non-negotiable; without it, simultaneous 429s retry in lockstep and you get thundering-herd 429s on retry.
How to work with paginated requests
How to work with paginated requests
The trap is treating "fetch all" as one logical operation. Each page is its own API call and competes for tokens with everything else.
Two practical rules:
Don't hold the worker idle while paginating.
If page N takes 500ms and page N+1 needs to wait 800ms for a token, you've burned 800ms of worker time doing nothing. Instead, fetch page N, dispatch the
processing
of page N as a separate job, and queue a "fetch page N+1" job with a delay equal to the wait time. Each page becomes its own atomic unit.
Always batch where HubSpot offers it.
POST /crm/v3/objects/{type}/batch/{read|update|create}
accepts up to 100 IDs per call. For your "patching IDs" flow this is the difference between 600 calls and 6.
Walkthrough: 600 opportunities
Walkthrough: 600 opportunities
Naive flow (one PATCH per deal): 600 calls. At 190/10s that's ~32s of API time, well under daily. You'd hit burst easily without throttling. Plus likely 1-3 search calls upfront and N association calls.
Sane flow:
Identify deltas
— if you can avoid Search at all, do. Use
lastmodifieddate
filter on a single search if you must, paginate at limit=200. For 600 deals that's 3 search calls @ 5/s = ~600ms naturally throttled.
Batch read
current state —
POST /crm/v3/objects/deals/batch/read
with 100 IDs per call → 6 calls. Burst weight 6.
Compute diff
in your code (no API).
Batch update
—
POST /crm/v3/objects/deals/batch/update
with 100 per call → 6 calls.
Associations
—
POST /crm/v4/associations/{from}/{to}/batch/create
if needed → another few batch calls.
Total: ~15-20 API calls for 600 deals. Burst budget consumed: 20/190 over ~5s. Daily impact: trivial.
Recognition: pre-check denies if
<weight>
slots aren't free; on 429 the response surfaces
policyName
(DAILY/SECONDLY) — log it, push the job back with
Retry-After
delay, increment a metric so you can alarm on sustained 429 rate.
Pitfalls & bottlenecks worth pre-empting
Pitfalls & bottlenecks worth pre-empting
Daily quota is shared across the whole portal
, including any n8n flows, other private apps, marketing automation calling APIs, etc. Budget for ~70-80% of the documented limit, not 100%. Add an internal per-app daily cap so a runaway sync can't starve other apps.
Search is uniquely fragile
: separate 5/s bucket, no headers to read, 10k-result cap per query. If you ever hit 10k+ deals matching a filter, partition by
hs_object_id
ranges or by
lastmodifieddate
windows.
Retry storms after HubSpot incidents
— always jitter, always cap total retries (e.g., 5 attempts, then dead-letter).
Webhook → sync → webhook loops
— when your update fires a HubSpot webhook that triggers another sync. Tag your own writes (e.g., a custom property
jy_last_sync_id
) and ignore webhooks where it just changed.
Token refresh
— OAuth refresh itself counts against burst. Cache the access token in Redis with TTL =
expires_in - 60s
, single-flight the refresh (only one worker refreshes; others wait on a lock).
Search latency for fresh writes
— newly created/updated objects don't appear in search instantly. Don't write-then-search; use returned IDs directly.
Clock skew
— Redis is authoritative. Don't use
time()
from each worker for window scoring; use
redis.call('TIME')
inside the Lua script.
Dead workers with held tokens
— sliding-window-log handles this naturally because tokens expire by score; token-bucket implementations need explicit release-on-crash logic.
The 5% error rule
counts every 429 toward your error budget, even successfully retried ones. If your pre-check is working well, 429s should be near zero — if they're not, your pre-check is wrong, not just slow.
Phantom contention with Laravel
RateLimited
middleware
: it's per-job-class by default, not per-portal. If your
SyncDealJob
and
UpdateActivityJob
are different classes both calling HubSpot, they don't share a Laravel-level limiter — you need a single
HubspotRateLimiter
service that everything routes through.
If you want, I can sketch the Lua script for the sliding-window acquire and the Laravel service wrapper around it.
Copy
Give positive feedback
Give negative feedback
Retry
You said: What will happen if there are two different types of rate limits?
You said: What will happen if there are two different types of rate limits?
What will happen if there are two different types of rate limits?
Search requests that have 5 requests per second
The other rate limit that has, let's say, 100 requests per 10 seconds How do these work together? Is there some conflict? Can I reach the limit with one request and block either as well, or are these separated? Can I still continue making search requests once I hit the normal requests limits?
13:40
Retry
Edit
Copy
Claude responded: They're independent buckets — with one shared bucket on top.
Claude responded: They're independent buckets — with one shared bucket on top.
Analyzed independent rate limit buckets and their practical interactions
Analyzed independent rate limit buckets and their practical interactions
They're independent buckets — with one shared bucket on top.
The three buckets and what each call hits
The three buckets and what each call hits
Copy to clipboard
┌──────────────────┐
Search request ──→ │ Search: 5/sec │ ──┐
└──────────────────┘ │
├──→ ┌─────────────────┐
┌──────────────────┐ │ │ Daily: 250k–1M │
Non-search call ──→ │ Burst: 190/10s │ ──┘ │ (per portal) │
└──────────────────┘ └─────────────────┘
A search call is only metered against the search bucket and the daily bucket. A non-search call (batch read/update, single PATCH, associations, etc.) is only metered against the burst bucket and the daily bucket. The two short-window buckets do not share counters.
What this means practically
What this means practically
Hitting search secondly limit (5/s):
Only further
/search
calls 429. Your batch reads, batch updates, single PATCHes, association calls — all keep working at full burst speed. This is actually useful: if your sync is bottlenecked on Search, you can pivot to using
lastmodifieddate
filters via batch endpoints, or use the IDs you already have to do batch reads, while Search cools off.
Hitting burst limit (190/10s):
Only non-search calls 429. You can still issue Search calls at 5/s. Useful for: continuing to identify deltas for queueing while in-flight updates drain, or refreshing a small set of records via Search even though your write pipeline is paused.
Hitting daily limit:
Everything stops. Search and non-search alike. Doesn't unblock until midnight in your portal's configured timezone — and remember this is shared across every private app in the portal, plus n8n flows, marketing tools, anything else hitting the API with that account.
So can one type of request block the other?
So can one type of request block the other?
Search → Burst:
No.
Saturating Search at 50 calls per 10s leaves your full 190/10s burst untouched.
Burst → Search:
No.
Saturating burst leaves Search's 5/s untouched.
Either → Daily:
Yes
, but only by contributing to the same daily counter. It's volume that kills you here, not the type.
In theory you can sustain ~50 search + ~190 other =
~240 calls per 10 seconds
indefinitely (until daily runs out), because the two buckets bill independently.
Implementation consequence
Implementation consequence
Your rate limiter needs to know which bucket a request hits before it acquires. Cleanest pattern:
Copy to clipboard
php
$limiter
->
acquire
(
'search'
,
$weight
=
1
)
;
// for search endpoints only
$limiter
->
acquire
(
'burst'
,
$weight
=
1
)
;
// for everything else
$limiter
->
acquire
(
'daily'
,
$weight
=
1
)
;
// every call, both kinds
In Redis: three separate keys, three separate Lua acquire scripts (or one script with a bucket parameter). A search call calls
acquire('search')
+
acquire('daily')
. A batch update calls
acquire('burst')
+
acquire('daily')
.
One subtle pitfall: when you backoff on a 429,
inspect
policyName
in the response body
to know which bucket actually fired. If you see
SECONDLY
from a search endpoint, you only need to delay search-bound jobs — burst-bound jobs in the queue can keep running. If you blanket-pause everything on any 429, you waste capacity on the bucket that's still healthy. Two queues (or two throttle keys) make this clean; one global pause is the lazy version.
The other subtlety: the burst response gives you
X-HubSpot-RateLimit-Remaining
to clamp local state against, but search doesn't return those headers. So your search counter is unverified — be slightly more conservative there (e.g., budget 4/s instead of 5) to absorb the unaccounted-for calls.
Copy
Give positive feedback
Give negative feedback
Retry
You said: Ok, so what will happen each time I make a request?
You said: Ok, so what will happen each time I make a request?
Ok, so what will happen each time I make a request? Let's say I have 100,000 requests to make that are instant. Do I need to increment each request based on the type? For example, if there is a search request, I need to increment both the search bucket and also the daily bucket. If it's a burst, then I can go to the daily and burst buckets. If I need to check if it can make a call, do I need to see both the daily and search, or burst, respectively? Isn't that too heavy for the infrastructure, adding additional load to each request?
13:44
Retry
Edit
Copy
Claude responded: Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out.
Claude responded: Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out.
Analyzed per-request overhead concerns and quantified Redis performance impact
Analyzed per-request overhead concerns and quantified Redis performance impact
Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out. But the overhead is much smaller than it sounds, and importantly, it's nowhere near your bottleneck.
What "two buckets per request" actually costs
What "two buckets per request" actually costs...
|
Claude
|
Claude
|
NULL
|
2364
|
|
2363
|
Skip to content
Skip to content
Click to collapse
Skip to content
Skip to content
Click to collapse
⌘B
Drag to resize
Open sidebar
Chat
Cowork
Code
New chat ⌘N
New chat
⌘N
Projects
Artifacts
Customize
Pinned
Bulgarian citizenship application process for EU residents
More options for Bulgarian citizenship application process for EU residents
Dawarich location tracking project
More options for Dawarich location tracking project
Recents
View all
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Screenpipe retention policy code location
More options for Screenpipe retention policy code location
Viewing retention policy in screenpipe
More options for Viewing retention policy in screenpipe
Clean shot x video recording termination issue
More options for Clean shot x video recording termination issue
HubSpot rate limit handling with executeRequest
More options for HubSpot rate limit handling with executeRequest
Untitled
More options
💬 Screen pipe. Is there ability…
More options for 💬 Screen pipe. Is there ability…
SMB mount access inconsistency between Finder and iTerm
More options for SMB mount access inconsistency between Finder and iTerm
💬 What is the best switch I can…
More options for 💬 What is the best switch I can…
Permission denied on screenpipe volume
More options for Permission denied on screenpipe volume
Screenpipe sync database attachment error
More options for Screenpipe sync database attachment error
Last swimming outing with Dani
More options for Last swimming outing with Dani
Definition of incarcerated
More options for Definition of incarcerated
Chromecast remote volume buttons not working
More options for Chromecast remote volume buttons not working
Salesforce API errors with Organization and FieldDefinition queries
More options for Salesforce API errors with Organization and FieldDefinition queries
Daily activity summary from screenpipe data
More options for Daily activity summary from screenpipe data
MacBook unexpected restarts and kanji screen
More options for MacBook unexpected restarts and kanji screen
Security patch review and testing guidance
More options for Security patch review and testing guidance
Food calorie values reference
More options for Food calorie values reference
Tracking location history from last week
More options for Tracking location history from last week
Lukas Pro
Get apps and extensions
HubSpot rate limit implementation strategy, rename chat
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Share chat
Claude finished the response
You said: So just a solution for rate limit implementation.
You said: So just a solution for rate limit implementation.
So just a solution for rate limit implementation. The situation currently is that there are some daily and secondary limits for HubSpot. I would like to make sure I never reach a 429 error rate limit. The requests can come from any flow. It can be:
updating activity (engagement, meeting, call, note)
searching for a company or contact
updating deal
patching IDs
Review what the limit is at the moment in the HubSpot documentation and then think of the solution:
where to store it
how to read it
how to work with multiple jobs
how to work with paginated requests Let's consider a situation when there are 600 opportunities to sync. What would be the flow? How would the rate limit be recognized? How would it be handled? What are the potential issues? [API usage guidelines and limits - HubSpot docs](
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
). Example of such a error Client error:
POST https://api.hubapi.com/crm/v3/objects/contact/search
resulted in a
429 Too Many Requests
response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT","correlationId":"019dffc4-4 (truncated...). Think carefully about the implementation and potential issue and bottlenecks.
Show more
10:42
Retry
Edit
Copy
Claude responded: Current HubSpot limits (Apr 2026)
Claude responded: Current HubSpot limits (Apr 2026)
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Current HubSpot limits (Apr 2026)
Current HubSpot limits (Apr 2026)
For privately distributed apps (which is what Jiminny presumably uses with HubSpot), the limits are layered: a per-app burst window of 100/10s on Free/Starter, 190/10s on Pro/Enterprise, or 250/10s with the API Limit Increase add-on
, plus a per-account daily cap of 250k / 625k / 1M depending on tier — shared across all private apps in the account
. The burst window is per app; the daily quota is per portal.
hubspot
hubspot
hubspot
hubspot
The Search API is special: five requests per second per account, capped at 200 records per page, with a hard 10,000-result ceiling per query
. That's the limit the 429 in your example is hitting (
secondly limit
on
/crm/v3/objects/contact/search
). It's a separate bucket from the 190/10s, and critically, search responses do not include the
X-HubSpot-RateLimit-*
headers
— you can't read remaining capacity off the response, you have to track it yourself.
hubspot
hubspot
hubspot
hubspot
Non-search endpoints return
X-HubSpot-RateLimit-Remaining
,
-Max
, and
-Interval-Milliseconds
. The daily headers are not returned for OAuth-authenticated calls
, so for those you check the account-info endpoint or maintain your own counter. There's also a soft rule: errors should stay under 5% of total daily requests
— that's enforced for marketplace listing, but it's also a sane operational target.
hubspot
hubspot
hubspot
hubspot
So you have
four buckets
to track at minimum: app-burst (10s sliding), search-secondly (1s sliding), account-daily (24h fixed, midnight in HubSpot's TZ), and per-app daily share (your own budgeting on top of the account cap).
Where to store it
Where to store it
Redis. It's the only realistic option once you have multiple queue workers — DB-backed counters serialize too much, and in-process state can't coordinate across workers. Laravel already speaks Redis natively, and you get atomic
INCR
/
EXPIRE
plus Lua scripting for true CAS semantics.
Key layout I'd use:
Copy to clipboard
hubspot:rl:burst:{portalId}:{appId} ZSET (sliding 10s)
hubspot:rl:search:{portalId} ZSET (sliding 1s)
hubspot:rl:daily:{portalId} STRING + TTL to midnight TZ
hubspot:rl:meta:{portalId} HASH (last seen headers)
The two short-window buckets are sliding-window-log (Redis ZSET, score =
microtime
, member = unique request id). Lua script removes entries older than the window, counts remaining slots, and only adds the new one if there's room — all atomic. Fixed windows are simpler but allow 2× the limit at the boundary, which on a 5/s window is brutal.
The daily bucket is a plain
INCR
with TTL set to seconds-until-midnight in
HubSpot's account timezone
, not yours — Sofia is UTC+2/+3 but your portal might be set to US Eastern. Get this once and cache it.
How to read it
How to read it
Two-phase: optimistic pre-check, authoritative post-update.
Before a call, run the Lua acquire script. If it returns "denied," sleep until a slot frees up (the script can return ms-until-next-slot) or push the job back to the queue with a delay. Don't busy-loop.
After the call, parse
X-HubSpot-RateLimit-Remaining
/
-Max
/
-Interval-Milliseconds
and store them in
hubspot:rl:meta:{portalId}
. This is your reality check — if your local counter says 50 remaining but HubSpot's header says 5, you trust HubSpot and clamp your counter. This handles clock drift, missed accounting (e.g., crashed worker that took a token but never made the request), and other apps in the same account consuming the daily budget invisibly.
For search specifically, since headers don't come back, the local counter
is
the source of truth — meaning if you ever crash mid-flight, you've under-counted. Always release tokens on connection-level failure but
not
on 429 (you really did make that request).
How to work with multiple jobs
How to work with multiple jobs
The queue layer needs to enforce concurrency separately from the rate limiter. Both work together:
Concurrency cap
via
Queue::throttle()
or a Redis semaphore — limits how many sync workers run in parallel against HubSpot. Without this, you can have 50 workers all blocked waiting for tokens, which is wasteful and creates retry storms.
Per-tenant fairness
— if you sync many Jiminny customers into different HubSpot portals, each portal has its own bucket but you still want one slow portal not to starve others. Either separate queues per portal or a fair-share scheduler.
Priority lanes
— webhook-driven updates (user-visible latency) should outrank background batch syncs. Two queues:
hubspot-priority
and
hubspot-bulk
, with priority workers taking 70% of the burst budget and bulk taking 30% (enforce via separate sub-buckets if you really want hard separation, otherwise just pull from priority first).
Backoff on 429
— respect the
Retry-After
header. If absent, exponential with jitter (e.g.,
min(2^attempt * 250ms, 30s) ± 20%
). The jitter is non-negotiable; without it, simultaneous 429s retry in lockstep and you get thundering-herd 429s on retry.
How to work with paginated requests
How to work with paginated requests
The trap is treating "fetch all" as one logical operation. Each page is its own API call and competes for tokens with everything else.
Two practical rules:
Don't hold the worker idle while paginating.
If page N takes 500ms and page N+1 needs to wait 800ms for a token, you've burned 800ms of worker time doing nothing. Instead, fetch page N, dispatch the
processing
of page N as a separate job, and queue a "fetch page N+1" job with a delay equal to the wait time. Each page becomes its own atomic unit.
Always batch where HubSpot offers it.
POST /crm/v3/objects/{type}/batch/{read|update|create}
accepts up to 100 IDs per call. For your "patching IDs" flow this is the difference between 600 calls and 6.
Walkthrough: 600 opportunities
Walkthrough: 600 opportunities
Naive flow (one PATCH per deal): 600 calls. At 190/10s that's ~32s of API time, well under daily. You'd hit burst easily without throttling. Plus likely 1-3 search calls upfront and N association calls.
Sane flow:
Identify deltas
— if you can avoid Search at all, do. Use
lastmodifieddate
filter on a single search if you must, paginate at limit=200. For 600 deals that's 3 search calls @ 5/s = ~600ms naturally throttled.
Batch read
current state —
POST /crm/v3/objects/deals/batch/read
with 100 IDs per call → 6 calls. Burst weight 6.
Compute diff
in your code (no API).
Batch update
—
POST /crm/v3/objects/deals/batch/update
with 100 per call → 6 calls.
Associations
—
POST /crm/v4/associations/{from}/{to}/batch/create
if needed → another few batch calls.
Total: ~15-20 API calls for 600 deals. Burst budget consumed: 20/190 over ~5s. Daily impact: trivial.
Recognition: pre-check denies if
<weight>
slots aren't free; on 429 the response surfaces
policyName
(DAILY/SECONDLY) — log it, push the job back with
Retry-After
delay, increment a metric so you can alarm on sustained 429 rate.
Pitfalls & bottlenecks worth pre-empting
Pitfalls & bottlenecks worth pre-empting
Daily quota is shared across the whole portal
, including any n8n flows, other private apps, marketing automation calling APIs, etc. Budget for ~70-80% of the documented limit, not 100%. Add an internal per-app daily cap so a runaway sync can't starve other apps.
Search is uniquely fragile
: separate 5/s bucket, no headers to read, 10k-result cap per query. If you ever hit 10k+ deals matching a filter, partition by
hs_object_id
ranges or by
lastmodifieddate
windows.
Retry storms after HubSpot incidents
— always jitter, always cap total retries (e.g., 5 attempts, then dead-letter).
Webhook → sync → webhook loops
— when your update fires a HubSpot webhook that triggers another sync. Tag your own writes (e.g., a custom property
jy_last_sync_id
) and ignore webhooks where it just changed.
Token refresh
— OAuth refresh itself counts against burst. Cache the access token in Redis with TTL =
expires_in - 60s
, single-flight the refresh (only one worker refreshes; others wait on a lock).
Search latency for fresh writes
— newly created/updated objects don't appear in search instantly. Don't write-then-search; use returned IDs directly.
Clock skew
— Redis is authoritative. Don't use
time()
from each worker for window scoring; use
redis.call('TIME')
inside the Lua script.
Dead workers with held tokens
— sliding-window-log handles this naturally because tokens expire by score; token-bucket implementations need explicit release-on-crash logic.
The 5% error rule
counts every 429 toward your error budget, even successfully retried ones. If your pre-check is working well, 429s should be near zero — if they're not, your pre-check is wrong, not just slow.
Phantom contention with Laravel
RateLimited
middleware
: it's per-job-class by default, not per-portal. If your
SyncDealJob
and
UpdateActivityJob
are different classes both calling HubSpot, they don't share a Laravel-level limiter — you need a single
HubspotRateLimiter
service that everything routes through.
If you want, I can sketch the Lua script for the sliding-window acquire and the Laravel service wrapper around it.
Copy
Give positive feedback
Give negative feedback
Retry
You said: What will happen if there are two different types of rate limits?
You said: What will happen if there are two different types of rate limits?
What will happen if there are two different types of rate limits?
Search requests that have 5 requests per second
The other rate limit that has, let's say, 100 requests per 10 seconds How do these work together? Is there some conflict? Can I reach the limit with one request and block either as well, or are these separated? Can I still continue making search requests once I hit the normal requests limits?
13:40
Retry
Edit
Copy
Claude responded: They're independent buckets — with one shared bucket on top.
Claude responded: They're independent buckets — with one shared bucket on top.
Analyzed independent rate limit buckets and their practical interactions
Analyzed independent rate limit buckets and their practical interactions
They're independent buckets — with one shared bucket on top.
The three buckets and what each call hits
The three buckets and what each call hits
Copy to clipboard
┌──────────────────┐
Search request ──→ │ Search: 5/sec │ ──┐
└──────────────────┘ │
├──→ ┌─────────────────┐
┌──────────────────┐ │ │ Daily: 250k–1M │
Non-search call ──→ │ Burst: 190/10s │ ──┘ │ (per portal) │
└──────────────────┘ └─────────────────┘
A search call is only metered against the search bucket and the daily bucket. A non-search call (batch read/update, single PATCH, associations, etc.) is only metered against the burst bucket and the daily bucket. The two short-window buckets do not share counters.
What this means practically
What this means practically
Hitting search secondly limit (5/s):
Only further
/search
calls 429. Your batch reads, batch updates, single PATCHes, association calls — all keep working at full burst speed. This is actually useful: if your sync is bottlenecked on Search, you can pivot to using
lastmodifieddate
filters via batch endpoints, or use the IDs you already have to do batch reads, while Search cools off.
Hitting burst limit (190/10s):
Only non-search calls 429. You can still issue Search calls at 5/s. Useful for: continuing to identify deltas for queueing while in-flight updates drain, or refreshing a small set of records via Search even though your write pipeline is paused.
Hitting daily limit:
Everything stops. Search and non-search alike. Doesn't unblock until midnight in your portal's configured timezone — and remember this is shared across every private app in the portal, plus n8n flows, marketing tools, anything else hitting the API with that account.
So can one type of request block the other?
So can one type of request block the other?
Search → Burst:
No.
Saturating Search at 50 calls per 10s leaves your full 190/10s burst untouched.
Burst → Search:
No.
Saturating burst leaves Search's 5/s untouched.
Either → Daily:
Yes
, but only by contributing to the same daily counter. It's volume that kills you here, not the type.
In theory you can sustain ~50 search + ~190 other =
~240 calls per 10 seconds
indefinitely (until daily runs out), because the two buckets bill independently.
Implementation consequence
Implementation consequence
Your rate limiter needs to know which bucket a request hits before it acquires. Cleanest pattern:
Copy to clipboard
php
$limiter
->
acquire
(
'search'
,
$weight
=
1
)
;
// for search endpoints only
$limiter
->
acquire
(
'burst'
,
$weight
=
1
)
;
// for everything else
$limiter
->
acquire
(
'daily'
,
$weight
=
1
)
;
// every call, both kinds
In Redis: three separate keys, three separate Lua acquire scripts (or one script with a bucket parameter). A search call calls
acquire('search')
+
acquire('daily')
. A batch update calls
acquire('burst')
+
acquire('daily')
.
One subtle pitfall: when you backoff on a 429,
inspect
policyName
in the response body
to know which bucket actually fired. If you see
SECONDLY
from a search endpoint, you only need to delay search-bound jobs — burst-bound jobs in the queue can keep running. If you blanket-pause everything on any 429, you waste capacity on the bucket that's still healthy. Two queues (or two throttle keys) make this clean; one global pause is the lazy version.
The other subtlety: the burst response gives you
X-HubSpot-RateLimit-Remaining
to clamp local state against, but search doesn't return those headers. So your search counter is unverified — be slightly more conservative there (e.g., budget 4/s instead of 5) to absorb the unaccounted-for calls....
|
Claude
|
Claude
|
NULL
|
2363
|
|
2362
|
Skip to content
Skip to content
Click to collapse
Skip to content
Skip to content
Click to collapse
⌘B
Drag to resize
Open sidebar
Chat
Cowork
Code
New chat ⌘N
New chat
⌘N
Projects
Artifacts
Customize
Pinned
Bulgarian citizenship application process for EU residents
More options for Bulgarian citizenship application process for EU residents
Dawarich location tracking project
More options for Dawarich location tracking project
Recents
View all
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Screenpipe retention policy code location
More options for Screenpipe retention policy code location
Viewing retention policy in screenpipe
More options for Viewing retention policy in screenpipe
Clean shot x video recording termination issue
More options for Clean shot x video recording termination issue
HubSpot rate limit handling with executeRequest
More options for HubSpot rate limit handling with executeRequest
Untitled
More options
💬 Screen pipe. Is there ability…
More options for 💬 Screen pipe. Is there ability…
SMB mount access inconsistency between Finder and iTerm
More options for SMB mount access inconsistency between Finder and iTerm
💬 What is the best switch I can…
More options for 💬 What is the best switch I can…
Permission denied on screenpipe volume
More options for Permission denied on screenpipe volume
Screenpipe sync database attachment error
More options for Screenpipe sync database attachment error
Last swimming outing with Dani
More options for Last swimming outing with Dani
Definition of incarcerated
More options for Definition of incarcerated
Chromecast remote volume buttons not working
More options for Chromecast remote volume buttons not working
Salesforce API errors with Organization and FieldDefinition queries
More options for Salesforce API errors with Organization and FieldDefinition queries
Daily activity summary from screenpipe data
More options for Daily activity summary from screenpipe data
MacBook unexpected restarts and kanji screen
More options for MacBook unexpected restarts and kanji screen
Security patch review and testing guidance
More options for Security patch review and testing guidance
Food calorie values reference
More options for Food calorie values reference
Tracking location history from last week
More options for Tracking location history from last week
Lukas Pro
Get apps and extensions
HubSpot rate limit implementation strategy, rename chat
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Share chat
Claude finished the response
You said: So just a solution for rate limit implementation.
You said: So just a solution for rate limit implementation.
So just a solution for rate limit implementation. The situation currently is that there are some daily and secondary limits for HubSpot. I would like to make sure I never reach a 429 error rate limit. The requests can come from any flow. It can be:
updating activity (engagement, meeting, call, note)
searching for a company or contact
updating deal
patching IDs
Review what the limit is at the moment in the HubSpot documentation and then think of the solution:
where to store it
how to read it
how to work with multiple jobs
how to work with paginated requests Let's consider a situation when there are 600 opportunities to sync. What would be the flow? How would the rate limit be recognized? How would it be handled? What are the potential issues? [API usage guidelines and limits - HubSpot docs](
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
). Example of such a error Client error:
POST https://api.hubapi.com/crm/v3/objects/contact/search
resulted in a
429 Too Many Requests
response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT","correlationId":"019dffc4-4 (truncated...). Think carefully about the implementation and potential issue and bottlenecks.
Show more
10:42
Retry
Edit
Copy
Claude responded: Current HubSpot limits (Apr 2026)
Claude responded: Current HubSpot limits (Apr 2026)
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Current HubSpot limits (Apr 2026)
Current HubSpot limits (Apr 2026)
For privately distributed apps (which is what Jiminny presumably uses with HubSpot), the limits are layered: a per-app burst window of 100/10s on Free/Starter, 190/10s on Pro/Enterprise, or 250/10s with the API Limit Increase add-on
, plus a per-account daily cap of 250k / 625k / 1M depending on tier — shared across all private apps in the account
. The burst window is per app; the daily quota is per portal.
hubspot
hubspot
hubspot
hubspot
The Search API is special: five requests per second per account, capped at 200 records per page, with a hard 10,000-result ceiling per query
. That's the limit the 429 in your example is hitting (
secondly limit
on
/crm/v3/objects/contact/search
). It's a separate bucket from the 190/10s, and critically, search responses do not include the
X-HubSpot-RateLimit-*
headers
— you can't read remaining capacity off the response, you have to track it yourself.
hubspot
hubspot
hubspot
hubspot
Non-search endpoints return
X-HubSpot-RateLimit-Remaining
,
-Max
, and
-Interval-Milliseconds
. The daily headers are not returned for OAuth-authenticated calls
, so for those you check the account-info endpoint or maintain your own counter. There's also a soft rule: errors should stay under 5% of total daily requests
— that's enforced for marketplace listing, but it's also a sane operational target.
hubspot
hubspot
hubspot
hubspot
So you have
four buckets
to track at minimum: app-burst (10s sliding), search-secondly (1s sliding), account-daily (24h fixed, midnight in HubSpot's TZ), and per-app daily share (your own budgeting on top of the account cap).
Where to store it
Where to store it
Redis. It's the only realistic option once you have multiple queue workers — DB-backed counters serialize too much, and in-process state can't coordinate across workers. Laravel already speaks Redis natively, and you get atomic
INCR
/
EXPIRE
plus Lua scripting for true CAS semantics.
Key layout I'd use:
Copy to clipboard
hubspot:rl:burst:{portalId}:{appId} ZSET (sliding 10s)
hubspot:rl:search:{portalId} ZSET (sliding 1s)
hubspot:rl:daily:{portalId} STRING + TTL to midnight TZ
hubspot:rl:meta:{portalId} HASH (last seen headers)
The two short-window buckets are sliding-window-log (Redis ZSET, score =
microtime
, member = unique request id). Lua script removes entries older than the window, counts remaining slots, and only adds the new one if there's room — all atomic. Fixed windows are simpler but allow 2× the limit at the boundary, which on a 5/s window is brutal.
The daily bucket is a plain
INCR
with TTL set to seconds-until-midnight in
HubSpot's account timezone
, not yours — Sofia is UTC+2/+3 but your portal might be set to US Eastern. Get this once and cache it.
How to read it
How to read it
Two-phase: optimistic pre-check, authoritative post-update.
Before a call, run the Lua acquire script. If it returns "denied," sleep until a slot frees up (the script can return ms-until-next-slot) or push the job back to the queue with a delay. Don't busy-loop.
After the call, parse
X-HubSpot-RateLimit-Remaining
/
-Max
/
-Interval-Milliseconds
and store them in
hubspot:rl:meta:{portalId}
. This is your reality check — if your local counter says 50 remaining but HubSpot's header says 5, you trust HubSpot and clamp your counter. This handles clock drift, missed accounting (e.g., crashed worker that took a token but never made the request), and other apps in the same account consuming the daily budget invisibly.
For search specifically, since headers don't come back, the local counter
is
the source of truth — meaning if you ever crash mid-flight, you've under-counted. Always release tokens on connection-level failure but
not
on 429 (you really did make that request).
How to work with multiple jobs
How to work with multiple jobs
The queue layer needs to enforce concurrency separately from the rate limiter. Both work together:
Concurrency cap
via
Queue::throttle()
or a Redis semaphore — limits how many sync workers run in parallel against HubSpot. Without this, you can have 50 workers all blocked waiting for tokens, which is wasteful and creates retry storms.
Per-tenant fairness
— if you sync many Jiminny customers into different HubSpot portals, each portal has its own bucket but you still want one slow portal not to starve others. Either separate queues per portal or a fair-share scheduler.
Priority lanes
— webhook-driven updates (user-visible latency) should outrank background batch syncs. Two queues:
hubspot-priority
and
hubspot-bulk
, with priority workers taking 70% of the burst budget and bulk taking 30% (enforce via separate sub-buckets if you really want hard separation, otherwise just pull from priority first).
Backoff on 429
— respect the
Retry-After
header. If absent, exponential with jitter (e.g.,
min(2^attempt * 250ms, 30s) ± 20%
). The jitter is non-negotiable; without it, simultaneous 429s retry in lockstep and you get thundering-herd 429s on retry.
How to work with paginated requests
How to work with paginated requests
The trap is treating "fetch all" as one logical operation. Each page is its own API call and competes for tokens with everything else.
Two practical rules:
Don't hold the worker idle while paginating.
If page N takes 500ms and page N+1 needs to wait 800ms for a token, you've burned 800ms of worker time doing nothing. Instead, fetch page N, dispatch the
processing
of page N as a separate job, and queue a "fetch page N+1" job with a delay equal to the wait time. Each page becomes its own atomic unit.
Always batch where HubSpot offers it.
POST /crm/v3/objects/{type}/batch/{read|update|create}
accepts up to 100 IDs per call. For your "patching IDs" flow this is the difference between 600 calls and 6.
Walkthrough: 600 opportunities
Walkthrough: 600 opportunities
Naive flow (one PATCH per deal): 600 calls. At 190/10s that's ~32s of API time, well under daily. You'd hit burst easily without throttling. Plus likely 1-3 search calls upfront and N association calls.
Sane flow:
Identify deltas
— if you can avoid Search at all, do. Use
lastmodifieddate
filter on a single search if you must, paginate at limit=200. For 600 deals that's 3 search calls @ 5/s = ~600ms naturally throttled.
Batch read
current state —
POST /crm/v3/objects/deals/batch/read
with 100 IDs per call → 6 calls. Burst weight 6.
Compute diff
in your code (no API).
Batch update
—
POST /crm/v3/objects/deals/batch/update
with 100 per call → 6 calls.
Associations
—
POST /crm/v4/associations/{from}/{to}/batch/create
if needed → another few batch calls.
Total: ~15-20 API calls for 600 deals. Burst budget consumed: 20/190 over ~5s. Daily impact: trivial.
Recognition: pre-check denies if
<weight>
slots aren't free; on 429 the response surfaces
policyName
(DAILY/SECONDLY) — log it, push the job back with
Retry-After
delay, increment a metric so you can alarm on sustained 429 rate.
Pitfalls & bottlenecks worth pre-empting
Pitfalls & bottlenecks worth pre-empting
Daily quota is shared across the whole portal
, including any n8n flows, other private apps, marketing automation calling APIs, etc. Budget for ~70-80% of the documented limit, not 100%. Add an internal per-app daily cap so a runaway sync can't starve other apps.
Search is uniquely fragile
: separate 5/s bucket, no headers to read, 10k-result cap per query. If you ever hit 10k+ deals matching a filter, partition by
hs_object_id
ranges or by
lastmodifieddate
windows.
Retry storms after HubSpot incidents
— always jitter, always cap total retries (e.g., 5 attempts, then dead-letter).
Webhook → sync → webhook loops
— when your update fires a HubSpot webhook that triggers another sync. Tag your own writes (e.g., a custom property
jy_last_sync_id
) and ignore webhooks where it just changed.
Token refresh
— OAuth refresh itself counts against burst. Cache the access token in Redis with TTL =
expires_in - 60s
, single-flight the refresh (only one worker refreshes; others wait on a lock).
Search latency for fresh writes
— newly created/updated objects don't appear in search instantly. Don't write-then-search; use returned IDs directly.
Clock skew
— Redis is authoritative. Don't use
time()
from each worker for window scoring; use
redis.call('TIME')
inside the Lua script.
Dead workers with held tokens
— sliding-window-log handles this naturally because tokens expire by score; token-bucket implementations need explicit release-on-crash logic.
The 5% error rule
counts every 429 toward your error budget, even successfully retried ones. If your pre-check is working well, 429s should be near zero — if they're not, your pre-check is wrong, not just slow.
Phantom contention with Laravel
RateLimited
middleware
: it's per-job-class by default, not per-portal. If your
SyncDealJob
and
UpdateActivityJob
are different classes both calling HubSpot, they don't share a Laravel-level limiter — you need a single
HubspotRateLimiter
service that everything routes through.
If you want, I can sketch the Lua script for the sliding-window acquire and the Laravel service wrapper around it.
Copy
Give positive feedback
Give negative feedback
Retry
You said: What will happen if there are two different types of rate limits?
You said: What will happen if there are two different types of rate limits?
What will happen if there are two different types of rate limits?
Search requests that have 5 requests per second
The other rate limit that has, let's say, 100 requests per 10 seconds How do these work together? Is there some conflict? Can I reach the limit with one request and block either as well, or are these separated? Can I still continue making search requests once I hit the normal requests limits?
13:40
Retry
Edit
Copy
Claude responded: They're independent buckets — with one shared bucket on top.
Claude responded: They're independent buckets — with one shared bucket on top.
Analyzed independent rate limit buckets and their practical interactions
Analyzed independent rate limit buckets and their practical interactions
They're independent buckets — with one shared bucket on top.
The three buckets and what each call hits
The three buckets and what each call hits
Copy to clipboard
┌──────────────────┐
Search request ──→ │ Search: 5/sec │ ──┐
└──────────────────┘ │
├──→ ┌─────────────────┐
┌──────────────────┐ │ │ Daily: 250k–1M │
Non-search call ──→ │ Burst: 190/10s │ ──┘ │ (per portal) │
└──────────────────┘ └─────────────────┘
A search call is only metered against the search bucket and the daily bucket. A non-search call (batch read/update, single PATCH, associations, etc.) is only metered against the burst bucket and the daily bucket. The two short-window buckets do not share counters.
What this means practically
What this means practically
Hitting search secondly limit (5/s):
Only further
/search
calls 429. Your batch reads, batch updates, single PATCHes, association calls — all keep working at full burst speed. This is actually useful: if your sync is bottlenecked on Search, you can pivot to using
lastmodifieddate
filters via batch endpoints, or use the IDs you already have to do batch reads, while Search cools off.
Hitting burst limit (190/10s):
Only non-search calls 429. You can still issue Search calls at 5/s. Useful for: continuing to identify deltas for queueing while in-flight updates drain, or refreshing a small set of records via Search even though your write pipeline is paused.
Hitting daily limit:
Everything stops. Search and non-search alike. Doesn't unblock until midnight in your portal's configured timezone — and remember this is shared across every private app in the portal, plus n8n flows, marketing tools, anything else hitting the API with that account.
So can one type of request block the other?
So can one type of request block the other?
Search → Burst:
No.
Saturating Search at 50 calls per 10s leaves your full 190/10s burst untouched.
Burst → Search:
No.
Saturating burst leaves Search's 5/s untouched.
Either → Daily:
Yes
, but only by contributing to the same daily counter. It's volume that kills you here, not the type.
In theory you can sustain ~50 search + ~190 other =
~240 calls per 10 seconds
indefinitely (until daily runs out), because the two buckets bill independently.
Implementation consequence
Implementation consequence
Your rate limiter needs to know which bucket a request hits before it acquires. Cleanest pattern:
Copy to clipboard
php
$limiter
->
acquire
(
'search'
,
$weight
=
1
)
;
// for search endpoints only
$limiter
->
acquire
(
'burst'
,
$weight
=
1
)
;
// for everything else
$limiter
->
acquire
(
'daily'
,
$weight
=
1
)
;
// every call, both kinds
In Redis: three separate keys, three separate Lua acquire scripts (or one script with a bucket parameter). A search call calls
acquire('search')
+
acquire('daily')
. A batch update calls
acquire('burst')
+
acquire('daily')
.
One subtle pitfall: when you backoff on a 429,
inspect
policyName
in the response body
to know which bucket actually fired. If you see
SECONDLY
from a search endpoint, you only need to delay search-bound jobs — burst-bound jobs in the queue can keep running. If you blanket-pause everything on any 429, you waste capacity on the bucket that's still healthy. Two queues (or two throttle keys) make this clean; one global pause is the lazy version.
The other subtlety: the burst response gives you
X-HubSpot-RateLimit-Remaining
to clamp local state against, but search doesn't return those headers. So your search counter is unverified — be slightly more conservative there (e.g., budget 4/s instead of 5) to absorb the unaccounted-for calls.
Copy
Give positive feedback
Give negative feedback
Retry
You said: Ok, so what will happen each time I make a request?
You said: Ok, so what will happen each time I make a request?
Ok, so what will happen each time I make a request? Let's say I have 100,000 requests to make that are instant. Do I need to increment each request based on the type? For example, if there is a search request, I need to increment both the search bucket and also the daily bucket. If it's a burst, then I can go to the daily and burst buckets. If I need to check if it can make a call, do I need to see both the daily and search, or burst, respectively? Isn't that too heavy for the infrastructure, adding additional load to each request?
13:44
Retry
Edit
Copy
Claude responded: Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out.
Claude responded: Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out.
Analyzed per-request overhead concerns and quantified Redis performance impact
Analyzed per-request overhead concerns and quantified Redis performance impact
Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out. But the overhead is much smaller than it sounds, and importantly, it's nowhere near your bottleneck.
What "two buckets per request" actually costs
What "two buckets per request" actually costs
Each request makes
one round trip to Redis
— not two — because you fold both bucket checks into a single Lua script that runs atomically server-side:
Copy to clipboard
lua
-- KEYS[1] = burst bucket key (or search)
-- KEYS[2] = daily bucket key
-- ARGV[1] = now (ms) ARGV[2] = window_ms
-- ARGV[3] = bucket_max ARGV[4] = daily_max
-- ARGV[5] = request_id ARGV[6] = daily_ttl
-- Trim sliding window
redis
.
call
(
'ZREMRANGEBYSCORE'
,
KEYS...
|
Claude
|
Claude
|
NULL
|
2362
|
|
2361
|
PostmanEditVIewWindowmelpHubSpot rate limit imple PostmanEditVIewWindowmelpHubSpot rate limit implementation strategyX-HubSpot-RateLimit-Secondly-RemainingDeprecated, ignoreSO Max=190, Interval=10000 means this portal is on a Pro/ Enterprise privately-distributedaoo aliyuius. I vousee max=110 .rs a oubnc VAutn nstal. max=250 means they nave uneAPI Limit Increase add-on.What vou cannot get via API• Search 5/sec limit - not exposed anywhere. Not in headers (search responses stripthem), not in any endpoint. It's a documented constant: vou assume it.• Daily usage broken out by app within a portal — the daily endpoint aggregates all privateapps. You can't tell from the API which app spent the budget.• Per-app burst limit programmatically — only inferred from Max in headers from a callthat app madePostman recide to fullv profile a vortallIhree calis in order1. GET /account-info/v3/details →grab portalid. timeZone also notethe x-HunSnot-Rate imit-x resnonse neaders (this is vour burst nronle)2. GET /account-info/v3/api-usage/daily/private-apps → daily limit, current spend.reset time3. (Optional) Trigger a 429 deliberately on a sandbox to confirm policyName shape, but thisisn't necessary just for inspection.That gives vou evervthing HubSpot will tell vou about a specific portal's limits. Save the tworequests as a Postman collection with (faccess token}} and (portal idi} ascollectionvariables and vou can profile anv portal in two clicks.Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..running and testing as it goesWrite a message…Opus 4.7 Adaptive vhellQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.HTTP https:pi.hubapi.com/account-info/v3/detailsnttps://api.nubapi.com/account-info/vs/details= DocsParamsAuthorization • Headers 9 Body Scripts SettinasAuth TypeTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorizationGET httos://:{tokenl}"supoont Dally • In 47mNo environmentvg Save100% L24* AIVariables in request> All variablesThu 7 May 14:13:11v COLLECtIONscontacts› CRM ObjectseRM owners> CRM Pipelines> DealsEngagements• D OLD ENGAGEMENTSGET list meetingsPST search moditied companiePOST search tasksGET read call> Post search callsGET list callsPOST meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio> HubsnotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscrintionGET Journal earliestGET lournal latestGeT https:ubspot-webhooks-lournal-nal.s.GET neyt offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY pRODEpTICC VA©Authi> Properties> RESSARCHwCCADAUPOSt search contact bv ohonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCSELOWSConnect Git E Console 2 TermirCNeR-JHaMxlZoiNd.CookiesBOdVJSONvPreview? Visualize"portalld": 4392066"additionalCurrencies": (200 OK • 591 ms • 1.23 KB •(| .•CQ108Globals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2361
|
|
2360
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 48 m100% [8DEV (docker)83Thu 7 May 14:12:53T81₴6DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)-zsh• 84screenpipe*•$5-zshPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2360
|
|
2359
|
PostmanEditVIewWindowmelpHubSpot rate limit imple PostmanEditVIewWindowmelpHubSpot rate limit implementation strategyX-HubSpot-RateLimit-Secondly-RemainingDeprecated, ignoreSO Max=190, Interval=10000 means this portal is on a Pro/ Enterprise privately-distributedaoo aliyuius. I vousee max=110 .rs a oubnc VAutn nstal. max=250 means they nave uneAPI Limit Increase add-on.What vou cannot get via API• Search 5/sec limit - not exposed anywhere. Not in headers (search responses stripthem), not in any endpoint. It's a documented constant: vou assume it.• Daily usage broken out by app within a portal — the daily endpoint aggregates all privateapps. You can't tell from the API which app spent the budget.• Per-app burst limit programmatically — only inferred from Max in headers from a callthat app madePostman recide to fullv profile a vortallIhree calls in order.1. GET /account-info/v3/details →grab portalid. timeZone also notethe x-HunSnot-Rate imit-x resnonse neaders (this is vour burst nronle)2. GET /account-info/v3/api-usage/daily/private-apps → daily limit, current spend.reset time3. (Optional) Trigger a 429 deliberately on a sandbox to confirm policyName shape, but thisisn't necessary just for inspection.That gives vou evervthing HubSpot will tell vou about a specific portal's limits. Save the tworequests as a Postman collection with (faccess token}} and ((portal idi} ascollectionvariables and vou can profile anv portal in two clicks.Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..running and testing as it goesWrite a message…Opus 4.7 Adaptive v100% L2Thu 7 May 14:12:40Xx Hubspot vQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.HTTP https:pi.hubapi.com/account-info/v3/detailsnttps://api.nubapi.com/account-info/vs/details= DocsParamsAuthorization • Headers 9 Body Scripts SettinasAuth TypeTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorizationGET Get EngGET httos://:{tokenl}supoont Dally • In 40 mNo environmentv~ Savev COLLECtIONscontacts› CRM ObjectseRM owners> CRM Pipelines> DealsEngagements• D OLD ENGAGEMENTSGET list meetingsPST search moditied companiePOST search tasksGET read call> Post search callsGET list callsPOST meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio> HubsnotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscrintionGET Journal earliestGET lournal latestGeT https:ubspot-webhooks-lournal-nal.s.GET neyt offcotpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY pRODEpTICC VA©Authi> Properties> RESSARCHwCCADAUPOSt search contact bv ohonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCSELOWS$ Connect Git @ Console TermirCookiesVariables in requestG token> All variablesCNeR-JHaMxlZoiNd.BOdVJSONvPreview? Visualize"portalld": 4392066"additionalCurrencies": (200 OK • 591 ms • 1.23 KB •(| .•CQ108Globals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2359
|
|
2358
|
Postman•• 0caltVIewWindowmelpHubSpot rate limit i Postman•• 0caltVIewWindowmelpHubSpot rate limit implementation strategy'+03:00""UlDomain": "app.hubspot.com","dataHostingLocation": "eu1'This doesn t show limits directly, but you need timezone tointerpret resetsAt tromendpoint #1 and to know when this portal's daily quota actually rolls over. There's no tierfield that tells you "this is Pro 190/10s vs Starter 100/10s" - you have to infer that from theburst headers below.3. Burst limit — onlv via response headersThere is no dedicated endpoint that returns "vour burst limit is 190 10s." You have to make anycheap call and read the headers. The simplest ping:GET https:/api.hubapi.com/account-info/v3/detailsAuthorization: Bearer portal access token}In Postman. look at the Headers tab of the response for:HeaderMeaningX-HuhSnot-Ratel imit-MaxBurst ceiling (e.g., 190 )X-HubSpot-RateLimit-RemainingCalls left in current windowX-HuoSoot-RateLimit-interval -vnusecondsWindow size, always 10000X-HubSpot-RateLimit-SecondlyDeprecated, ignoreX-HubSpot-RateLimit-Secondlv-RemainingDeprecated, ignoreSo Max=190. Interval=10000 means this portal is on a Pris/Enterprise privatelv-distributedapp at 190/10s. If you see Max=110 , it's a public OAuth install. Max=250 means they have theAPI Limit Increase add-onWhat you cannot get via API• Search 5/seclimit — not exposed anvwhere Not in headers (search responses stripthem). not in anv endooint. It's a documenonstant vou assume 10•Doily ucode broton out hu onn within a nortol- tho doily andnoint aaarogotoc oll nrivoteKeep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..Write a message…Thu 7 May 14:12:37Q SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.GET next off.HTTP https:pi.hubapi.com/account-info/v3/detailsnttps://api.nubapi.com/accoun-info/vs/details= DocsAuthorization • Headers 9 Body Scripts SettinasAuth TypeTokenine autnorization neader will oe automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorization.GET Get EngGET httos://:{tokenl}supoont Dally • In 40 mNo environmentv~ Save100% L24* AIVariables in requestG token> All variablesv COLLECtIONscontacts› CRM ObjectseRM owners> CRM PipelinesDealsEngagements• D OLD ENGAGEMENTSGET list meetingsPST search moditied companiePOST search tasksGET read call> Post search callsGET list callsPOST meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio> HubsnotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscrintionGET Journal earliestGET lournal latestGET https:ubspot-webhooks-lournal-nal.s.GET neyt offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY pRODEptIcC vA©Authi> Properties> RESSARCHwCCADAUPOST search contact bv ohonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCSELOWS$ Connect Git @ Console TermirCNeR-JHaMxlZoiNd.CookiesBodyJSONv200 OK • 591 ms • 1.23 KB •(| .•CQ108Previewp. Visualize v"portalld": 4392066odditionalCurroncioch. ПOpus 4.7 Adaptive vGlobals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2358
|
|
2357
|
PostmancaltVIewWindowmelpHubSpot rate limit imple PostmancaltVIewWindowmelpHubSpot rate limit implementation strategy vGEl nttps://ap1.hubap1.com/account-into/v3/detailsAuthorization: Bearer (portal access token}Kerums."portalid": 123456,"accountType": "STANDARD","timeZone": "Europe/Sofia"."utcoftset": "+03:00","uiDomain": "app.hubspot.com","dataHostingLocation": "eu1'T'his doesn t show limits directly, but you need timezone tointerpret resetsAt fromendpoint #1 and to know when this portal's dailv quota actuallv rolls over. There's no tierfeld that tells you "this is Pro 190/10s vs Starter 100 /10s" — you have to infer that from theburst headers below.3. Burst limit — onlv via response headersThere is no dedicated endpoint that returns "vour burst limit is 190 10s." You have to make anvcheap call and read the headers. The simplest ping:GET https:api.hubapi.com/account-info/v3/detailsAuthorization: Bearer portal access tokenIn Postman, look at the Headers tab of the response for:HeaderMeaningX-HubSpot-RateLimit-MaxBurst ceiling (e.g., 190 )X-HubSpot-RateLimit-RemainingCalls left in current windowX-HubSnot-RateLimit-interval -Mil isecondsWindow size, always 10000X-HubSpot-RateLimit-SecondlyDeprecated, ignoreKeep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..Write a message…Thu 7 May 14:12:34Q SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.GET next off. •HTTP https:pi.hubapi.com/account-info/v3/detailsnttps://api.nubapi.com/account-info/vs/details= DocsParamsAuthorization • Headers 9 Body ScriptsSettinasAuth TypeTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorization.GET Get EngGET httos://:{tokenl}supoont Dally • In 40 mNo environmentv~ Save100% L24* AIVariables in requestG token> All variablesCOLLECTIONScontacts› CRM ObjectseRM owners> CRM PipelinesDealsEngagements• D OLD ENGAGEMENTSGET list meetingsPST search moditied companiePOST search tasksGET read call> Post search callsGET list callsPOST meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio> HubsnotJournal & webhoooks v4POSt Get tokenGET get subscriptionsPOST create subscrintionGET Journal earliestGET lournal latestGET https://hubspot-webhooks-iournal-na1.sGET neyt offcotpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAL.GET DEAL WITH HISTORY pRODEptIcC vA©Authi> Properties> RESSARCHwCCADAUPOST search contact bv ohonePOSt search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCSELOWSConnect Git E Console 2 TermirCNeR-JHaMxlZoiNd.CookiesBodyJSONvPreview? Visualize"portalld": 4392066"timeZone". "US/Eastern" ."additionalCurrencies": (200 OK • 591 ms • 1.23 KB •(| .•CQ108Opus 4.7 Adaptive vGlobals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2357
|
|
2356
|
PostmanEditVIewWindowmelpHubSpot rate limit implem PostmanEditVIewWindowmelpHubSpot rate limit implementation strategy vThere are essentially two endpoints plus response header inspection. That's the entire APIsurface for rate-limit discovery per portal.1. Daily limit + current daily usageGET https://api.hubapi.com/account-info/v3/api-usage/daily/private-appsAuthorization: Bearer {portal_access_token}Returns:"results": [{"name": "orivate-aoos-ao1-cauis-danv"."usageLimit": 1000000,"currentUsage": 47213"resetsAt": "2026-05-08T05:00: 00z","fetchStatus": "SUCCESS"This is the only API that tells you the daily ceiling and current spend for a portal. Theendpoint name says private-apps, which is what it's officially documented for — itaggregates all legacy private apps in that portal. If your portal is connected via OAuth (publicapp), this endpoint may return empty results or a different shape; test it on one of yourcustomer portals to see.2. Portal context (timerrelated info)GET https://api.hubapi.com/account-info/v3/detailsAuthorization: Bearer {portal access token?Returns:"portalid": 123456."accountType": "STANDARD","timeZone": "Europe/Sofia",Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno.iWrite a message…Opus 4.7 Adaptive~Claude is Al and can make mistakes. Please double-check responses.Inu / May 14:12-22UparadeQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.HTTP https:pi.hubapi.com/account-info/v3/detailsnttps://api.nubapi.com/accoun-info/vs/detailsE DocsAuth TypeAuthorization • Headers 9 Body ScriptsSettingsTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorization.((token))40GET https://e•supoont Dally • In 40 mNo environmentva SaveServiy2w Cookies100% L24* AIVariables in requestG token> All variablesv COLLECtIONscontacts› CRM ObjectseRM owners› CRM Pipelines> Deals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiePOST search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET get subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGeT https://hubspot-webhooks-iournal-na1.sGET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTG> SPFCS> FLOWSConnect Git E Console 2 TerminCNeR-JHgMxIZQINQ…..BodyJSONvPreview? Visualize"results":"name": "private-aops-aoi-calls-dailv"."ucadel imi+". 1000000"collectedAt": "2026-05-07T11:11:49.6772"."2026-05-08T04:00:002"200 OK • 194 ms • 1.2 KB •C| .•=Q108Globals Vault Tools S000...
|
iTerm2
|
NULL
|
NULL
|
2356
|
|
2355
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 48 m100% [Thu 7 May 14:12:22DEV (docker)83DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)-zsh• 84screenpipe*•$5-zsh₴6Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2355
|
|
2354
|
PostmanEditVIewWindowmelpHubSpot rate limit implem PostmanEditVIewWindowmelpHubSpot rate limit implementation strategy vThere are essentially two endpoints plus response header inspection. That's the entire APIsurface for rate-limit discovery per portal.1. Daily limit + current daily usageGET https://api.hubapi.com/account-info/v3/api-usage/daily/private-appsAuthorization: Bearer {portal_access_token}Returns:"results": [{"name": "orivate-aoos-ao1-cauis-danv"."usageLimit": 1000000,"currentUsage": 47213"resetsAt": "2026-05-08T05:00: 00z","fetchStatus": "SUCCESS"This is the only API that tells you the daily ceiling and current spend for a portal. Theendpoint name says private-apps, which is what it's officially documented for — itaggregates all legacy private apps in that portal. If your portal is connected via OAuth (publicapp), this endpoint may return empty results or a different shape; test it on one of yourcustomer portals to see.2. Portal context (time7related info)GET https://api.hubapi.com/account-info/v3/detailsAuthorization: Bearer {portal access token?Returns:"portalid": 123456."accountType": "STANDARD","timeZone": "Europe/Sofia",Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno.iWrite a message…Opus 4.7 Adaptive~Claude is Al and can make mistakes. Please double-check responses.Inu / May 14:12-20UparadeQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.GET read ciHTTP https:pi.hubapi.com/account-info/v3/api-usaqe/daily/private-appshttps://api.hubapi.com/account-info/v3/api-usage/daily/private-appsE DocsAuth TypeAuthorization • Headers 9 Body ScriptsSettingsTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorization((token))40GET https://t•supoont Dally • In 40 m100% L2No environmentv~ SaveVariables in requestG tokenCookies> All variablesv COLLECtIONscontacts› CRM ObjectseRM owners› CRM PipelinesDeals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPST search moditied companiePoSt search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET get subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGeT https://hubspot-webhooks-iournal-na1.sGET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAL.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCS> FLOWSConnect Git E Console 2 TerminCNeR-JHgMxIZQINQ…..BodyJSONvPreview? Visualize"results":"name": "private-aops-aoi-calls-dailv"."ucadel imi+". 1000000"collectedAt": "2026-05-07T11:11:49.6772"."2026-05-08T04:00:002"200 OK • 194 ms • 1.2 KB •C| .•=Q108Globals Vault Tools S000...
|
iTerm2
|
NULL
|
NULL
|
2354
|
|
2353
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 48 m100% [Thu 7 May 14:12:20DEV (docker)83DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)-zsh• 84screenpipe*•$5-zsh₴6Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2353
|
|
2352
|
PostmanEditVIewWindowmelpHubSpot rate limit implem PostmanEditVIewWindowmelpHubSpot rate limit implementation strategy vThere are essentially two endpoints plus response header inspection. That's the entire APIsurface for rate-limit discovery per portal.1. Daily limit + current daily usageGET https://api.hubapi.com/account-info/v3/api-usage/daily/private-appsAuthorization: Bearer {portal_access_token}Returns:"results": [{"name": "orivate-aoos-ao1-cauis-danv"."usageLimit": 1000000,"currentUsage": 47213"resetsAt": "2026-05-08T05:00: 00z","fetchStatus": "SUCCESS"This is the only API that tells you the daily ceiling and current spend for a portal. Theendpoint name says private-apps, which is what it's officially documented for — itaggregates all legacy private apps in that portal. If your portal is connected via OAuth (publicapp), this endpoint may return empty results or a different shape; test it on one of yourcustomer portals to see.2. Portal context (timerrelated info)GET https://api.hubapi.com/account-info/v3/detailsAuthorization: Bearer {portal access token?Returns:"portalid": 123456."accountType": "STANDARD","timeZone": "Europe/Sofia",Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno.iWrite a message…Opus 4.7 AdaptiveClaude is Al and can make mistakes. Please double-check responses.Thu 7 May 14:12:19Q SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.https:///api.hubapi.com/account-info/v3/api-usaqe/daily/private-appsaccount-info/v3/api-usage/daily/private-apps-E DocsAuth TypeAuthorization • Headers 9 Body ScriptsSettingsTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorization((token))40hhlGET https://t•supoont Dally • In 40 mNo environmentv~ Save100% L24* AIVariables in requestCookies> All variablesv COLLECtIONscontacts› CRM ObjectseRM owners› CRM PipelinesDeals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPST search moditied companiePOST search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET get subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGeT https://hubspot-webhooks-iournal-na1.sGET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAL.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCS> FLOWSConnect Git E Console 2 TerminCNeR-JHaMxlZoiNd.BOdVJSONvPreview? Visualize"results":"name": "private-aops-aoi-calls-dailv"."ucadel imi+". 1000000"collectedAt": "2026-05-07T11:11:49.6772"."2026-05-08T04:00:002"200 OK • 194 ms • 1.2 KB •C| .•=Q108Globals Vault Tools S000...
|
iTerm2
|
NULL
|
NULL
|
2352
|
|
2351
|
ClaudeVIeWWindowHelpHubSpot rate limit implementat ClaudeVIeWWindowHelpHubSpot rate limit implementation strategyThere are essentially two endpoints plus response header inspection. That's the entire APIsurface for rate-limit discovery per portal.1. Daily limit + current daily usageGET https://api.hubapi.com/account-info/v3/api-usage/daily/private-appsAuthorization: Bearer {portal_access_token}Returns:"results": [{"name": "orivate-aoos-ao1-cauis-danv"."usageLimit": 1000000,"currentUsage": 47213"resetsAt": "2026-05-08T05:00 : 00z","fetchStatus": "SUCCESS"This is the only API that tells you the daily ceiling and current spend for a portal. Theendpoint name says private-apps, which is what it's officially documented for — itaggregates all legacy private apps in that portal. If your portal is connected via OAuth (publicapp), this endpoint may return empty results or a different shape; test it on one of yourcustomer portals to see.2. Portal context (time7related info)GET https://api.hubapi.com/account-info/v3/detailsAuthorization: Bearer {portal access token?Returns:"portallid": 123456."accountType": "STANDARD","timeZone": "Europe/Sofia",Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno.Write a message…Opus 4.7 AdaptiveClaude is Al and can make mistakes. Please double-check responses.40hhlsupoont Dally • In 40 mThu 7 May 14:12:18Q Searchn. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.HTTP https:pi.hubapi.com/account-info/v3/api-usage/daily/private-appshttps://api.hubapi.com/account-info/v3/api-usage/daily/private-apps= Docs Params Authorization • Headers 9 Body Scripts SettingsAuth TypeBearer TokenTokenine autnorization neader will oe automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorizationGET Get Eng((token))GET https://t•No environmentvg Save100% L2* AIVariables in requestCookies> All variablesCNeR-JHaMxlZoiNd.Body Cookies 1 Headers 20 lest ResultsJSONvPreview ?. Visualize v"results": ["name": "private-aops-aoi-calls-daiilv".."ucadel imi+". 1000000"collectedAt": "2026-05-07T11:11:49.6772".*2026-05-08T04:00:002*200 OK • 194 ms • 1.2 KB •C| .•=Q108Globals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2351
|
|
2350
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 48 m100% [Thu 7 May 14:12:18DEV (docker)T81DOCKERLast login: Thu MayDEV (docker)H82APP (-zsh)83-zsh• 84screenpipe*•$5-zsh₴67 09:44:56 on ttys006Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2350
|
|
2349
|
Skip to content
Skip to content
Click to collapse
Skip to content
Skip to content
Click to collapse
⌘B
Drag to resize
Open sidebar
Chat
Cowork
Code
New chat ⌘N
New chat
⌘N
Projects
Artifacts
Customize
Pinned
Bulgarian citizenship application process for EU residents
More options for Bulgarian citizenship application process for EU residents
Dawarich location tracking project
More options for Dawarich location tracking project
Recents
View all
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Screenpipe retention policy code location
More options for Screenpipe retention policy code location
Viewing retention policy in screenpipe
More options for Viewing retention policy in screenpipe
Clean shot x video recording termination issue
More options for Clean shot x video recording termination issue
HubSpot rate limit handling with executeRequest
More options for HubSpot rate limit handling with executeRequest
Untitled
More options
💬 Screen pipe. Is there ability…
More options for 💬 Screen pipe. Is there ability…
SMB mount access inconsistency between Finder and iTerm
More options for SMB mount access inconsistency between Finder and iTerm
💬 What is the best switch I can…
More options for 💬 What is the best switch I can…
Permission denied on screenpipe volume
More options for Permission denied on screenpipe volume
Screenpipe sync database attachment error
More options for Screenpipe sync database attachment error
Last swimming outing with Dani
More options for Last swimming outing with Dani
Definition of incarcerated
More options for Definition of incarcerated
Chromecast remote volume buttons not working
More options for Chromecast remote volume buttons not working
Salesforce API errors with Organization and FieldDefinition queries
More options for Salesforce API errors with Organization and FieldDefinition queries
Daily activity summary from screenpipe data
More options for Daily activity summary from screenpipe data
MacBook unexpected restarts and kanji screen
More options for MacBook unexpected restarts and kanji screen
Security patch review and testing guidance
More options for Security patch review and testing guidance
Food calorie values reference
More options for Food calorie values reference
Tracking location history from last week
More options for Tracking location history from last week
Lukas Pro
Get apps and extensions
HubSpot rate limit implementation strategy, rename chat
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Share chat
Claude finished the response
You said: So just a solution for rate limit implementation.
You said: So just a solution for rate limit implementation.
So just a solution for rate limit implementation. The situation currently is that there are some daily and secondary limits for HubSpot. I would like to make sure I never reach a 429 error rate limit. The requests can come from any flow. It can be:
updating activity (engagement, meeting, call, note)
searching for a company or contact
updating deal
patching IDs
Review what the limit is at the moment in the HubSpot documentation and then think of the solution:
where to store it
iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 48 m100% [Thu 7 May 14:12:15DEV (docker)T81DOCKERLast login: Thu MayDEV (docker)H82APP (-zsh)83-zsh• 84screenpipe*•$5-zsh₴67 09:44:56 on ttys006Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
Claude
|
Claude
|
NULL
|
2349
|
|
2348
|
Skip to content
Skip to content
Click to collapse
Skip to content
Skip to content
Click to collapse
⌘B
Drag to resize
Open sidebar
Chat
Cowork
Code
New chat ⌘N
New chat
⌘N
Projects
Artifacts
Customize
Pinned
Bulgarian citizenship application process for EU residents
More options for Bulgarian citizenship application process for EU residents
Dawarich location tracking project
More options for Dawarich location tracking project
Recents
View all
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Screenpipe retention policy code location
More options for Screenpipe retention policy code location
Viewing retention policy in screenpipe
More options for Viewing retention policy in screenpipe
Clean shot x video recording termination issue
More options for Clean shot x video recording termination issue
HubSpot rate limit handling with executeRequest
More options for HubSpot rate limit handling with executeRequest
Untitled
More options
💬 Screen pipe. Is there ability…
More options for 💬 Screen pipe. Is there ability…
SMB mount access inconsistency between Finder and iTerm
More options for SMB mount access inconsistency between Finder and iTerm
💬 What is the best switch I can…
More options for 💬 What is the best switch I can…
Permission denied on screenpipe volume
More options for Permission denied on screenpipe volume
Screenpipe sync database attachment error
More options for Screenpipe sync database attachment error
Last swimming outing with Dani
More options for Last swimming outing with Dani
Definition of incarcerated
More options for Definition of incarcerated
Chromecast remote volume buttons not working
More options for Chromecast remote volume buttons not working
Salesforce API errors with Organization and FieldDefinition queries
More options for Salesforce API errors with Organization and FieldDefinition queries
Daily activity summary from screenpipe data
More options for Daily activity summary from screenpipe data
MacBook unexpected restarts and kanji screen
More options for MacBook unexpected restarts and kanji screen
Security patch review and testing guidance
More options for Security patch review and testing guidance
Food calorie values reference
More options for Food calorie values reference
Tracking location history from last week
More options for Tracking location history from last week
Lukas Pro
Get apps and extensions
HubSpot rate limit implementation strategy, rename chat
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Share chat
Claude finished the response
You said: So just a solution for rate limit implementation.
You said: So just a solution for rate limit implementation.
So just a solution for rate limit implementation. The situation currently is that there are some daily and secondary limits for HubSpot. I would like to make sure I never reach a 429 error rate limit. The requests can come from any flow. It can be:
updating activity (engagement, meeting, call, note)
searching for a company or contact
updating deal
patching IDs
Review what the limit is at the moment in the HubSpot documentation and then think of the solution:
where to store it
how to read it
how to work with multiple jobs
how to work with paginated requests Let's consider a situation when there are 600 opportunities to sync. What would be the flow? How would the rate limit be recognized? How would it be handled? What are the potential issues? [API usage guidelines and limits - HubSpot docs](
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
). Example of such a error Client error:
POST https://api.hubapi.com/crm/v3/objects/contact/search
resulted in a
429 Too Many Requests
response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT","correlationId":"019dffc4-4 (truncated...). Think carefully about the implementation and potential issue and bottlenecks.
Show more
10:42
Retry
Edit
Copy
Claude responded: Current HubSpot limits (Apr 2026)
Claude responded: Current HubSpot limits (Apr 2026)
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Current HubSpot limits (Apr 2026)
Current HubSpot limits (Apr 2026)
For privately distributed apps (which is what Jiminny presumably uses with HubSpot), the limits are layered: a per-app burst window of 100/10s on Free/Starter, 190/10s on Pro/Enterprise, or 250/10s with the API Limit Increase add-on
, plus a per-account daily cap of 250k / 625k / 1M depending on tier — shared across all private apps in the account
. The burst window is per app; the daily quota is per portal.
hubspot
hubspot
hubspot
hubspot
The Search API is special: five requests per second per account, capped at 200 records per page, with a hard 10,000-result ceiling per query
. That's the limit the 429 in your example is hitting (
secondly limit
on
/crm/v3/objects/contact/search
). It's a separate bucket from the 190/10s, and critically, search responses do not include the
X-HubSpot-RateLimit-*
headers
— you can't read remaining capacity off the response, you have to track it yourself.
hubspot
hubspot
hubspot
hubspot
Non-search endpoints return
X-HubSpot-RateLimit-Remaining
,
-Max
, and
-Interval-Milliseconds
. The daily headers are not returned for OAuth-authenticated calls
, so for those you check the account-info endpoint or maintain your own counter. There's also a soft rule: errors should stay under 5% of total daily requests
— that's enforced for marketplace listing, but it's also a sane operational target.
hubspot
hubspot
hubspot
hubspot
So you have
four buckets
to track at minimum: app-burst (10s sliding), search-secondly (1s sliding), account-daily (24h fixed, midnight in HubSpot's TZ), and per-app daily share (your own budgeting on top of the account cap).
Where to store it
Where to store it
Redis. It's the only realistic option once you have multiple queue workers — DB-backed counters serialize too much, and in-process state can't coordinate across workers. Laravel already speaks Redis natively, and you get atomic
INCR
/
EXPIRE
plus Lua scripting for true CAS semantics.
Key layout I'd use:
Copy to clipboard
hubspot:rl:burst:{portalId}:{appId} ZSET (sliding 10s)
hubspot:rl:search:{portalId} ZSET (sliding 1s)
hubspot:rl:daily:{portalId} STRING + TTL to midnight TZ
hubspot:rl:meta:{portalId} HASH (last seen headers)
The two short-window buckets are sliding-window-log (Redis ZSET, score =
microtime
, member = unique request id). Lua script removes entries older than the window, counts remaining slots, and only adds the new one if there's room — all atomic. Fixed windows are simpler but allow 2× the limit at the boundary, which on a 5/s window is brutal.
The daily bucket is a plain
INCR
with TTL set to seconds-until-midnight in
HubSpot's account timezone
, not yours — Sofia is UTC+2/+3 but your portal might be set to US Eastern. Get this once and cache it.
How to read it
How to read it
Two-phase: optimistic pre-check, authoritative post-update.
Before a call, run the Lua acquire script. If it returns "denied," sleep until a slot frees up (the script can return ms-until-next-slot) or push the job back to the queue with a delay. Don't busy-loop.
After the call, parse
X-HubSpot-RateLimit-Remaining
/
-Max
/
-Interval-Milliseconds
and store them in
hubspot:rl:meta:{portalId}
. This is your reality check — if your local counter says 50 remaining but HubSpot's header says 5, you trust HubSpot and clamp your counter. This handles clock drift, missed accounting (e.g., crashed worker that took a token but never made the request), and other apps in the same account consuming the daily budget invisibly.
For search specifically, since headers don't come back, the local counter
is
the source of truth — meaning if you ever crash mid-flight, you've under-counted. Always release tokens on connection-level failure but
not
on 429 (you really did make that request).
How to work with multiple jobs
How to work with multiple jobs
The queue layer needs to enforce concurrency separately from the rate limiter. Both work together:
Concurrency cap
via
Queue::throttle()
or a Redis semaphore — limits how many sync workers run in parallel against HubSpot. Without this, you can have 50 workers all blocked waiting for tokens, which is wasteful and creates retry storms.
Per-tenant fairness
— if you sync many Jiminny customers into different HubSpot portals, each portal has its own bucket but you still want one slow portal not to starve others. Either separate queues per portal or a fair-share scheduler.
Priority lanes
— webhook-driven updates (user-visible latency) should outrank background batch syncs. Two queues:
hubspot-priority
and
hubspot-bulk
, with priority workers taking 70% of the burst budget and bulk taking 30% (enforce via separate sub-buckets if you really want hard separation, otherwise just pull from priority first)....
|
Claude
|
Claude
|
NULL
|
2348
|
|
2347
|
Skip to content
Skip to content
Click to collapse
Skip to content
Skip to content
Click to collapse
⌘B
Drag to resize
Open sidebar
Chat
Cowork
Code
New chat ⌘N
New chat
⌘N
Projects
Artifacts
Customize
Pinned
Bulgarian citizenship application process for EU residents
More options for Bulgarian citizenship application process for EU residents
Dawarich location tracking project
More options for Dawarich location tracking project
Recents
View all
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Screenpipe retention policy code location
More options for Screenpipe retention policy code location
Viewing retention policy in screenpipe
More options for Viewing retention policy in screenpipe
Clean shot x video recording termination issue
More options for Clean shot x video recording termination issue
HubSpot rate limit handling with executeRequest
More options for HubSpot rate limit handling with executeRequest
Untitled
More options
💬 Screen pipe. Is there ability…
More options for 💬 Screen pipe. Is there ability…
SMB mount access inconsistency between Finder and iTerm
More options for SMB mount access inconsistency between Finder and iTerm
💬 What is the best switch I can…
More options for 💬 What is the best switch I can…
Permission denied on screenpipe volume
More options for Permission denied on screenpipe volume
Screenpipe sync database attachment error
More options for Screenpipe sync database attachment error
Last swimming outing with Dani
More options for Last swimming outing with Dani
Definition of incarcerated
More options for Definition of incarcerated
Chromecast remote volume buttons not working
More options for Chromecast remote volume buttons not working
Salesforce API errors with Organization and FieldDefinition queries
More options for Salesforce API errors with Organization and FieldDefinition queries
Daily activity summary from screenpipe data
More options for Daily activity summary from screenpipe data
MacBook unexpected restarts and kanji screen
More options for MacBook unexpected restarts and kanji screen
Security patch review and testing guidance
More options for Security patch review and testing guidance
Food calorie values reference
More options for Food calorie values reference
Tracking location history from last week
More options for Tracking location history from last week
Lukas Pro
Get apps and extensions
HubSpot rate limit implementation strategy, rename chat
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Share chat
Claude finished the response
You said: So just a solution for rate limit implementation.
You said: So just a solution for rate limit implementation.
So just a solution for rate limit implementation. The situation currently is that there are some daily and secondary limits for HubSpot. I would like to make sure I never reach a 429 error rate limit. The requests can come from any flow. It can be:
updating activity (engagement, meeting, call, note)
searching for a company or contact
updating deal
patching IDs
Review what the limit is at the moment in the HubSpot documentation and then think of the solution:
where to store it
how to read it
how to work with multiple jobs
how to work with paginated requests Let's consider a situation when there are 600 opportunities to sync. What would be the flow? How would the rate limit be recognized? How would it be handled? What are the potential issues? [API usage guidelines and limits - HubSpot docs](
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
). Example of such a error Client error:
POST https://api.hubapi.com/crm/v3/objects/contact/search
resulted in a
429 Too Many Requests
response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT","correlationId":"019dffc4-4 (truncated...). Think carefully about the implementation and potential issue and bottlenecks.
Show more
10:42
Retry
Edit
Copy
Claude responded: Current HubSpot limits (Apr 2026)
Claude responded: Current HubSpot limits (Apr 2026)
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Current HubSpot limits (Apr 2026)
Current HubSpot limits (Apr 2026)
For privately distributed apps (which is what Jiminny presumably uses with HubSpot), the limits are layered: a per-app burst window of 100/10s on Free/Starter, 190/10s on Pro/Enterprise, or 250/10s with the API Limit Increase add-on
, plus a per-account daily cap of 250k / 625k / 1M depending on tier — shared across all private apps in the account
. The burst window is per app; the daily quota is per portal.
hubspot
hubspot
hubspot
hubspot
The Search API is special: five requests per second per account, capped at 200 records per page, with a hard 10,000-result ceiling per query
. That's the limit the 429 in your example is hitting (
secondly limit
on
/crm/v3/objects/contact/search
). It's a separate bucket from the 190/10s, and critically, search responses do not include the
X-HubSpot-RateLimit-*
headers
— you can't read remaining capacity off the response, you have to track it yourself.
hubspot
hubspot
hubspot
hubspot
Non-search endpoints return
X-HubSpot-RateLimit-Remaining
,
-Max
, and
-Interval-Milliseconds
. The daily headers are not returned for OAuth-authenticated calls
, so for those you check the account-info endpoint or maintain your own counter. There's also a soft rule: errors should stay under 5% of total daily requests
— that's enforced for marketplace listing, but it's also a sane operational target.
hubspot
hubspot
hubspot
hubspot
So you have
four buckets
to track at minimum: app-burst (10s sliding), search-secondly (1s sliding), account-daily (24h fixed, midnight in HubSpot's TZ), and per-app daily share (your own budgeting on top of the account cap).
Where to store it
Where to store it
Redis. It's the only realistic option once you have multiple queue workers — DB-backed counters serialize too much, and in-process state can't coordinate across workers. Laravel already speaks Redis natively, and you get atomic
INCR
/
EXPIRE
plus Lua scripting for true CAS semantics.
Key layout I'd use:
Copy to clipboard
hubspot:rl:burst:{portalId}:{appId} ZSET (sliding 10s)
hubspot:rl:search:{portalId} ZSET (sliding 1s)
hubspot:rl:daily:{portalId} STRING + TTL to midnight TZ
hubspot:rl:meta:{portalId} HASH (last seen headers)
The two short-window buckets are sliding-window-log (Redis ZSET, score =
microtime
, member = unique request id). Lua script removes entries older than the window, counts remaining slots, and only adds the new one if there's room — all atomic. Fixed windows are simpler but allow 2× the limit at the boundary, which on a 5/s window is brutal.
The daily bucket is a plain
INCR
with TTL set to seconds-until-midnight in
HubSpot's account timezone
, not yours — Sofia is UTC+2/+3 but your portal might be set to US Eastern. Get this once and cache it.
How to read it
How to read it
Two-phase: optimistic pre-check, authoritative post-update.
Before a call, run the Lua acquire script. If it returns "denied," sleep until a slot frees up (the script can return ms-until-next-slot) or push the job back to the queue with a delay. Don't busy-loop.
After the call, parse
X-HubSpot-RateLimit-Remaining
/
-Max
/
-Interval-Milliseconds
and store them in
hubspot:rl:meta:{portalId}
. This is your reality check — if your local counter says 50 remaining but HubSpot's header says 5, you trust HubSpot and clamp your counter. This handles clock drift, missed accounting (e.g., crashed worker that took a token but never made the request), and other apps in the same account consuming the daily budget invisibly.
For search specifically, since headers don't come back, the local counter
is
the source of truth — meaning if you ever crash mid-flight, you've under-counted. Always release tokens on connection-level failure but
not
on 429 (you really did make that request).
How to work with multiple jobs
How to work with multiple jobs
The queue layer needs to enforce concurrency separately from the rate limiter. Both work together:
Concurrency cap
via
Queue::throttle()
or a Redis semaphore — limits how many sync workers run in parallel against HubSpot. Without this, you can have 50 workers all blocked waiting for tokens, which is wasteful and creates retry storms.
Per-tenant fairness
— if you sync many Jiminny customers into different HubSpot portals, each portal has its own bucket but you still want one slow portal not to starve others. Either separate queues per portal or a fair-share scheduler.
Priority lanes
— webhook-driven updates (user-visible latency) should outrank background batch syncs. Two queues:
hubspot-priority
and
hubspot-bulk
, with priority workers taking 70% of the burst budget and bulk taking 30% (enforce via separate sub-buckets if you really want hard separation, otherwise just pull from priority first).
Backoff on 429
— respect the
Retry-After
header. If absent, exponential with jitter (e.g.,
min(2^attempt * 250ms, 30s) ± 20%
). The jitter is non-negotiable; without it, simultaneous 429s retry in lockstep and you get thundering-herd 429s on retry.
How to work with paginated requests
How to work with paginated requests
The trap is treating "fetch all" as one logical operation. Each page is its own API call and competes for tokens with everything else.
Two practical rules:
Don't hold the worker idle while paginating.
If page N takes 500ms and page N+1 needs to wait 800ms for a token, you've burned 800ms of worker time doing nothing. Instead, fetch page N, dispatch the
processing
of page N as a separate job, and queue a "fetch page N+1" job with a delay equal to the wait time. Each page becomes its own atomic unit.
Always batch where HubSpot offers it.
POST /crm/v3/objects/{type}/batch/{read|update|create}
accepts up to 100 IDs per call. For your "patching IDs" flow this is the difference between 600 calls and 6.
Walkthrough: 600 opportunities
Walkthrough: 600 opportunities
Naive flow (one PATCH per deal): 600 calls. At 190/10s that's ~32s of API time, well under daily. You'd hit burst easily without throttling. Plus likely 1-3 search calls upfront and N association calls.
Sane flow:
Identify deltas
— if you can avoid Search at all, do. Use
lastmodifieddate
filter on a single search if you must, paginate at limit=200. For 600 deals that's 3 search calls @ 5/s = ~600ms naturally throttled.
Batch read
current state —
POST /crm/v3/objects/deals/batch/read
with 100 IDs per call → 6 calls. Burst weight 6.
Compute diff
in your code (no API).
Batch update
—
POST /crm/v3/objects/deals/batch/update
with 100 per call → 6 calls.
Associations
—
POST /crm/v4/associations/{from}/{to}/batch/create
if needed → another few batch calls.
Total: ~15-20 API calls for 600 deals. Burst budget consumed: 20/190 over ~5s. Daily impact: trivial.
Recognition: pre-check denies if
<weight>
slots aren't free; on 429 the response surfaces
policyName
(DAILY/SECONDLY) — log it, push the job back with
Retry-After
delay, increment a metric so you can alarm on sustained 429 rate.
Pitfalls & bottlenecks worth pre-empting
Pitfalls & bottlenecks worth pre-empting
Daily quota is shared across the whole portal
, including any n8n flows, other private apps, marketing automation calling APIs, etc. Budget for ~70-80% of the documented limit, not 100%. Add an internal per-app daily cap so a runaway sync can't starve other apps.
Search is uniquely fragile
: separate 5/s bucket, no headers to read, 10k-result cap per query. If you ever hit 10k+ deals matching a filter, partition by
hs_object_id
ranges or by
lastmodifieddate
windows.
Retry storms after HubSpot incidents
— always jitter, always cap total retries (e.g., 5 attempts, then dead-letter).
Webhook → sync → webhook loops
— when your update fires a HubSpot webhook that triggers another sync. Tag your own writes (e.g., a custom property
jy_last_sync_id
) and ignore webhooks where it just changed.
Token refresh
— OAuth refresh itself counts against burst. Cache the access token in Redis with TTL =
expires_in - 60s
, single-flight the refresh (only one worker refreshes; others wait on a lock).
Search latency for fresh writes
— newly created/updated objects don't appear in search instantly. Don't write-then-search; use returned IDs directly.
Clock skew
— Redis is authoritative. Don't use
time()
from each worker for window scoring; use...
|
Claude
|
Claude
|
NULL
|
2347
|
|
2346
|
rostmanEditVIewWindowmelpHubSpot rate limit implem rostmanEditVIewWindowmelpHubSpot rate limit implementation strategy vThere are essentially two endpoints plus response header inspection. That's the entire APIsurface for rate-limit discovery per portal.1. Daily limit + current daily usageGET https://api.hubapi.com/account-info/v3/api-usage/daily/private-appsAuthorization: Bearer {portal_access_token}Returns:"results": [{"name": "orivate-aoos-ao1-cauis-danv"."usageLimit": 1000000,"currentUsage": 47213"resetsAt": "2026-05-08T05:00 : 00z","fetchStatus": "SUCCESS"This is the only API that tells you the daily ceiling and current spend for a portal. Theendpoint name says private-apps, which is what it's officially documented for — itaggregates all legacy private apps in that portal. If your portal is connected via OAuth (publicapp), this endpoint may return empty results or a different shape; test it on one of yourcustomer portals to see.2. Portal context (timezone, tier-related info)GET https://api.hubapi.com/account-info/v3/detailsAuthorization: Bearer {portal access token?Returns:"portalid": 123456."accountType": "STANDARD","timeZone": "Europe/Sofia",Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno.iWrite a message…Opus 4.7 Adaptive~Claude is Al and can make mistakes. Please double-check responses.hhlQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.GET read ciGET Get EnaGET https://e•HTTP https:pi.hubapi.com/account-info/v3/api-usaqe/daily/private-appshttps://api.hubapi.com/account-info/v3/api-usage/daily/private-appsE DocsAuth TypeAuthorization • Headers 9 Body ScriptsSettingsToken((token))The authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorizationsupoont Dally • In 40 mNo environmentvg SaveCookies100% L2* AIVariables in request> All variablesThu 7 May 14:12:13v COLLECtIONscontacts› CRM ObjectseRM owners› CRM Pipelines> Deals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiesPoSt search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET get subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGeT https://hubspot-webhooks-iournal-na1.sGET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAL.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPOST search contact bv ohonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCS> FLOWS$ Connect Git @ Console 2 TerminCNeR-JHaMxlZoiNO.BodyJSONvPreview? Visualize"results":"name": "private-apos-api-calls-dailly""usagelimit": 1000000,"collectedAt": "2026-05-07T11:11:49.6772""2026-05-08T04:00:002"200 OK • 194 ms • 1.2 KB •C| .•=Q1O0Globals Vault Tools S000...
|
iTerm2
|
NULL
|
NULL
|
2346
|
|
2345
|
PostmanEditVIewWindowmelpHubSpot rate limit implem PostmanEditVIewWindowmelpHubSpot rate limit implementation strategy vUl is per-portal), and see the search secondly limit anywhere except your own tracking. Bothare wny the keais-dacked dasnboard is non-optional once you nave more than a nandarul orlenlanlls.lets focus only on hubspot api I can call vai postman. If I want to know specificportal what limits does it have.Catalogued HubSoot APl endooints for auerving portal rate limits ›There are essentially two endpoints plus response header inspection. That's the entire APIsurface for rate-limit discovery per portal.1. Daily limit + current daily usageGET https://api.hubapi. com/account-info/v3/api-usage/daily/private-appsAuthorization: Bearer {portal_access_token}Returns:"results": [{"name": "private-apps-api-calls-daily","usageLimit": 1000000,"currentusage": 47213"resetsAt" : "2026-05-08T05:00: 00z",IfotchStatucll, lcllceees"This is the only API that tells you the daily ceiling and current spend for a portal. Theendpoint name savs private-apps . which is what it's officially documented for — itaggregates all legacy private apps in that portal. If your portal is connected via OAuth (publicapp), this endpoint may return empty results or a different shape; test it on one of yourcustomer portals to see.Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..Write a message…Opus 4.7 AdaptiveClaude is Al and can make mistakes. Please double-check responses.Thu 7 May 14:12:04UparadeXx Hubspot vQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.GET read ciGET https://e•HTTP https:pi.hubapi.com/account-info/v3/api-usaqe/daily/private-appshttps://api.hubapi.com/account-info/v3/api-usage/daily/private-appsE DocsParamsAuthorization • Headers 9 Body Scripts SettinasAuth TypeTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorization.GET Get Eng((token))supoont Dally • In 40 mNo environmentv~ SaveCookies100% L2* AIVariables in requestG token> All variablesCOLLECTIONScontacts› CRM ObjectseRM owners› CRM Pipelines> Deals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPST search moditied companiePoSt search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET get subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGET https://hubspot-webhooks-iournal-na1.sGET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTG> SPFCS> FLOWS$ Connect Git @ Console 2 TerminCNeR-JHgMxIZQINQ…..BOdVJSONvPreviewe. Visualize"results":"name": "private-apos-api-calls-dailly""usagelimit": 1000000,"collectedAt": "2026-05-07T11:11:49.6772""2026-05-08T04:00:002"200 OK • 194 ms • 1.2 KB •C| .•=Q1O0Globals Vault Tools S000...
|
iTerm2
|
NULL
|
NULL
|
2345
|
|
2344
|
claudeVIeWWindowHelpHubSpot rate limit implementat claudeVIeWWindowHelpHubSpot rate limit implementation strategyUl is per-portal), and see the search secondly limit anywhere except your own tracking. Bothare wny the keais-dacked dasnboard is non-optional once you nave more than a nandrul orlenlanlls.lets focus only on hubspot api I can call vai postman. If I want to know specificportal what limits does it have.Catalogued HubSoot APl endooints for auerving portal rate limits ›There are essentially two endpoints plus response header inspection. That's the entire APIsurface for rate-limit discovery per portal.1. Daily limit + current daily usageGET https://api.hubapi. com/account-info/v3/api-usage/daily/private-appsAuthorization: Bearer {portal_access_token}Returns:"results": [{"name": "private-apps-api-calls-daily","usageLimit": 1000000,"currentusage": 47213"resetsAt" : "2026-05-08T05:00: 00z",IfotchStatucll, lcllceees"This is the only API that tells you the daily ceiling and current spend for a portal. Theendpoint name savs private-apps. which is what it's officially documented for — itaggregates all legacy private apps in that portal. If your portal is connected via OAuth (publicapp), this endpoint may return empty results or a different shape; test it on one of yourcustomer portals to see.Keep going in Claude CodeSwitch to Claude Code and let Claude work directiv in vour reno..Write a message…Opus 4.7 AdaptiveClaude is Al and can make mistakes. Please double-check responses.Q Searchn. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaborationGET Get EnaHTTP https:pi.hubapi.com/account-info/v3/api-usaqe/daily/private-appsE Docs ParamsAuth TypeBearer TokenGET Retrieve private app daily API usage • https://api.hubapi.com/account-info/2025-09/api-usage/daily/private-apps • HubSpot *GET Retrieve private apo daily APl usage • «baseUrl')/account-info/2026-03/api-usage/dailv/private-apos • HubSoot cGET Retrieve private app daily API usage • ({baseUrl))/account-info/2025-09/api-usage/daily/private-apps • HubSpot •The authorizationIgenerated when vGET Retrieve private app daily API usage • https://api.hubapi.com/account-info/2025-09/api-usage/daily/private-apps • HubSpot •more about Bearer Token authorization.Body Cookies 1 Headers 20 lest Results"JSONvPreview ?. Visualize v"results":"name". "private-aoos-aoi-calls-dail.v".lucadelimi+". 1000000"collectedAt": "2026-05-07T11:11:49.6772",*2026-05-08T04:00:002*hhlf Support Daily - in 48m100% C4)Thu 7 May 14:12:02No environmentv# SaveCookies* AIVariables in requestG token>All variablesCNeR-JHaMxlZoiNd.200 OK • 194 ms • 1.2 KB •a1 .•= =aID8Giobals Vault Tooks •- =...
|
iTerm2
|
NULL
|
NULL
|
2344
|
|
2343
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 48 m100% [Thu 7 May 14:12:03DEV (docker)T81DOCKERLast login: Thu MayDEV (docker)H82APP (-zsh)83-zsh• 84screenpipe*•$5-zsh₴67 09:44:56 on ttys006Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2343
|
|
2342
|
Skip to content
Skip to content
Click to collapse
Skip to content
Skip to content
Click to collapse
⌘B
Drag to resize
Open sidebar
Chat
Cowork
Code
New chat ⌘N
New chat
⌘N
Projects
Artifacts
Customize
Pinned
Bulgarian citizenship application process for EU residents
More options for Bulgarian citizenship application process for EU residents
Dawarich location tracking project
More options for Dawarich location tracking project
Recents
View all
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Screenpipe retention policy code location
More options for Screenpipe retention policy code location
Viewing retention policy in screenpipe
More options for Viewing retention policy in screenpipe
Clean shot x video recording termination issue
More options for Clean shot x video recording termination issue
HubSpot rate limit handling with executeRequest
More options for HubSpot rate limit handling with executeRequest
Untitled
More options
💬 Screen pipe. Is there ability…
More options for 💬 Screen pipe. Is there ability…
SMB mount access inconsistency between Finder and iTerm
More options for SMB mount access inconsistency between Finder and iTerm
💬 What is the best switch I can…
More options for 💬 What is the best switch I can…
Permission denied on screenpipe volume
More options for Permission denied on screenpipe volume
Screenpipe sync database attachment error
More options for Screenpipe sync database attachment error
Last swimming outing with Dani
More options for Last swimming outing with Dani
Definition of incarcerated
More options for Definition of incarcerated
Chromecast remote volume buttons not working
More options for Chromecast remote volume buttons not working
Salesforce API errors with Organization and FieldDefinition queries
More options for Salesforce API errors with Organization and FieldDefinition queries
Daily activity summary from screenpipe data
More options for Daily activity summary from screenpipe data
MacBook unexpected restarts and kanji screen
More options for MacBook unexpected restarts and kanji screen
Security patch review and testing guidance
More options for Security patch review and testing guidance
Food calorie values reference
More options for Food calorie values reference
Tracking location history from last week
More options for Tracking location history from last week
Lukas Pro
Get apps and extensions
HubSpot rate limit implementation strategy, rename chat
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Share chat
Claude finished the response
You said: So just a solution for rate limit implementation.
You said: So just a solution for rate limit implementation.
So just a solution for rate limit implementation. The situation currently is that there are some daily and secondary limits for HubSpot. I would like to make sure I never reach a 429 error rate limit. The requests can come from any flow. It can be:
updating activity (engagement, meeting, call, note)
searching for a company or contact
updating deal
patching IDs
Review what the limit is at the moment in the HubSpot documentation and then think of the solution:
where to store it
how to read it
how to work with multiple jobs
how to work with paginated requests Let's consider a situation when there are 600 opportunities to sync. What would be the flow? How would the rate limit be recognized? How would it be handled? What are the potential issues? [API usage guidelines and limits - HubSpot docs](
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
). Example of such a error Client error:
POST https://api.hubapi.com/crm/v3/objects/contact/search
resulted in a
429 Too Many Requests
response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT","correlationId":"019dffc4-4 (truncated...). Think carefully about the implementation and potential issue and bottlenecks.
Show more
10:42
Retry
Edit
Copy
Claude responded: Current HubSpot limits (Apr 2026)
Claude responded: Current HubSpot limits (Apr 2026)
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Current HubSpot limits (Apr 2026)
Current HubSpot limits (Apr 2026)
For privately distributed apps (which is what Jiminny presumably uses with HubSpot), the limits are layered: a per-app burst window of 100/10s on Free/Starter, 190/10s on Pro/Enterprise, or 250/10s with the API Limit Increase add-on
, plus a per-account daily cap of 250k / 625k / 1M depending on tier — shared across all private apps in the account
. The burst window is per app; the daily quota is per portal.
hubspot
hubspot
hubspot
hubspot
The Search API is special: five requests per second per account, capped at 200 records per page, with a hard 10,000-result ceiling per query
. That's the limit the 429 in your example is hitting (
secondly limit
on
/crm/v3/objects/contact/search
). It's a separate bucket from the 190/10s, and critically, search responses do not include the
X-HubSpot-RateLimit-*
headers
— you can't read remaining capacity off the response, you have to track it yourself.
hubspot
hubspot
hubspot
hubspot
Non-search endpoints return
X-HubSpot-RateLimit-Remaining
,
-Max
, and
-Interval-Milliseconds
. The daily headers are not returned for OAuth-authenticated calls
, so for those you check the account-info endpoint or maintain your own counter. There's also a soft rule: errors should stay under 5% of total daily requests
— that's enforced for marketplace listing, but it's also a sane operational target.
hubspot
hubspot
hubspot
hubspot
So you have
four buckets
to track at minimum: app-burst (10s sliding), search-secondly (1s sliding), account-daily (24h fixed, midnight in HubSpot's TZ), and per-app daily share (your own budgeting on top of the account cap).
Where to store it
Where to store it
Redis. It's the only realistic option once you have multiple queue workers — DB-backed counters serialize too much, and in-process state can't coordinate across workers. Laravel already speaks Redis natively, and you get atomic
INCR
/
EXPIRE
plus Lua scripting for true CAS semantics.
Key layout I'd use:
Copy to clipboard
hubspot:rl:burst:{portalId}:{appId} ZSET (sliding 10s)
hubspot:rl:search:{portalId} ZSET (sliding 1s)
hubspot:rl:daily:{portalId} STRING + TTL to midnight TZ
hubspot:rl:meta:{portalId} HASH (last seen headers)
The two short-window buckets are sliding-window-log (Redis ZSET, score =
microtime
, member = unique request id). Lua script removes entries older than the window, counts remaining slots, and only adds the new one if there's room — all atomic. Fixed windows are simpler but allow 2× the limit at the boundary, which on a 5/s window is brutal.
The daily bucket is a plain
INCR
with TTL set to seconds-until-midnight in
HubSpot's account timezone
, not yours — Sofia is UTC+2/+3 but your portal might be set to US Eastern. Get this once and cache it.
How to read it
How to read it
Two-phase: optimistic pre-check, authoritative post-update.
Before a call, run the Lua acquire script. If it returns "denied," sleep until a slot frees up (the script can return ms-until-next-slot) or push the job back to the queue with a delay. Don't busy-loop.
After the call, parse
X-HubSpot-RateLimit-Remaining
/
-Max
/
-Interval-Milliseconds
and store them in
hubspot:rl:meta:{portalId}
. This is your reality check — if your local counter says 50 remaining but HubSpot's header says 5, you trust HubSpot and clamp your counter. This handles clock drift, missed accounting (e.g., crashed worker that took a token but never made the request), and other apps in the same account consuming the daily budget invisibly.
For search specifically, since headers don't come back, the local counter
is
the source of truth — meaning if you ever crash mid-flight, you've under-counted. Always release tokens on connection-level failure but
not
on 429 (you really did make that request).
How to work with multiple jobs
How to work with multiple jobs
The queue layer needs to enforce concurrency separately from the rate limiter. Both work together:
Concurrency cap
via
Queue::throttle()
or a Redis semaphore — limits how many sync workers run in parallel against HubSpot. Without this, you can have 50 workers all blocked waiting for tokens, which is wasteful and creates retry storms.
Per-tenant fairness
— if you sync many Jiminny customers into different HubSpot portals, each portal has its own bucket but you still want one slow portal not to starve others. Either separate queues per portal or a fair-share scheduler.
Priority lanes
— webhook-driven updates (user-visible latency) should outrank background batch syncs. Two queues:
hubspot-priority
and
hubspot-bulk
, with priority workers taking 70% of the burst budget and bulk taking 30% (enforce via separate sub-buckets if you really want hard separation, otherwise just pull from priority first).
Backoff on 429
— respect the
Retry-After
header. If absent, exponential with jitter (e.g.,
min(2^attempt * 250ms, 30s) ± 20%
). The jitter is non-negotiable; without it, simultaneous 429s retry in lockstep and you get thundering-herd 429s on retry.
How to work with paginated requests
How to work with paginated requests
The trap is treating "fetch all" as one logical operation. Each page is its own API call and competes for tokens with everything else.
Two practical rules:
Don't hold the worker idle while paginating.
If page N takes 500ms and page N+1 needs to wait 800ms for a token, you've burned 800ms of worker time doing nothing. Instead, fetch page N, dispatch the
processing
of page N as a separate job, and queue a "fetch page N+1" job with a delay equal to the wait time. Each page becomes its own atomic unit.
Always batch where HubSpot offers it.
POST /crm/v3/objects/{type}/batch/{read|update|create}
accepts up to 100 IDs per call. For your "patching IDs" flow this is the difference between 600 calls and 6.
Walkthrough: 600 opportunities
Walkthrough: 600 opportunities
Naive flow (one PATCH per deal): 600 calls. At 190/10s that's ~32s of API time, well under daily. You'd hit burst easily without throttling. Plus likely 1-3 search calls upfront and N association calls.
Sane flow:
Identify deltas
— if you can avoid Search at all, do. Use
lastmodifieddate
filter on a single search if you must, paginate at limit=200. For 600 deals that's 3 search calls @ 5/s = ~600ms naturally throttled.
Batch read
current state —
POST /crm/v3/objects/deals/batch/read
with 100 IDs per call → 6 calls. Burst weight 6.
Compute diff
in your code (no API).
Batch update
—
POST /crm/v3/objects/deals/batch/update
with 100 per call → 6 calls.
Associations
—
POST /crm/v4/associations/{from}/{to}/batch/create
if needed → another few batch calls.
Total: ~15-20 API calls for 600 deals. Burst budget consumed: 20/190 over ~5s. Daily impact: trivial.
Recognition: pre-check denies if
<weight>
slots aren't free; on 429 the response surfaces
policyName
(DAILY/SECONDLY) — log it, push the job back with
Retry-After
delay, increment a metric so you can alarm on sustained 429 rate.
Pitfalls & bottlenecks worth pre-empting
Pitfalls & bottlenecks worth pre-empting
Daily quota is shared across the whole portal
, including any n8n flows, other private apps, marketing automation calling APIs, etc. Budget for ~70-80% of the documented limit, not 100%. Add an internal per-app daily cap so a runaway sync can't starve other apps.
Search is uniquely fragile
: separate 5/s bucket, no headers to read, 10k-result cap per query. If you ever hit 10k+ deals matching a filter, partition by
hs_object_id
ranges or by
lastmodifieddate
windows.
Retry storms after HubSpot incidents
— always jitter, always cap total retries (e.g., 5 attempts, then dead-letter).
Webhook → sync → webhook loops
— when your update fires a HubSpot webhook that triggers another sync. Tag your own writes (e.g., a custom property
jy_last_sync_id
) and ignore webhooks where it just changed.
Token refresh
— OAuth refresh itself counts against burst. Cache the access token in Redis with TTL =
expires_in - 60s
, single-flight the refresh (only one worker refreshes; others wait on a lock).
Search latency for fresh writes
— newly created/updated objects don't appear in search instantly. Don't write-then-search; use returned IDs directly.
Clock skew
— Redis is authoritative. Don't use
time()
from each worker for window scoring; use
redis.call('TIME')
inside the Lua script.
Dead workers with held tokens
— sliding-window-log handles this naturally because tokens expire by score; token-bucket implementations need explicit release-on-crash logic.
The 5% error rule
counts every 429 toward your error budget, even successfully retried ones. If your pre-check is working well, 429s should be near zero — if they're not, your pre-check is wrong, not just slow.
Phantom contention with Laravel
RateLimited
middleware
: it's per-job-class by default, not per-portal. If your
SyncDealJob
and
UpdateActivityJob
are different classes both calling HubSpot, they don't share a Laravel-level limiter — you need a single
HubspotRateLimiter
service that everything routes through.
If you want, I can sketch the Lua script for the sliding-window acquire and the Laravel service wrapper around it.
Copy
Give positive feedback
Give negative feedback
Retry
You said: What will happen if there are two different types of rate limits?
You said: What will happen if there are two different types of rate limits?
What will happen if there are two different types of rate limits?
Search requests that have 5 requests per second
The other rate limit that has, let's say, 100 requests per 10 seconds How do these work together? Is there some conflict? Can I reach the limit with one request and block either as well, or are these separated? Can I still continue making search requests once I hit the normal requests limits?
13:40
Retry
Edit
Copy
Claude responded: They're independent buckets — with one shared bucket on top.
Claude responded: They're independent buckets — with one shared bucket on top.
Analyzed independent rate limit buckets and their practical interactions
Analyzed independent rate limit buckets and their practical interactions
They're independent buckets — with one shared bucket on top.
The three buckets and what each call hits
The three buckets and what each call hits
Copy to clipboard
┌──────────────────┐
Search request ──→ │ Search: 5/sec │ ──┐
└──────────────────┘ │
├──→ ┌─────────────────┐
┌──────────────────┐ │ │ Daily: 250k–1M │
Non-search call ──→ │ Burst: 190/10s │ ──┘ │ (per portal) │
└──────────────────┘ └─────────────────┘
A search call is only metered against the search bucket and the daily bucket. A non-search call (batch read/update, single PATCH, associations, etc.) is only metered against the burst bucket and the daily bucket. The two short-window buckets do not share counters.
What this means practically
What this means practically
Hitting search secondly limit (5/s):
Only further
/search
calls 429. Your batch reads, batch updates, single PATCHes, association calls — all keep working at full burst speed. This is actually useful: if your sync is bottlenecked on Search, you can pivot to using
lastmodifieddate
filters via batch endpoints, or use the IDs you already have to do batch reads, while Search cools off.
Hitting burst limit (190/10s):
Only non-search calls 429. You can still issue Search calls at 5/s. Useful for: continuing to identify deltas for queueing while in-flight updates drain, or refreshing a small set of records via Search even though your write pipeline is paused.
Hitting daily limit:
Everything stops. Search and non-search alike. Doesn't unblock until midnight in your portal's configured timezone — and remember this is shared across every private app in the portal, plus n8n flows, marketing tools, anything else hitting the API with that account.
So can one type of request block the other?
So can one type of request block the other?
Search → Burst:
No.
Saturating Search at 50 calls per 10s leaves your full 190/10s burst untouched.
Burst → Search:
No.
Saturating burst leaves Search's 5/s untouched.
Either → Daily:
Yes
, but only by contributing to the same daily counter. It's volume that kills you here, not the type.
In theory you can sustain ~50 search + ~190 other =
~240 calls per 10 seconds
indefinitely (until daily runs out), because the two buckets bill independently.
Implementation consequence
Implementation consequence
Your rate limiter needs to know which bucket a request hits before it acquires. Cleanest pattern:
Copy to clipboard
php
$limiter
->
acquire
(
'search'
,
$weight
=
1
)
;
// for search endpoints only
$limiter
->
acquire
(
'burst'
,
$weight
=
1
)
;
// for everything else
$limiter
->
acquire
(
'daily'
,
$weight
=
1
)
;
// every call, both kinds
In Redis: three separate keys, three separate Lua acquire scripts (or one script with a bucket parameter). A search call calls
acquire('search')
+
acquire('daily')
. A batch update calls
acquire('burst')
+
acquire('daily')
.
One subtle pitfall: when you backoff on a 429,
inspect
policyName
in the response body
to know which bucket actually fired. If you see
SECONDLY
from a search endpoint, you only need to delay search-bound jobs — burst-bound jobs in the queue can keep running. If you blanket-pause everything on any 429, you waste capacity on the bucket that's still healthy. Two queues (or two throttle keys) make this clean; one global pause is the lazy version.
The other subtlety: the burst response gives you
X-HubSpot-RateLimit-Remaining
to clamp local state against, but search doesn't return those headers. So your search counter is unverified — be slightly more conservative there (e.g., budget 4/s instead of 5) to absorb the unaccounted-for calls.
Copy
Give positive feedback
Give negative feedback
Retry
You said: Ok, so what will happen each time I make a request?
You said: Ok, so what will happen each time I make a request?
Ok, so what will happen each time I make a request? Let's say I have 100,000 requests to make that are instant. Do I need to increment each request based on the type? For example, if there is a search request, I need to increment both the search bucket and also the daily bucket. If it's a burst, then I can go to the daily and burst buckets. If I need to check if it can make a call, do I need to see both the daily and search, or burst, respectively? Isn't that too heavy for the infrastructure, adding additional load to each request?
13:44
Retry
Edit
Copy
Claude responded: Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out.
Claude responded: Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out.
Analyzed per-request overhead concerns and quantified Redis performance impact
Analyzed per-request overhead concerns and quantified Redis performance impact
Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out. But the overhead is much smaller than it sounds, and importantly, it's nowhere near your bottleneck.
What "two buckets per request" actually costs
What "two buckets per request" actually costs
Each request makes
one round trip to Redis
— not two — because you fold both bucket checks into a single Lua script that runs atomically server-side:
Copy to clipboard
lua
-- KEYS[1] = burst bucket key (or search)
-- KEYS[2] = daily bucket key
-- ARGV[1] = now (ms) ARGV[2] = window_ms
-- ARGV[3] = bucket_max ARGV[4] = daily_max
-- ARGV[5] = request_id ARGV[6] = daily_ttl
-- Trim sliding window
redis
.
call
(
'ZREMRANGEBYSCORE'
,
KEYS
[
1
]
,
0
,
ARGV
[
1
]
-
ARGV
[
2
]
)
local
burst_used
=
redis
.
call
(
'ZCARD'
,
KEYS
[
1
]
)
local
daily_used
=
tonumber
(
redis
.
call
(
'GET'
,
KEYS
[
2
]
)
or
'0'
)
if
burst_used
>=
tonumber
(
ARGV
[
3
]
)
then
-- Tell caller how long to sleep until oldest entry expires
local
oldest
=
redis
.
call
(
'ZRANGE'
,
KEYS
[
1
]
,
0
,
0
,
'WITHSCORES'
)
return
{
0
,
'BURST'
,
(
oldest...
|
Claude
|
Claude
|
NULL
|
2342
|
|
2341
|
Skip to content
Skip to content
Click to collapse
Skip to content
Skip to content
Click to collapse
⌘B
Drag to resize
Open sidebar
Chat
Cowork
Code
New chat ⌘N
New chat
⌘N
Projects
Artifacts
Customize
Pinned
Bulgarian citizenship application process for EU residents
More options for Bulgarian citizenship application process for EU residents
Dawarich location tracking project
More options for Dawarich location tracking project
Recents
View all
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Screenpipe retention policy code location
More options for Screenpipe retention policy code location
Viewing retention policy in screenpipe
More options for Viewing retention policy in screenpipe
Clean shot x video recording termination issue
More options for Clean shot x video recording termination issue
HubSpot rate limit handling with executeRequest
More options for HubSpot rate limit handling with executeRequest
Untitled
More options
💬 Screen pipe. Is there ability…
More options for 💬 Screen pipe. Is there ability…
SMB mount access inconsistency between Finder and iTerm
More options for SMB mount access inconsistency between Finder and iTerm
💬 What is the best switch I can…
More options for 💬 What is the best switch I can…
Permission denied on screenpipe volume
More options for Permission denied on screenpipe volume
Screenpipe sync database attachment error
More options for Screenpipe sync database attachment error
Last swimming outing with Dani
More options for Last swimming outing with Dani
Definition of incarcerated
More options for Definition of incarcerated
Chromecast remote volume buttons not working
More options for Chromecast remote volume buttons not working
Salesforce API errors with Organization and FieldDefinition queries
More options for Salesforce API errors with Organization and FieldDefinition queries
Daily activity summary from screenpipe data
More options for Daily activity summary from screenpipe data
MacBook unexpected restarts and kanji screen
More options for MacBook unexpected restarts and kanji screen
Security patch review and testing guidance
More options for Security patch review and testing guidance
Food calorie values reference
More options for Food calorie values reference
Tracking location history from last week
More options for Tracking location history from last week
Lukas Pro
Get apps and extensions
HubSpot rate limit implementation strategy, rename chat
HubSpot rate limit implementation strategy
More options for HubSpot rate limit implementation strategy
Share chat
Claude finished the response
You said: So just a solution for rate limit implementation.
You said: So just a solution for rate limit implementation.
So just a solution for rate limit implementation. The situation currently is that there are some daily and secondary limits for HubSpot. I would like to make sure I never reach a 429 error rate limit. The requests can come from any flow. It can be:
updating activity (engagement, meeting, call, note)
searching for a company or contact
updating deal
patching IDs
Review what the limit is at the moment in the HubSpot documentation and then think of the solution:
where to store it
how to read it
how to work with multiple jobs
how to work with paginated requests Let's consider a situation when there are 600 opportunities to sync. What would be the flow? How would the rate limit be recognized? How would it be handled? What are the potential issues? [API usage guidelines and limits - HubSpot docs](
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
). Example of such a error Client error:
POST https://api.hubapi.com/crm/v3/objects/contact/search
resulted in a
429 Too Many Requests
response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT","correlationId":"019dffc4-4 (truncated...). Think carefully about the implementation and potential issue and bottlenecks.
Show more
10:42
Retry
Edit
Copy
Claude responded: Current HubSpot limits (Apr 2026)
Claude responded: Current HubSpot limits (Apr 2026)
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Synthesized HubSpot rate limit architecture with Redis storage and sliding window algorithms
Current HubSpot limits (Apr 2026)
Current HubSpot limits (Apr 2026)
For privately distributed apps (which is what Jiminny presumably uses with HubSpot), the limits are layered: a per-app burst window of 100/10s on Free/Starter, 190/10s on Pro/Enterprise, or 250/10s with the API Limit Increase add-on
, plus a per-account daily cap of 250k / 625k / 1M depending on tier — shared across all private apps in the account
. The burst window is per app; the daily quota is per portal.
hubspot
hubspot
hubspot
hubspot
The Search API is special: five requests per second per account, capped at 200 records per page, with a hard 10,000-result ceiling per query
. That's the limit the 429 in your example is hitting (
secondly limit
on
/crm/v3/objects/contact/search
). It's a separate bucket from the 190/10s, and critically, search responses do not include the
X-HubSpot-RateLimit-*
headers
— you can't read remaining capacity off the response, you have to track it yourself.
hubspot
hubspot
hubspot
hubspot
Non-search endpoints return
X-HubSpot-RateLimit-Remaining
,
-Max
, and
-Interval-Milliseconds
. The daily headers are not returned for OAuth-authenticated calls
, so for those you check the account-info endpoint or maintain your own counter. There's also a soft rule: errors should stay under 5% of total daily requests
— that's enforced for marketplace listing, but it's also a sane operational target.
hubspot
hubspot
hubspot
hubspot
So you have
four buckets
to track at minimum: app-burst (10s sliding), search-secondly (1s sliding), account-daily (24h fixed, midnight in HubSpot's TZ), and per-app daily share (your own budgeting on top of the account cap).
Where to store it
Where to store it
Redis. It's the only realistic option once you have multiple queue workers — DB-backed counters serialize too much, and in-process state can't coordinate across workers. Laravel already speaks Redis natively, and you get atomic
INCR
/
EXPIRE
plus Lua scripting for true CAS semantics.
Key layout I'd use:
Copy to clipboard
hubspot:rl:burst:{portalId}:{appId} ZSET (sliding 10s)
hubspot:rl:search:{portalId} ZSET (sliding 1s)
hubspot:rl:daily:{portalId} STRING + TTL to midnight TZ
hubspot:rl:meta:{portalId} HASH (last seen headers)
The two short-window buckets are sliding-window-log (Redis ZSET, score =
microtime
, member = unique request id). Lua script removes entries older than the window, counts remaining slots, and only adds the new one if there's room — all atomic. Fixed windows are simpler but allow 2× the limit at the boundary, which on a 5/s window is brutal.
The daily bucket is a plain
INCR
with TTL set to seconds-until-midnight in
HubSpot's account timezone
, not yours — Sofia is UTC+2/+3 but your portal might be set to US Eastern. Get this once and cache it.
How to read it
How to read it
Two-phase: optimistic pre-check, authoritative post-update.
Before a call, run the Lua acquire script. If it returns "denied," sleep until a slot frees up (the script can return ms-until-next-slot) or push the job back to the queue with a delay. Don't busy-loop.
After the call, parse
X-HubSpot-RateLimit-Remaining
/
-Max
/
-Interval-Milliseconds
and store them in
hubspot:rl:meta:{portalId}
. This is your reality check — if your local counter says 50 remaining but HubSpot's header says 5, you trust HubSpot and clamp your counter. This handles clock drift, missed accounting (e.g., crashed worker that took a token but never made the request), and other apps in the same account consuming the daily budget invisibly.
For search specifically, since headers don't come back, the local counter
is
the source of truth — meaning if you ever crash mid-flight, you've under-counted. Always release tokens on connection-level failure but
not
on 429 (you really did make that request).
How to work with multiple jobs
How to work with multiple jobs
The queue layer needs to enforce concurrency separately from the rate limiter. Both work together:
Concurrency cap
via
Queue::throttle()
or a Redis semaphore — limits how many sync workers run in parallel against HubSpot. Without this, you can have 50 workers all blocked waiting for tokens, which is wasteful and creates retry storms.
Per-tenant fairness
— if you sync many Jiminny customers into different HubSpot portals, each portal has its own bucket but you still want one slow portal not to starve others. Either separate queues per portal or a fair-share scheduler.
Priority lanes
— webhook-driven updates (user-visible latency) should outrank background batch syncs. Two queues:
hubspot-priority
and
hubspot-bulk
, with priority workers taking 70% of the burst budget and bulk taking 30% (enforce via separate sub-buckets if you really want hard separation, otherwise just pull from priority first).
Backoff on 429
— respect the
Retry-After
header. If absent, exponential with jitter (e.g.,
min(2^attempt * 250ms, 30s) ± 20%
). The jitter is non-negotiable; without it, simultaneous 429s retry in lockstep and you get thundering-herd 429s on retry.
How to work with paginated requests
How to work with paginated requests
The trap is treating "fetch all" as one logical operation. Each page is its own API call and competes for tokens with everything else.
Two practical rules:
Don't hold the worker idle while paginating.
If page N takes 500ms and page N+1 needs to wait 800ms for a token, you've burned 800ms of worker time doing nothing. Instead, fetch page N, dispatch the
processing
of page N as a separate job, and queue a "fetch page N+1" job with a delay equal to the wait time. Each page becomes its own atomic unit.
Always batch where HubSpot offers it.
POST /crm/v3/objects/{type}/batch/{read|update|create}
accepts up to 100 IDs per call. For your "patching IDs" flow this is the difference between 600 calls and 6.
Walkthrough: 600 opportunities
Walkthrough: 600 opportunities
Naive flow (one PATCH per deal): 600 calls. At 190/10s that's ~32s of API time, well under daily. You'd hit burst easily without throttling. Plus likely 1-3 search calls upfront and N association calls.
Sane flow:
Identify deltas
— if you can avoid Search at all, do. Use
lastmodifieddate
filter on a single search if you must, paginate at limit=200. For 600 deals that's 3 search calls @ 5/s = ~600ms naturally throttled.
Batch read
current state —
POST /crm/v3/objects/deals/batch/read
with 100 IDs per call → 6 calls. Burst weight 6.
Compute diff
in your code (no API).
Batch update
—
POST /crm/v3/objects/deals/batch/update
with 100 per call → 6 calls.
Associations
—
POST /crm/v4/associations/{from}/{to}/batch/create
if needed → another few batch calls.
Total: ~15-20 API calls for 600 deals. Burst budget consumed: 20/190 over ~5s. Daily impact: trivial.
Recognition: pre-check denies if
<weight>
slots aren't free; on 429 the response surfaces
policyName
(DAILY/SECONDLY) — log it, push the job back with
Retry-After
delay, increment a metric so you can alarm on sustained 429 rate.
Pitfalls & bottlenecks worth pre-empting
Pitfalls & bottlenecks worth pre-empting
Daily quota is shared across the whole portal
, including any n8n flows, other private apps, marketing automation calling APIs, etc. Budget for ~70-80% of the documented limit, not 100%. Add an internal per-app daily cap so a runaway sync can't starve other apps.
Search is uniquely fragile
: separate 5/s bucket, no headers to read, 10k-result cap per query. If you ever hit 10k+ deals matching a filter, partition by
hs_object_id
ranges or by
lastmodifieddate
windows.
Retry storms after HubSpot incidents
— always jitter, always cap total retries (e.g., 5 attempts, then dead-letter).
Webhook → sync → webhook loops
— when your update fires a HubSpot webhook that triggers another sync. Tag your own writes (e.g., a custom property
jy_last_sync_id
) and ignore webhooks where it just changed.
Token refresh
— OAuth refresh itself counts against burst. Cache the access token in Redis with TTL =
expires_in - 60s
, single-flight the refresh (only one worker refreshes; others wait on a lock).
Search latency for fresh writes
— newly created/updated objects don't appear in search instantly. Don't write-then-search; use returned IDs directly.
Clock skew
— Redis is authoritative. Don't use
time()
from each worker for window scoring; use
redis.call('TIME')
inside the Lua script.
Dead workers with held tokens
— sliding-window-log handles this naturally because tokens expire by score; token-bucket implementations need explicit release-on-crash logic.
The 5% error rule
counts every 429 toward your error budget, even successfully retried ones. If your pre-check is working well, 429s should be near zero — if they're not, your pre-check is wrong, not just slow.
Phantom contention with Laravel
RateLimited
middleware
: it's per-job-class by default, not per-portal. If your
SyncDealJob
and
UpdateActivityJob
are different classes both calling HubSpot, they don't share a Laravel-level limiter — you need a single
HubspotRateLimiter
service that everything routes through.
If you want, I can sketch the Lua script for the sliding-window acquire and the Laravel service wrapper around it.
Copy
Give positive feedback
Give negative feedback
Retry
You said: What will happen if there are two different types of rate limits?
You said: What will happen if there are two different types of rate limits?
What will happen if there are two different types of rate limits?
Search requests that have 5 requests per second
The other rate limit that has, let's say, 100 requests per 10 seconds How do these work together? Is there some conflict? Can I reach the limit with one request and block either as well, or are these separated? Can I still continue making search requests once I hit the normal requests limits?
13:40
Retry
Edit
Copy
Claude responded: They're independent buckets — with one shared bucket on top.
Claude responded: They're independent buckets — with one shared bucket on top.
Analyzed independent rate limit buckets and their practical interactions
Analyzed independent rate limit buckets and their practical interactions
They're independent buckets — with one shared bucket on top.
The three buckets and what each call hits
The three buckets and what each call hits
Copy to clipboard
┌──────────────────┐
Search request ──→ │ Search: 5/sec │ ──┐
└──────────────────┘ │
├──→ ┌─────────────────┐
┌──────────────────┐ │ │ Daily: 250k–1M │
Non-search call ──→ │ Burst: 190/10s │ ──┘ │ (per portal) │
└──────────────────┘ └─────────────────┘
A search call is only metered against the search bucket and the daily bucket. A non-search call (batch read/update, single PATCH, associations, etc.) is only metered against the burst bucket and the daily bucket. The two short-window buckets do not share counters.
What this means practically
What this means practically
Hitting search secondly limit (5/s):
Only further
/search
calls 429. Your batch reads, batch updates, single PATCHes, association calls — all keep working at full burst speed. This is actually useful: if your sync is bottlenecked on Search, you can pivot to using
lastmodifieddate
filters via batch endpoints, or use the IDs you already have to do batch reads, while Search cools off.
Hitting burst limit (190/10s):
Only non-search calls 429. You can still issue Search calls at 5/s. Useful for: continuing to identify deltas for queueing while in-flight updates drain, or refreshing a small set of records via Search even though your write pipeline is paused.
Hitting daily limit:
Everything stops. Search and non-search alike. Doesn't unblock until midnight in your portal's configured timezone — and remember this is shared across every private app in the portal, plus n8n flows, marketing tools, anything else hitting the API with that account.
So can one type of request block the other?
So can one type of request block the other?
Search → Burst:
No.
Saturating Search at 50 calls per 10s leaves your full 190/10s burst untouched.
Burst → Search:
No.
Saturating burst leaves Search's 5/s untouched.
Either → Daily:
Yes
, but only by contributing to the same daily counter. It's volume that kills you here, not the type.
In theory you can sustain ~50 search + ~190 other =
~240 calls per 10 seconds
indefinitely (until daily runs out), because the two buckets bill independently.
Implementation consequence
Implementation consequence
Your rate limiter needs to know which bucket a request hits before it acquires. Cleanest pattern:
Copy to clipboard
php
$limiter
->
acquire
(
'search'
,
$weight
=
1
)
;
// for search endpoints only
$limiter
->
acquire
(
'burst'
,
$weight
=
1
)
;
// for everything else
$limiter
->
acquire
(
'daily'
,
$weight
=
1
)
;
// every call, both kinds
In Redis: three separate keys, three separate Lua acquire scripts (or one script with a bucket parameter). A search call calls
acquire('search')
+
acquire('daily')
. A batch update calls
acquire('burst')
+
acquire('daily')
.
One subtle pitfall: when you backoff on a 429,
inspect
policyName
in the response body
to know which bucket actually fired. If you see
SECONDLY
from a search endpoint, you only need to delay search-bound jobs — burst-bound jobs in the queue can keep running. If you blanket-pause everything on any 429, you waste capacity on the bucket that's still healthy. Two queues (or two throttle keys) make this clean; one global pause is the lazy version.
The other subtlety: the burst response gives you
X-HubSpot-RateLimit-Remaining
to clamp local state against, but search doesn't return those headers. So your search counter is unverified — be slightly more conservative there (e.g., budget 4/s instead of 5) to absorb the unaccounted-for calls.
Copy
Give positive feedback
Give negative feedback
Retry
You said: Ok, so what will happen each time I make a request?
You said: Ok, so what will happen each time I make a request?
Ok, so what will happen each time I make a request? Let's say I have 100,000 requests to make that are instant. Do I need to increment each request based on the type? For example, if there is a search request, I need to increment both the search bucket and also the daily bucket. If it's a burst, then I can go to the daily and burst buckets. If I need to check if it can make a call, do I need to see both the daily and search, or burst, respectively? Isn't that too heavy for the infrastructure, adding additional load to each request?
13:44
Retry
Edit
Copy
Claude responded: Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out.
Claude responded: Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out.
Analyzed per-request overhead concerns and quantified Redis performance impact
Analyzed per-request overhead concerns and quantified Redis performance impact
Yes, your understanding is correct — every request must check and reserve from each bucket it applies to, atomically, before the call goes out. But the overhead is much smaller than it sounds, and importantly, it's nowhere near your bottleneck.
What "two buckets per request" actually costs
What "two buckets per request" actually costs
Each request makes
one round trip to Redis
— not two — because you fold both bucket checks into a single Lua script that runs atomically server-side:
Copy to clipboard
lua
-- KEYS[1] = burst bucket key (or search)
-- KEYS[2] = daily bucket key
-- ARGV[1] = now (ms) ARGV[2] = window_ms
-- ARGV[3] = bucket_max ARGV[4] = daily_max
-- ARGV[5] = request_id ARGV[6] = daily_ttl
-- Trim sliding window
redis
.
call
(
'ZREMRANGEBYSCORE'
,
KEYS
[
1
]
,
0
,
ARGV
[
1
]
-
ARGV
[
2
]
)
local
burst_used
=
redis
.
call
(
'ZCARD'
,
KEYS
[
1
]
)
local
daily_used
=
tonumber
(
redis
.
call
(
'GET'
,
KEYS
[
2
]
)
or
'0'
)
if
burst_used
>=
tonumber
(
ARGV
[
3
]
)
then
-- Tell caller how long to sleep until oldest entry expires
local
oldest
=
redis
.
call
(
'ZRANGE'
,
KEYS
[
1
]
,
0
,
0
,
'WITHSCORES'
)
return
{
0
,
'BURST'
,
(
oldest
[
2
]
+
ARGV
[
2
]
)
-
ARGV
[
1
]
}
end
if
daily_used
>=
tonumber
(
ARGV
[
4
]
)
then
return
{
0
,
'DAILY'
,
-
1
}
end...
|
Claude
|
Claude
|
NULL
|
2341
|
|
2340
|
rostmancaltvlewWindowmelpProject© RingCentral/Clie rostmancaltvlewWindowmelpProject© RingCentral/Client.phpA EU [EU]v A jiminny@localhost& console uiminny clocainosADI [jiminny@localhost4 HS Jocal ljiminny@localhosA SF jiminny@localhost]A zoho_dev (jiminny@localhoV A PROD& console ProDIRematchActivityOnCrmObjectDetach.php# DeleteCrmEntity Trait.php© RateLimitException.phpMiddleware/RateLimited.pnpC) ProviderRateLimiter.pho Xclass ProviderRateLimiterpublic function canMakeRequest(RateLimited $provider): bool& console 1 PROD< DI PROD> AOAA QAI> 4 QAI PRODLSTAGING/** @var RateLimitInterface $rateLimit */foreach (Sprovider->getRateLimits() as SrateLimit) {$key = $rateLimit->getKeyO);if ($this-›rateLimiter->tooManyAttempts($key, $rateLimit->getQuota())) €return false;& console STAGING& console STAGiNgduranus STAGINGI> Fxtansinnsservicesv D DatabaseV AEUconsole& |iminny@localhost4 HS_JocalA SF~ A PRODconsole 1s 381 msV A STAGINGA console 1s 250 ms…DockenPlatform Sprint 3 Q2© SyncToUsSevenShores|Hubsp.$ Service-Desk - Queue• Jy 20807 check varioA Sentry••Pull requests • jiminnyU Useroilot I Ask Jimin@Jy-20773 fix user piloJiminnyNew TabXx Hubspot vQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.GET next off. • POST search •HTTP https:pi.hubapi.com/account-info/v3/api-usaqe/daily/private-appshttps://api.hubapi.com/account-info/v3/api-usage/daily/private-appsE DocsParamsAuth TypeBearer TokenAuthorization • Headers 9 Body Scripts SettinasTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorization.((token))40hhlGET https://e•supoont Dally • In45 m100% L2No environmentvg Save* AIVariables in requestCookiesAll variablesThu 7 May 14:11:52h OutoutW 1rowv1i timinnv.social accounts XIX: Auto vRQGA®Did! sociable_idprovider_user_idprovider_user_tokenI provider_refresh_tokenMexnires149914827225182CNeR-JHgMxIZQLNQML8kQEwrAgwACAKUAhIJBB4BAQEDBxi(d5ab04e2-2109-4c0b-b513-8cba1dd543711778154080I refresh_token_expiresO providerhubspotI stateconnectedID auth_scope<null>retry_after<null>created_at2026-01-16 07-30-47I updated_at2026-05-07 11:11:20provider_user_token_encryptedeyJpdiI6Ik1PcXNtZ3R6TzFWMUVEMHBLb2U1Umc9PSIsInZtprovider_refresh_token_encryptedd5ab04e2-2109-4c0b-b513-8cba1dd54371I encryption_key (Hex)0x01020300784A7E08630802C9456B8B85CC5951D489859CCOLLECTIONScontacts› CRM ObjectseRM owners› CRM PipelinesDeals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPST search moditied companiePoSt search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET get subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGET https://hubspot-webhooks-iournal-na1.sGET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCS>FLOWS$ Connect Git @ Console TermirCNeR-JHaMxlZoiNd.BOdVCookiesJSONvPreviewe. Visualize"results":"name": "private-aops-aoi-calls-dail.v"."ucadel imi+". 1000000"collectedAt": "2026-05-07T11:11:49.6772""2026-05-08T04:00:002"200 OK • 194 ms • 1.2 KB • C| ...=a1D0Globals Vault Tools?000...
|
iTerm2
|
NULL
|
NULL
|
2340
|
|
2339
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 49 m100% [Thu 7 May 14:11:52DEV (docker)181DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)83-zsh• 84screenpipe*•$5-zsh₴6Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2339
|
|
2338
|
rostmancaltvlewWindowmelpProject© RingCentral/Clie rostmancaltvlewWindowmelpProject© RingCentral/Client.phpA EU [EU]v A jiminny@localhost& console uiminny clocainosADI [jiminny@localhost4 HS Jocal ljiminny@localhosA SF jiminny@localhost]A zoho_dev (jiminny@localhoV A PROD& console PrODIRematchActivityOnCrmObjectDetach.php# DeleteCrmEntity Trait.php© RateLimitException.phpMiddleware/RateLimited.pnpC) ProviderRateLimiter.pho Xclass ProviderRateLimitenpublic function canMakeRequest(RateLimited $provider): bool& console 1 PROD< DI PROD> AOAA QAI> 4 QAI PRODLSTAGING/** @var RateLimitInterface $rateLimit */foreach (Sprovider->getRateLimits() as SrateLimit) {$key = $rateLimit->getKeyO);if ($this-›rateLimiter->tooManyAttempts($key, $rateLimit->getQuota())) €return false;& console STAGING& console STAGINGduranus STAGINGI> Fxtansinnsservicesv D DatabaseV AEUconsole& |iminny@localhost4 HS_JocalA SF~ A PRODconsole 1s 381 msV A STAGINGA console 1s 250 ms…DockenPlatform Sprint 3 Q2© SyncToUsSevenShores|Hubsp.$ Service-Desk - Queue• Jy 20807 check varioA Sentry••Pull requests • jiminnyU Useroilot I Ask Jimin@Jy-20773 fix user piloaJiminnuNew TabhhlQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.GET next off. • POST search •HTTP https:pi.hubapi.com/account-info/v3/api-usaqe/daily/private-appshttps://api.hubapi.com/account-info/v3/api-usage/daily/private-appsE DocsAuth TypeBearer TokenAuthorization • Headers 9 Body Scripts SettinasTokenThe authorization header will be automaticallygenerated when you send the reauest. Learnmore about Bearer Token authorizationGET https://e•((token))supoont Dally • In45 m100% L2No environmentv~ SaveVariables in requestG tokenSendsw cookies> All variablesThu 7 May 14:11:48h OutoutW 1rowvii timinnv.socialaccounts XIX: Auto vFQGA®Did! sociable_idprovider_user_idprovider_user_tokenI provider_refresh_tokenMexnires149914827225182CNeR-JHgMxIZQLNQML8kQEwrAgwACAKUAhIJBB4BAQEDBxi(d5ab04e2-2109-4c0b-b513-8cba1dd543711778154080I refresh_token_expiresO providerhubspotI stateconnectedID auth_scope<nUll>retry_after<null>created_at2026-01-16 07-30-47I updated_at2026-05-07 11:11:20provider_user_token_encryptedeyJpdiI6Ik1PcXNtZ3R6TzFWMUVEMHBLb2U1Umc9PSIsInZtprovider_refresh_token_encryptedd5ab04e2-2109-4c0b-b513-8cba1dd54371I encryption_key (Hex)0x01020300784A7E08630802C9456B8B85CC5951D489859Cv COLLECtIONscontacts› CRM ObjectseRM owners› CRM Pipelines> Deals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiesPoSt search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET get subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGET https://hubspot-webhooks-iournal-na1.sGET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOST search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCS>FLOWSConnect Git E Console 2 TermirCNeR-JHgMxIZQINQ…..BodyCookiesJSONvPreviewSo, Pass the correct auth credentials v"message". "The OAuth token used to make this call expired 4 hour(s) ago.".#contov+". S"expire time": ["2026-05-07T06:41:35.576Z"401 Unauthorized • 149 ms • 1.14 KB • (a| ...=aIDOGlobals Vault Tools S 0 0 0...
|
iTerm2
|
NULL
|
NULL
|
2338
|
|
2337
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 49 m100% [Thu 7 May 14:11:48DEV (docker)181DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)83-zsh• 84screenpipe*•$5-zsh₴6Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2337
|
|
2336
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 49 m100% [Thu 7 May 14:11:43DEV (docker)T81DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)83-zsh• 84screenpipe*•$5-zsh₴6Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2336
|
|
2335
|
rostmancaltvlewWindowmelpProject© RingCentral/Clie rostmancaltvlewWindowmelpProject© RingCentral/Client.phpRematchActivityOnCrmObjectDetach.phpA EU [EU]v A jiminny@localhost& console uiminny clocainosADI [jiminny@localhost4 HS Jocal ljiminny@localhosA SF jiminny@localhost]A zoho_dev (jiminny@localhoV A PROD& console PrODI& console 1 PROD< DI PROD> AOAA QAI> 4 QAI PRODLSTAGING& console STAGING& console STAGiNgduranus STAGINGI> Fxtansinns# DeleteCrmEntity Trait.php© RateLimitException.phpMiddleware/RateLimited.pnpC) ProviderRateLimiter.php Xclass ProviderRateLimiterpublic function canMakeRequest(RateLimited $provider): boolservicesv D DatabaseV AEUconsole& |iminny@localhost4 HS_JocalA SF~ A PRODconsole 1s 381 msV A STAGINGA console 1s 250 ms…Docken/** @var RateLimitInterface $rateLimit */foreach (Sprovider->getRateLimits() as SrateLimit) {$key = $rateLimit->getKeyO);if ($this-›rateLimiter->tooManyAttempts($key, $rateLimit->getQuota())) {return false;h OutoutW 1rowv1i timinnv.social accounts XIX: Auto vRQGA®Did! sociable_idprovider_user_idprovider_user_tokenI provider_refresh_tokenMexnires149914827225182CNeR-JHgMxIZQLNQML8kQEwrAgwACAKUAhIJBB4BAQEDBxi(d5ab04e2-2109-4c0b-b513-8cba1dd543711778154080I refresh_token_expiresO providerhubspotI stateconnectedID auth_scope<nUll>retry_after<null>created_at2026-01-16 07-30-47I updated_at2026-05-07 11:11:20provider_user_token_encryptedeyJpdiI6Ik1PcXNtZ3R6TzFWMUVEMHBLb2U1Umc9PSIsInZtprovider_refresh_token_encryptedd5ab04e2-2109-4c0b-b513-8cba1dd54371I encryption_key (Hex)0x01020300784A7E08630802C9456B8B85CC5951D489859CPlatform Sprint 3 Q2© SyncToUsSevenShores|Hubsp.$i Service-Desk - Queur• Jy 20807 check varioA Sentry••Pull requests • jiminnU Useroilot I Ask Jiminsy-20773 fix user piloaJiminnuNew TaiQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.SEARCH › search deals= DocsAuthorization • Headers 11 Body • ScriptserawSettingsO binary GraphQL JSON~rilters":"value": 177304112436240GET ritos:/ Xsupoont Dally • In45 mNo environmentv) SaveCookiesSchema Beautify100% L2VAIlVariables in requestG token› All variablesThu 7 May 14:11:43UpgradeCNeR-JHgMxIZQINQ...v COLLECtIONscontacts› CRM ObjectseRM owners› CRM Pipelines> Deals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiesPoSt search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGeT https:ubspot-webhooks-lournal-nal.s.GET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAL.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOST search contact by emailPoSt search meetingsPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCS>FLOWS@ Connect Git = ConcoldB Te3092055800."hs_call_direction",BOdVJSONvPreviewe. Visualize200 OK • 244 ms • 1.71 KB • | e.g. Save Response ..==aID8w2019-06.16707.22-66 20274: 2015-035-16-07 :8218 3327) 3a02' ,"hubsoot owner id": "579583316"2026-05-04105:33:47.3402"archived": talse."ux":"httos:aop.hubspot.com/contacts/4392066/xecoxd/0-3/297846423"id". "181281563".#nronortjoc".S"hs_lastmodifieddate": "2026-04-19T16:14:05.694Z","updatedAt": "2026-04- 19T16:14:05.6942"....
|
iTerm2
|
NULL
|
NULL
|
2335
|
|
2334
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 49 m100% [Thu 7 May 14:11:41DEV (docker)181DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)83-zsh• 84screenpipe*•$5-zsh₴6Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2334
|
|
2333
|
rostmancaltvlewWindowmelpProject© RingCentral/Clie rostmancaltvlewWindowmelpProject© RingCentral/Client.phpRematchActivityOnCrmObjectDetach.phpA EU [EU]v A jiminny@localhost& console uiminny clocainosADI [jiminny@localhost4 HS Jocal ljiminny@localhosA SF jiminny@localhost]A zoho_dev (jiminny@localhoV A PROD& console PrODI& console 1 PROD< DI PROD> AOAA QAI> 4 QAI PRODLSTAGING& console STAGING& console STAGINGduranus STAGINGI> Fxtansinns# DeleteCrmEntity Trait.php© RateLimitException.phpMiddleware/RateLimited.pnpC) ProviderRateLimiter.pho Xclass ProviderRateLimiterpublic function canMakeRequest(RateLimited Sprovider): boolservicesv D DatabaseV AEUconsole& |iminny@localhost4 HS_JocalA SF~ A PRODconsole 1s 381 msV A STAGINGA console 1s 250 ms…Docken/** @var RateLimitInterface $rateLimit */foreach (Sprovider->getRateLimits() as SrateLimit) {$key = $rateLimit->getKeyO);if ($this-›rateLimiter->tooManyAttempts($key, $rateLimit->getQuota())) €return false;h OutoutW 1rowvii timinnv.socialaccounts XIX: Auto vRQGA®Did! sociable_idprovider_user_idprovider_user_tokenI provider_refresh_tokenMexnires149914827225182CNeR-JHgMxIZQLNQML8kQEwrAgwACAKUAhIJBB4BAQEDBxi(d5ab04e2-2109-4c0b-b513-8cba1dd543711778154080I refresh_token_expiresO providerhubspotI stateconnectedID auth_scope<nUll>retry_after<null>created_at2026-01-16 07-30-47I updated_at2026-05-07 11:11:20provider_user_token_encryptedeyJpdiI6Ik1PcXNtZ3R6TzFWMUVEMHBLb2U1Umc9PSIsInZtprovider_refresh_token_encryptedd5ab04e2-2109-4c0b-b513-8cba1dd54371I encryption_key (Hex)0x01020300784A7E08630802C9456B8B85CC5951D489859CPlatform Sprint 3 Q2© SyncToUsSevenShores|Hubsp.$i Service-Desk - Queur• Jy 20807 check varioA Sentry••Pull requests • jiminnU Useroilot I Ask Jimin@Jy-20773 fix user piloaJiminnuNew Tab40supoont Dally • In45 mQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.SEARCH › search deals= DocsParamsAuthorization • Headers 11 Body • ScriptsSettings• torm-dataeraw• binary GraphQL JSON ~rilters":"value": 1773041124362No environmentvSaveCookiesSchema Beautify100% L2VAIlVariables in requestG token> All variables.Thu 7 May 14:11:39Uparadev COLLECtIONscontacts› CRM ObjectseRM owners› CRM PipelinesDeals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiesPoSt search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGET https:ubspot-webhooks-lournal-nal.s.GET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOSt search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCS>FLOWS@ Connect Git = Concolda Te"hs_call_direction",BOdVCookiesJSONvPrevievSo, Pass the correct auth credentials v"message". "The OAuth token used to make this call expired 4 hour(s) ago.".#contov+". S"expire time": ["2026-05-07T06:41:35.576Z"401 Unauthorized • 145 ms • 1.14 KB • CA e.g Save kesponse ••==aID8...
|
iTerm2
|
NULL
|
NULL
|
2333
|
|
2332
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 49 m100% [Thu 7 May 14:11:39DEV (docker)T81DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)83-zsh• 84screenpipe*•$5-zsh₴6Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2332
|
|
2331
|
rostmancaltvlewWindowmelpProject© RingCentral/Clie rostmancaltvlewWindowmelpProject© RingCentral/Client.phpRematchActivityOnCrmObjectDetach.phpA EU [EU]v A jiminny@localhost& console uiminny clocainosADI [jiminny@localhost4 HS Jocal ljiminny@localhosA SF jiminny@localhost]A zoho_dev (jiminny@localhoV A PROD& console PrODI& console 1 PROD< DI PROD> AOAA QAI> 4 QAI PRODLSTAGING& console STAGING& console STAGINGduranus STAGINGI> Fxtansinns# DeleteCrmEntity Trait.php© RateLimitException.phpMiddleware/RateLimited.pnpC) ProviderRateLimiter.pho Xclass ProviderRateLimiterpublic function canMakeRequest(RateLimited Sprovider): boolservicesv D DatabaseV AEUconsole& |iminny@localhost4 HS_JocalA SF~ A PRODconsole 1s 381 msV A STAGINGA console 1s 250 ms…Docken/** @var RateLimitInterface $rateLimit */foreach (Sprovider->getRateLimits() as SrateLimit) {$key = $rateLimit->getKeyO);if ($this-›rateLimiter->tooManyAttempts($key, $rateLimit->getQuota())) €return false;h OutoutW 1rowvii timinnv.socialaccounts XIX: Auto vRQGA®Did! sociable_idprovider_user_idprovider_user_tokenI provider_refresh_tokenMexnires149914827225182CNeR-JHgMxIZQLNQML8kQEwrAgwACAKUAhIJBB4BAQEDBxi(d5ab04e2-2109-4c0b-b513-8cba1dd543711778154080I refresh_token_expiresO providerhubspotI stateconnectedID auth_scope<nUll>retry_after<null>created_at2026-01-16 07-30-47I updated_at2026-05-07 11:11:20provider_user_token_encryptedeyJpdiI6Ik1PcXNtZ3R6TzFWMUVEMHBLb2U1Umc9PSIsInZtprovider_refresh_token_encryptedd5ab04e2-2109-4c0b-b513-8cba1dd54371I encryption_key (Hex)0x01020300784A7E08630802C9456B8B85CC5951D489859CPlatform Sprint 3 Q2© SyncToUsSevenShores|Hubsp.$i Service-Desk - Queur• Jy 20807 check varioA Sentry••Pull requests • jiminnU Useroilot I Ask Jimin@Jy-20773 fix user piloaJiminnuNew Tab40supoont Dally • In45 m• SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.SEARCH › search deals= DocsParamsAuthorization • Headers 11 Body • ScriptsSettings• torm-dataeraw• binary GraphQL JSON ~rilters":"value": 1773041124362No environmentv) SaveCookiesSchema Beautify100% L2VAIlVariables in requestG token> All variables.Thu 7 May 14:11:37Uparadev COLLECtIONscontacts› CRM ObjectseRM owners› CRM Pipelines> Deals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiesPoSt search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGET https:ubspot-webhooks-lournal-nal.s.GET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOSt search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCS>FLOWS@ Connect Git = Concolda Te"hs_call_direction",BOdVCookiesJSONvPrevievSo, Pass the correct auth credentials v"message". "The OAuth token used to make this call expired 4 hour(s) ago.".#contov+". S"expire time": ["2026-05-07T06:41:35.576Z"401 Unauthorized • 145 ms • 1.14 KB • CA e.g Save kesponse ••==aID8...
|
iTerm2
|
NULL
|
NULL
|
2331
|
|
2330
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 49 m100% [Thu 7 May 14:11:37DEV (docker)T81DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 on ttys006H82APP (-zsh)83-zsh• 84screenpipe*•$5-zsh₴6Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#...
|
iTerm2
|
NULL
|
NULL
|
2330
|
|
2329
|
rostmancaltvlewWindowmelpProject© RingCentral/Clie rostmancaltvlewWindowmelpProject© RingCentral/Client.phpA EU [EU]v A jiminny@localhost& console uiminny clocainosADI [jiminny@localhost4 HS Jocal ljiminny@localhosA SF jiminny@localhost]A zoho_dev (jiminny@localhoV A PROD& console PrODIRematchActivityOnCrmObjectDetach.php# DeleteCrmEntity Trait.php© RateLimitException.phpMiddleware/RateLimited.pnpC) ProviderRateLimiter.pho Xclass ProviderRateLimiterpublic function canMakeRequest(RateLimited Sprovider): bool& console 1 PROD< DI PROD> AOAA QAI> 4 QAI PRODLSTAGING/** @var RateLimitInterface $rateLimit */foreach (Sprovider->getRateLimits() as SrateLimit) {$key = $rateLimit->getKeyO);if ($this-›rateLimiter->tooManyAttempts($key, $rateLimit->getQuota())) €return false;& console STAGING& console STAGINGduranus STAGINGI> Fxtansinnsservicesv D DatabaseV AEUconsole& |iminny@localhost4 HS_JocalA SF~ A PRODconsole 1s 381 msV A STAGINGA console 1s 250 ms…DockenPlatform Sprint 3 Q2© SyncToUsSevenShores|Hubsp.$i Service-Desk - Queur• Jy 20807 check varioA Sentry••Pull requests • jiminnU Useroilot I Ask Jimin@Jy-20773 fix user piloaJiminnuNew Tab40supoont Dally • In45 mQ SearchYour team is now on the Free plan with 1 admin. You retain editing access and other members are read-only. View team permissions to see who can edit, or upgrade to restore collaboration.SEARCH › search deals= DocsParamsAuthorization • Headers 11 Body • ScriptsSettings• torm-dataerawO binary GraphQL JSON~rilters":"value": 1773041124362No environmentvf SaveCookies° Schema Beautify100% L2Thu 7 May 14:11:36UparadeVAIlVariables in requestG tokenCNi2rongMxIZQINQ…..› All variablesh OutoutW 1rowvii timinnv.socialaccounts X+=IX: Auto vRQGA®Did! sociable_idprovider_user_idprovider_user_tokenI provider_refresh_tokenMexnires149914827225182CNeR-JHgMxIZQLNQML8kQEwrAgwACAKUAhIJBB4BAQEDBxi(d5ab04e2-2109-4c0b-b513-8cba1dd543711778154080I refresh_token_expiresO providerhubspotI stateconnectedID auth_scope<nUll>retry_after<null>created_at2026-01-16 07-30-47I updated_at2026-05-07 11:11:20provider_user_token_encryptedeyJpdiI6Ik1PcXNtZ3R6TzFWMUVEMHBLb2U1Umc9PSIsInZtprovider_refresh_token_encryptedd5ab04e2-2109-4c0b-b513-8cba1dd54371I encryption_key (Hex)0x01020300784A7E08630802C9456B8B85CC5951D489859Cv COLLECtIONscontacts› CRM ObjectseRM owners› CRM Pipelines> Deals~ Engagements• D OLD ENGAGEMENTSGET list meetingsPOST search moditied companiesPoSt search tasksGET read call> PoST search callsGET list callsPosT meetings scheduledGET aet meetinaPOST get link to task> POST Create Contact with Associatio› HubspotJournal & webhoooks v4POSt Get tokenGET det subscriptionsPOST create subscriptionGET Journal earliestGET Journal latestGET https:ubspot-webhooks-lournal-nal.s.GET next offsetpost get loken prodDEL DELSTE CURSCRIPTION DEP PORTAI.GET DEAL WITH HISTORY PROPERTIES V3©Authi> Properties> RESSARCHSEARCHPost search contact by phonePOSt search contact by emailPOST search meetinasPOST search notes> Post Search calls v3.IPOST Search related meetinas v3POST search dealsCAMIDONMCNTC> SPFCS>FLOWS@ Connect Git = Concolda Te"hs_call_direction",BOdVCookiesJSONvPrevievSo, Pass the correct auth credentials v"message". "The OAuth token used to make this call expired 4 hour(s) ago.".#contov+". S"expire time": ["2026-05-07T06:41:35.576Z"401 Unauthorized • 145 ms • 1.14 KB • | e.g. Save Response •••==aID8...
|
iTerm2
|
NULL
|
NULL
|
2329
|
|
2328
|
iTerm2ShellEditViewSessionScriptsProfilesWindowHel iTerm2ShellEditViewSessionScriptsProfilesWindowHelp(ah]Support Daily • in 49 mA100% C 8DEV (docker)83Thu 7 May 14:11:34T₴1₴6DOCKERLast login: Thu MayO ₴1DEV (docker)7 09:44:56 onttys006H82APP (-zsh)-zsh• 84|screenpipe*-zshPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentsPoetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parentslukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ devroot@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00*Syncing opportunity for HubspotYour HubSpotaccount has become disconnected. Please login to Jiminny to reconnect. skipping...root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -RDEVaccess_tokenCFPAsBNZxoDp5kAcRyeB1QoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAACNeR-JHgMxIZQLNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQLNQM18kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAY1access_token_expires_at= 2026-05-07 11:41:20refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371refresh_token_expires_at =root@docker_lamp_1:/home/jiminny#31...
|
iTerm2
|
NULL
|
NULL
|
2328
|
|
2327
|
Platform Sprint 3 Q2 - Platform Team - Scrum Board Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Jy 20807 check various issues with stages by nikolaybiaivanov · Pull Request #12041 · jiminny/app
Jy 20807 check various issues with stages by nikolaybiaivanov · Pull Request #12041 · jiminny/app
Sentry
Sentry
Pull requests · jiminny/app
Pull requests · jiminny/app
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
Jiminny
Jiminny
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Sign In
Sign In
google Sign in with Google
Sign in with Google
microsoft Sign in with Office 365
Sign in with Office 365
Login via SSO
Login via SSO
EU
EU
Worldwide
Don’t have account yet? Speak to your sales leader to get an invite.
By using this service you agree to the
Privacy Policy
Privacy Policy
and
Terms of Service
Terms of Service
.
TERMS
TERMS
KNOWLEDGE BASE
KNOWLEDGE BASE
BLOG
BLOG...
|
Firefox
|
Jiminny — Work
|
app.dev.jiminny.com/login
|
2327
|
|
2326
|
Platform Sprint 3 Q2 - Platform Team - Scrum Board Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
SevenShores\Hubspot\Exceptions\BadRequest: Client error: `POST https://api.hubapi.com/crm/v3/objects/contact/search` resulted in a `429 Too Many Requests` response: {"status":"error","message":"You have reached your secondly limit.","errorType":"RATE_LIMIT
Service-Desk - Queues - Platform team - Service space - Jira
Service-Desk - Queues - Platform team - Service space - Jira
Jy 20807 check various issues with stages by nikolaybiaivanov · Pull Request #12041 · jiminny/app
Jy 20807 check various issues with stages by nikolaybiaivanov · Pull Request #12041 · jiminny/app
Sentry
Sentry
Pull requests · jiminny/app
Pull requests · jiminny/app
Userpilot | Ask Jiminny Report Generated
Userpilot | Ask Jiminny Report Generated
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
Jiminny
Jiminny
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Sign In
Sign In
google Sign in with Google
Sign in with Google
microsoft Sign in with Office 365
Sign in with Office 365
Login via SSO
Login via SSO
EU
EU
Worldwide
Don’t have account yet? Speak to your sales leader to get an invite.
By using this service you agree to the
Privacy Policy
Privacy Policy
and
Terms of Service
Terms of Service
.
TERMS
TERMS
KNOWLEDGE BASE
KNOWLEDGE BASE
BLOG
BLOG...
|
Firefox
|
Jiminny — Work
|
app.dev.jiminny.com/login
|
2326
|
|
2325
|
Project: faVsco.js, menu
master, menu
Start Listen Project: faVsco.js, menu
master, menu
Start Listening for PHP Debug Connections
AskJiminnyReportActivityServiceTest
Run 'AskJiminnyReportActivityServiceTest'
Debug 'AskJiminnyReportActivityServiceTest'
More Actions
JetBrains AI
Search Everywhere
IDE and Project Settings
Execute
Explain Plan
Browse Query History
View Parameters
Open Query Execution Settings…
In-Editor Results
Tx: Auto
Cancel Running Statements
Playground
jiminny
Sync Changes
Hide This Notification
Code changed:
Hide
6
1
6
Previous Highlighted Error
Next Highlighted Error
# [PASSWORD_DOTS] HS [PASSWORD_DOTS]
select * from teams where id = 2; # 2
select * from features; # 2
select * from team_features where team_id = 2; # 2
select * from crm_configurations where id = 2; # 2
select * from users where team_id = 2; #
select * from playbooks where team_id = 2; # event 38
select * from playbook_categories where playbook_id = 38; #
SELECT * FROM activities WHERE crm_configuration_id = 2 and crm_provider_id is not null order by id desc;
[URL_WITH_CREDENTIALS] RateLimitInterface $rateLimit */
foreach ($provider->getRateLimits() as $rateLimit) {
$key = $rateLimit->getKey();
if ($this->rateLimiter->tooManyAttempts($key, $rateLimit->getQuota())) {
return false;
}
}
return true;
}
public function requestAvailableIn(RateLimited $provider): int
{
return $provider->getRateLimits()->isNotEmpty()
? $provider->getRateLimits()
->map(fn (RateLimitInterface $rateLimit): int => $this->rateLimiter->availableIn($rateLimit->getKey()))
->max()
: 0
;
}
public function incrementRequestCount(RateLimited $provider): void
{
/** @var RateLimitInterface $rateLimit */
foreach ($provider->getRateLimits() as $rateLimit) {
$this->rateLimiter->hit($rateLimit->getKey(), $rateLimit->getWindow());
}
}
}
Project
Project
New File or Directory…
Expand Selected
Collapse All
Options
Hide...
|
PhpStorm
|
faVsco.js – HS_local [jiminny@localhost]
|
NULL
|
2325
|
|
2324
|
Project: faVsco.js, menu
master, menu
Start Listen Project: faVsco.js, menu
master, menu
Start Listening for PHP Debug Connections
AskJiminnyReportActivityServiceTest
Run 'AskJiminnyReportActivityServiceTest'
Debug 'AskJiminnyReportActivityServiceTest'
More Actions
JetBrains AI
Search Everywhere
IDE and Project Settings
Execute
Explain Plan
Browse Query History
View Parameters
Open Query Execution Settings…
In-Editor Results
Tx: Auto
Cancel Running Statements
Playground
jiminny
Sync Changes
Hide This Notification
Code changed:
Hide
6
1
6
Previous Highlighted Error
Next Highlighted Error
# [PASSWORD_DOTS] HS [PASSWORD_DOTS]
select * from teams where id = 2; # 2
select * from features; # 2
select * from team_features where team_id = 2; # 2
select * from crm_configurations where id = 2; # 2
select * from users where team_id = 2; #
select * from playbooks where team_id = 2; # event 38
select * from playbook_categories where playbook_id = 38; #
SELECT * FROM activities WHERE crm_configuration_id = 2 and crm_provider_id is not null order by id desc;
[URL_WITH_CREDENTIALS] RateLimitInterface $rateLimit */
foreach ($provider->getRateLimits() as $rateLimit) {
$key = $rateLimit->getKey();
if ($this->rateLimiter->tooManyAttempts($key, $rateLimit->getQuota())) {
return false;
}
}
return true;
}
public function requestAvailableIn(RateLimited $provider): int
{
return $provider->getRateLimits()->isNotEmpty()
? $provider->getRateLimits()
->map(fn (RateLimitInterface $rateLimit): int => $this->rateLimiter->availableIn($rateLimit->getKey()))
->max()
: 0
;
}
public function incrementRequestCount(RateLimited $provider): void
{
/** @var RateLimitInterface $rateLimit */
foreach ($provider->getRateLimits() as $rateLimit) {
$this->rateLimiter->hit($rateLimit->getKey(), $rateLimit->getWindow());
}
}
}
Project
Project
New File or Directory…
Expand Selected
Collapse All
Options
Hide...
|
PhpStorm
|
faVsco.js – HS_local [jiminny@localhost]
|
NULL
|
2324
|
|
2323
|
Last login: Thu May 7 09:44:56 on ttys006
Poetry Last login: Thu May 7 09:44:56 on ttys006
Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parents
Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parents
lukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ dev
root@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00'
Syncing opportunity for Hubspot
Your HubSpot account has become disconnected. Please login to Jiminny to reconnect. skipping...
root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A 1499 -R
----------------------------------------------------------------------------------------------------
access_token => CNeR-JHgMxIZQlNQMl8kQEwrAgwACAkUAhIJBB4BAQEDBxiCiYwCIN7Y_Qwo0qwCMhTnG549n-YtNuc1jgj-2AsLPSmw3DoyQlNQMl8kQEwrAiUACBkGawEFThwBARIBAQEEATEEAQEBAQEBAQEBAQUBEggBAQEBAYlCFPAsBNZxoDp5kAcRyeBlQoE5SM7DSgNuYTFSAFoAYABo3tj9DHAAeAA
----------------------------------------------------------------------------------------------------
access_token_expires_at => 2026-05-07 11:41:20
----------------------------------------------------------------------------------------------------
refresh_token => d5ab04e2-2109-4c0b-b513-8cba1dd54371
----------------------------------------------------------------------------------------------------
refresh_token_expires_at =>
----------------------------------------------------------------------------------------------------
root@docker_lamp_1:/home/jiminny#
DOCKER
Close Tab
DEV (docker)
Close Tab
APP (-zsh)
Close Tab
-zsh
Close Tab
screenpipe"
Close Tab
-zsh
Close Tab
⌥⌘1
DEV (docker)...
|
iTerm2
|
DEV (docker)
|
NULL
|
2323
|
|
2322
|
Last login: Thu May 7 09:44:56 on ttys006
Poetry Last login: Thu May 7 09:44:56 on ttys006
Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parents
Poetry could not find a pyproject.toml file in /Users/lukas/jiminny/app or its parents
lukas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/app (JY-20773-fix-automated-reports-user-pilot-tracking) $ dev
root@docker_lamp_1:/home/jiminny# php artisan crm:sync-opportunity --teamId=2 --from='2026-05-01 00:00:00'
Syncing opportunity for Hubspot
Your HubSpot account has become disconnected. Please login to Jiminny to reconnect. skipping...
root@docker_lamp_1:/home/jiminny# php artisan jiminny:token-info -A
DOCKER
Close Tab
DEV (docker)
Close Tab
APP (-zsh)
Close Tab
-zsh
Close Tab
screenpipe"
Close Tab
-zsh
Close Tab
⌥⌘1
DEV (docker)...
|
iTerm2
|
DEV (docker)
|
NULL
|
2322
|