Search Person without specifying name returns useless data

Question

Hi there,

When I send empty criteria for first/last name the "Search person with Filter" API returns hidden profiles "Linkedin Member", instead of public profiles, as expected. Is it possible to omit hidden profiles in output?

And other question is how can I control page size in this request, because 3 records per request is not enough definitely.

Thanks

```json
{
    "success": true,
    "status": 200,
    "data": {
        "people": [
            {
                "fullName": "LinkedIn Member",
                "primarySubtitle": "Senior Node.js Backend Developer",
                "summary": "Current: Senior Node.js Backend Engineer at Nextbike Polska S.A.",
                "secondarySubtitle": "Warsaw",
                "navigationUrl": "https://www.linkedin.com/search/results/people/headless?geoUrn=%5B105072130%5D&title=senior&origin=FACETED_SEARCH&keywords=node%20developer"
            },
            {
                "fullName": "LinkedIn Member",
                "primarySubtitle": "Senior Frontend Developer",
                "summary": "Current: Senior Frontend Developer at DataArt",
                "secondarySubtitle": "Poland",
                "navigationUrl": "https://www.linkedin.com/search/results/people/headless?geoUrn=%5B105072130%5D&title=senior&origin=FACETED_SEARCH&keywords=node%20developer"
            },
            {
                "fullName": "LinkedIn Member",
                "primarySubtitle": "Senior Developer Node.js in Huuuge Games",
                "summary": "Current: Senior Developer / Node.js at Huuuge Games",
                "secondarySubtitle": "Bydgoski",
                "navigationUrl": "https://www.linkedin.com/search/results/people/headless?geoUrn=%5B105072130%5D&title=senior&origin=FACETED_SEARCH&keywords=node%20developer"
            }
        ],
        "totalResults": 3404
    }
}
```

EZ · Answer

Hey, 
This endpoint is meant to find 1 person per API call. If need to scrape a list of leads, you can try Sales navigator endpoints.

P Sam · Answer

* Instead of the discount, it makes sense for you to change requests credits calculation - for example only 10 valid profiles in people search should be threated as 1 request. In current implementation the api seems useless. 
* The bug with limitation of 3 person per request is still there.
The endpoint seems useless with such bugs

EZ · Answer

Linkedin returns all profiles matching search query but hides those profiles which are out of searcher's network.

Don't worry about number of API calls, I can give you a huge discount in this regard if you need a decent quota.

P Sam · Answer

1) Filtering on client side makes no sense, because it contains lots of such records. In addition, with current limitation of 3, or even 10 records per page, it will drain request limits quickly.
2) Why should API return these useless profiles, which contains no any information at all?

EZ · Answer

You can filter out each item that have name = "Linkedin Member" from "people" Array. Does'nt that work for you?

P Sam · Answer

Can you also advice how to eliminate "Linkedin Member" profiles in results? I would like to retrieve profiles with names. But all pages of API output are showing stub "Linkedin Member".

EZ · Answer

Three people in response is quite a stramge thimg for us too. I have informed development team about this. Will ping you with update soon

LinkedIn data scraper

9.9 / 10

1,229ms

99%

100%

Search Person without specifying name returns useless data