What changed

Apollo searches now apply the filters in your URL

Apollo changed the parameter names it puts in a search URL, and our reader was still looking for the old ones. The result was that filters were dropped and the search ran without them, so lists came back far broader than the search you built. This is fixed: job titles, locations, company keywords, exclusions and employee size are all read again.

Two things worth knowing. A URL that carries no readable filter is now refused instead of running, because such a search returns everything and spends your balance on it. And a few Apollo filters cannot be read from a URL at all, in particular a saved persona and an industry chosen from Apollo's own list; those are skipped, so set them as ordinary filters in Apollo before copying the URL.

A job that runs out of time now delivers what it collected

Large jobs could hit the extraction time limit. Until now everything collected up to that point was discarded and the full amount refunded, so you were left with nothing. Now the records that were collected are delivered and only those are charged; the rest is refunded automatically. Large jobs also get a longer time budget, sized to the number of records you asked for.

List names accept every alphabet

Names such as Mısır Tekstil or Şirketler-2026 were rejected because the field only allowed the English alphabet. Any letters and digits are accepted now.

LinkedIn searches are built from filters, not a search URL

Earlier wording on this site suggested you could paste a LinkedIn or Sales Navigator search URL. That was never how the LinkedIn extraction worked, and we have corrected it everywhere. You describe the audience with filters instead:

• Job titles to include and to exclude
• Locations to include and to exclude, from a list of 1,857 countries, states and regions
• Seniority level and function
• Company domains, keywords to include and to exclude
• Industry, headcount, revenue range and funding stage

Apollo.io is unchanged: you still paste a people search URL you built there. Google Maps takes a search term and a place.

An API for your own code and for AI agents

You can now start extractions from your own code, or let an AI assistant do it. Price a job for free, start it, poll it, read the records as JSON. Documentation and the OpenAPI file are at evascrape.com/docs; keys are created in your account under API keys. An MCP server, so an assistant can call Evascrape directly, is on the way.

You land on the source you chose

If you arrive from a LinkedIn or Google Maps link, that is the form that opens after you sign up, confirm your email or sign in. Previously everyone landed on Apollo.

Times follow your own clock

Dates in your history are shown in your browser's timezone. Hover to see the original UTC value.

Records without an email address cost less

On Apollo.io and LinkedIn jobs, delivered records that carry no email address are now billed at a reduced rate rather than the full one. The difference is refunded automatically when the job finishes, and the amount is stated in the notification and in the email you receive.

Google Maps returns the number you asked for

The per-term limit is now worked out from your total, so a request for 700 places across three search terms collects up to 700 rather than stopping early. If your terms cannot cover the total, the form says how many more you need before you spend anything.

LinkedIn: include people whose email is not yet verified

A new checkbox on the LinkedIn form. Leaving it off is the most common reason a list comes back much shorter than requested, because only fully verified addresses are counted. Turning it on widens the pool considerably.

Clearer refunds

When a job delivers less than you asked for, the notification now separates the refund for undelivered records from the reduced-rate adjustment, and shows the rate that was actually applied.