Skip to main content
API troubleshooting: find the symptom, identify the cause, apply the fixAPI troubleshooting: find the symptom, identify the cause, apply the fix
Find the symptom, then follow the fix. If you’re still stuck, contact support with the request path, the time and the status code. Never send your API key.
The X-API-KEY header is missing or the key isn’t valid.
  • Check that the header name is exactly X-API-KEY and that the value has no quotes or trailing spaces.
  • Make sure the key still exists on the API page.
  • Make sure your proxy or HTTP client doesn’t strip custom headers.
The key can’t access this resource. The most common cause is a wrong Account ID in the path: copy it again from My Account. See authentication.
You hit a rate limit. Back off and retry later. Autocomplete allows 10 requests per second and feedback 60 per minute, per account. For many work emails, use the bulk work email lookup. See API errors and rate limits.
Forager has no data for that input.
  • Try another identifier for the same person. For example, find their Forager person_id with person role search, then look up with the ID.
  • Check that a LinkedIn public identifier is only the part after /in/, such as jane-doe, not the full URL.
Filters such as industries, locations, skills and technologies take Forager IDs, not free text. Get the IDs from the autocomplete endpoints first. See Find valid filter IDs.
Poll the bulk retrieve endpoint with a back-off, for example every few seconds, and honour a Retry-After header if one is sent. Polling never consumes credits. A batch is rejected, and nothing is charged, if your credit balance can’t cover the whole batch. See bulk work email lookups.
  • List your recent charges with the credit usage endpoints.
  • Look for repeated lookups of the same person, and cache results.
  • Run contact lookups only for search results you keep.
Report it with the feedback endpoints, with contact_status and, if you know it, is_correct_person: false.
Last modified on October 28, 2026