Skip to Content
SendCrew

Errors and limits

Error codes, HTTP statuses and API rate limits.

Errors come back as JSON with a stable error code, a readable message and sometimes details. Over MCP the same body is returned as a tool result with isError: true.

{ "error": "SAFETY_BLOCKED", "message": "This person was already contacted by another sender.", "details": { "reason": "contacted_by_other_sender" } }
CodeHTTPMeaning
BAD_REQUEST400The input failed validation.
UNAUTHORIZED401Missing or invalid API key.
PAYMENT_REQUIRED402Your plan doesn't cover this (for example, more senders than your trial allows).
FORBIDDEN403The key can't access this workspace or resource.
NOT_FOUND404No such action, sender, thread or contact.
CONFLICT409The request clashes with the current state.
SAFETY_BLOCKED422The safety layer refused the write. details.reason says why.
RATE_LIMITED429Too many requests. Wait Retry-After seconds.
UNAVAILABLE503A dependency is down. Try again later.

Rate limits

Each API key can make 120 requests per minute across MCP and REST. This limits API calls only; how fast LinkedIn actions run is set by the safety rules.

On this page