Seeking Help with Apollo API for People Search Response Values

Adrian P. · 2025-11-28T13:44:08.676Z

Hey, I'm using HTTP API call to call Apollo's people search (https://api.apollo.io/api/v1/mixed_people/search) In clay HTTP API call I want to use 'Response values to return' to reutnr only name, email, linkedin url, title. I want to do this for entire list of records (not just one record) I've been trying different ways but I can't figure it out. Can anyobdy help me?

Seeking Help with Apollo API for People Search Response Values | Clay

Clay Support
APP
·
·
To only return name, email, title, and profile URL for all records in your Clay HTTP API call, use the “Field Paths to Return” option. Enter the field paths separated by commas, using dot notation for nested fields. For example, if the response structure is people: [{name, email, title, profile_url}], set:
people.name, people.email, people.title, people.profile_url
This will filter the response to just those fields for every record in the list. [1] [2]
Clay Support
APP
·
·
Is that what you were looking for?
Adrian P.
·
·
There is no Field paths to return just Response values to return and i can choose from input text with tokens and formula. In text with tokens when I put the thing you suggested I'm getting this. It's fragmented. "," works automatically as a tag seperator
Clay Support
APP
·
·
To only get name, email, title, and profile URL for every record, use the “Field Paths to Return” field in Clay’s HTTP API setup. Enter each field path separated by a comma, using dot notation for nested fields. For example, if your response array is under people, enter:
people.name, people.email, people.title, people.profile_url
This will return just those fields for all records in the list. [1] [2]
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
Returning 0 people could be due to a mismatch in your request body formatting or an incorrect API key for the endpoint. Double-check that your JSON body uses proper quotes for string values and commas between keys. Also, ensure you’re using the correct API key for Apollo’s mixed_people/search endpoint.
For “Response values to return,” you should specify the results path (e.g., people) so Clay knows where to find the array in the response. Then, use field paths like people.name, people.email, people.title, and people.profile_url to filter the returned fields for all records. If you’re still stuck, paste your full JSON body here so I can help troubleshoot further. [1]
Clay Support
APP
·
·
Was this helpful?
Adrian P.
·
·
{ "api_key": "api key", "q_organization_domains": "google.com", "page": 1, "per_page": 100 }
Clay Support
APP
·
·
To configure Clay’s HTTP API call to Apollo’s mixed_people/search, make sure your JSON body uses proper quotes for string values and commas between keys, like this:
{ "api_key": "your_api_key", "q_organization_domains": "[google.com](<a href="https://google.com">https://google.com</a>)", "page": 1, "per_page": 100 }
Check that you’re using the correct API key for this endpoint. If you get a “failed to parse body” error, copy your JSON into a plain text editor to check for hidden characters or formatting issues. If you need more help, paste your full JSON here so I can help troubleshoot further. [1] [2] [3]
Clay Support
APP
·
·
Did this help?
Adrian P.
·
·
no
Clay Support
APP
·
·
I’m sorry for the trouble you’re experiencing. I’ll connect you to a human agent who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Bo (.
·
·
Adrian - Do you mind sending the link (url) to the table so we can take a look?
Adrian P.
·
·
https://app.clay.com/workspaces/424877/workbooks/wb_0t6fsskcgYRNQ7QBtEw/tables/t_0t6fsst9jfMg9Wfigpv/views/gv_0t6fsstEtPh82ZyGc8n

22 comments