Back to Help Center

Understanding daily limits

Every connected LinkedIn account has per-category daily caps. These are the defaults:

  • Searches: 300 per day (people, company, and post searches share it)
  • Profile views: 250 per day
  • Messages: 150 per day (regular messages, InMail, forwards, and voice messages share it)
  • Invitations: 15 per day
  • Posts: 10 per day (create_post and publish_draft share it)
  • Engagement: 100 per day (reactions, comments, comment replies, and reposts share it)
  • Endorsements: 50 per day
  • Follows and unfollows: 50 per day
  • Connection removals: 10 per day
  • Profile edits: 10 per day

All counters reset at midnight UTC. When a cap is reached, further actions in that category are blocked until the reset.

Invitations carry a second, shorter limit on top of the daily cap: your daily invitation budget is spread across 8 hours, so the default 15 per day works out to 2 per hour. This stops a full day of invitations going out in a few minutes, which is a strong automation signal. See 'Why invitations spread across the day' for detail.

Cleanup actions are deliberately not counted. Withdrawing a pending invitation with cancel_invitation and accepting or declining inbound invitations never consume your invitation budget, so tidying up is always possible.

Use get_account to see today's usage and the effective cap for each category at any time. If warm-up is active, the warm-up limit applies whenever it is lower than the normal cap.

You can customize limits per category with manage_outreach_settings using action 'limits', passing a minimum and maximum. Crispy then picks a daily cap inside your range each day, so output varies naturally. For a new account, set ranges below the defaults first and raise them as the account builds history.

The defaults are set conservatively so most accounts can run at them every day. Treat them as a ceiling, not a target: campaigns that consistently send a bit below capacity, inside business hours, are the ones that run for months without incident.

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