Evaboot API
  • Documentation
  • API Reference
Evaboot APIMCP ServerTroubleshooting
powered by Zudoku
Documentation

Troubleshooting

Check your connection first

Before debugging anything else, call the quota endpoint. It needs nothing but your API key, so it tells you whether the key works and whether your account is properly set up:

TerminalCode
curl -H "Authorization: Bearer YOUR_API_KEY" \ https://api.evaboot.com/v1/quota/

Errors

Every error comes back in the same shape:

Code
{ "success": false, "error": { "type": "InsufficientCredits", "message": "..." } }

401 Unauthorized

  • Check the header is exactly Authorization: Bearer YOUR_API_KEY.
  • Confirm the key is current — rotating or deleting it in Integrations → API invalidates the old value immediately.

402 Insufficient credits

Your balance won't cover the request. Check it with GET /v1/quota/ or on the dashboard.

429 Too many requests

Either your daily export quota is spent, or you've hit the search-builder's cap of 100 calls per day. Quotas reset daily.

422 Validation error

The request body or a Sales Navigator URL was rejected. The message names the specific field or reason. A URL that LinkedIn itself refuses — a search that's too broad, or filters that exceed its limits — also surfaces here.

Quota shows 0, or a seat is invalid

Your Evaboot account has no usable Sales Navigator cookies. The stored session is missing, or LinkedIn no longer accepts it.

Evaboot cannot refresh those cookies. Sign in to this same Evaboot account in Chrome, open a Sales Navigator search with the Evaboot extension installed, and click Export with Evaboot. Opening the Launch export page writes the cookies. The user does not have to click Launch export. Installing the extension, or opening Sales Navigator, does not by itself. Then retry.

Steps: https://help.evaboot.com/public/bug-fixing/how-to-reconnect-your-linkedin-account/

409, connection expired

The API answers 409 when the Sales Navigator seat was never connected, and again when the cookies it stored are no longer accepted. Both messages name the same fix: the Export with Evaboot click above. A reconnect is a new export, not a reinstall.

Still stuck?

Contact us via the Help Center. Include the endpoint, the request body, and the full error response.

Last modified on October 9, 2026
MCP Server
On this page
  • Check your connection first
  • Errors
    • 401 Unauthorized
    • 402 Insufficient credits
    • 429 Too many requests
    • 422 Validation error
  • Quota shows 0, or a seat is invalid
  • 409, connection expired
  • Still stuck?
JSON