Employee Data
...
Endpoints
Search Filters
6 min
data type employee posts query type coresignal's custom filters url https //api coresignal com/cdapi /v2/post employee/search/filter overview explore the available filters, their potential applications, and helpful tips use the endpoint to discover post ids this endpoint offers a less complex user experience than the /v2/post employee/search/filter endpoint if you prefer uncomplicated queries, opt for this endpoint below are details about filter explanations and how to use them endpoint structure full structure { "author profile url" "string", "article body" "string", "comments profile url" "string", "comments body" "string", "date published gte" "string", "date published lte" "string" } filter list example outputs are redacted and may not contain all the fields you would receive using the endpoint author profile url filter name data input type description usage author profile url s tring author's profile url use it to find records based on the profile's url available operators and (both keywords need to be present) or (one of the two input values) example input no operator { "author profile url" "https //professional network com/in/john doe" } use "(first phrase) or (second phrase)" if you are searching for words in a phrase and want them to be interpreted together article body filter name data input type description usage article body s tring content of the post use it to find records based on content available operators and (both keywords need to be present) or (one of the two input values) use "(first phrase) or (second phrase)" if you are searching for words in a phrase and want them to be interpreted together example input article body { "article body" "promoted to senior data analyst" } comments profile url filter name data input type description usage comments profile url s tring profile url of a posted comment use to find post records based on the posted comment profile url available operators and (both keywords need to be present) or (one of the two input values) use "(first phrase) or (second phrase)" if you are searching for words in a phrase and want them to be interpreted together comments profile url { "comments profile url" "https //www professional network com/in/john smith" } comments body filter name data input type description usage comments body s tring content of the comment use it to find post records based on the comments available operators and (both keywords need to be present) or (one of the two input values) example input no operator { "comments body" "this post is written by ai" } use "(first phrase) or (second phrase)" if you are searching for words in a phrase and want them to be interpreted together date published gte filter name data input type description usage date published gte s tring date and time when the record was published find employee records based on publication date use the yyyy mm dd date format the output value will be greater than or equal to the input value example input date published gte { "date published gte" "2025 07 01" } date published lte filter name data input type description usage date published lte s tring date and time when the record was published find employee records based on publication date use the yyyy mm dd date format the output value will be less than or equal to the input value example input date published lte { "date published lte" "2025 07 01" }