Back to Help Center

'Daily limit reached' errors explained

Crispy enforces two different daily limits, and the error text tells you which one you hit.

LinkedIn safety limits

The error looks like: 'LinkedIn safety limit reached: invitation (15/15 today). This protects your account from restrictions. Try again tomorrow or use get_account to find an account with remaining capacity.'

This is the per-account, per-action-category cap that protects your LinkedIn account. Each category has its own daily budget: search, profile views, messaging, invitations, posting, engagement, endorsements, follows, and more. Defaults are conservative, for example 15 invitations, 150 messages, and 10 posts per day.

What to do:

  • Run 'get_account' to see every category with used, limit, and remaining.
  • Wait for the reset at midnight UTC.
  • On multi-account plans, another connected account may still have capacity.

During warm-up, effective limits are lower than the standard defaults while the account ramps. That is intentional.

API rate limit

The error looks like: 'Daily API limit reached (X/Y)', followed by either 'Upgrade your plan for higher limits' or a note that your subscription payment is past due.

This is the total daily API call budget, independent of LinkedIn safety. It also resets at midnight UTC. Active paid subscriptions have no daily API call limit, so this error means one of two things:

  • You have no active subscription. Subscribe to get access.
  • Your subscription payment is past due. While a payment is failing, the account is temporarily limited to 50 API calls per day per LinkedIn account. Upgrading does not lift this limit; updating your payment method at https://crispy.sh/dashboard/billing does. The counter includes background inbox and content sync, so it can be higher than the calls you made yourself; the usage number on the billing dashboard counts the same way while the limit applies.

REST responses carry X-RateLimit-Remaining and X-RateLimit-Reset headers so clients can self-pace, and the CLI prints a remaining-requests footer after each call.

Which one is blocking me?

Safety limit errors name an action category. API limit errors say 'Daily API limit reached' and mention your plan or payment. And read-only tools carry no safety limit at all, so if reads work while sends fail, it is the safety limit.

Still stuck? Email [email protected] or browse answered questions.