Discussions

I am experiencing an issue when trying to retrieve a specific contact via your API. 

My automation relies on fetching contact details, but this particular contact is not being returned by the /api/v2/workspaces/{workspace_id}/contacts endpoint, even though it clearly exists in the workspace.

Details of the Problem:

I am making GET requests to the following endpoint for Workspace ID jPGQRL: https://api.myclickfunnels.com/api/v2/workspaces/jPGQRL/contacts

I have performed two specific tests, and in both cases, the contact is not present in the Data array of the API's successful 200 OK response.

Test Scenarios & Results:

Request with email query parameter:

URL Used: https://api.myclickfunnels.com/api/v2/workspaces/{workspace_id}/contacts?email={{invitee_email}}

Expected Result: The API should return only the contact matching this email, or an empty Data array if it doesn't exist.

Actual Result: The API returns a 200 OK status, but the Data array does not contain, Instead, it contains a bunch of seemingly unrelated contacts from inside the workspace.

Request without any filters (fetching general contact list):

URL Used: https://api.myclickfunnels.com/api/v2/workspaces/{workspace_id}/contacts

Expected Result: If the email contact exists (which it does because I've checked the UI), it should be present in the list of contacts returned (possibly on a paginated page).

Actual Result: The API returns a 200 OK status, but after inspecting the full Data array of the response, the contact is still not included.

Confirmation of Contact Existence: I have verified that the contact does exist within my ClickFunnels 2.0 workspace when viewed through the UI.

Tool Used: I am using Make.com to build the automation and interact with your API, last time I tested it it worked PERFECTLY, but now for some reason it seems to be getting stuck at this step.

Note that the exact URL I use is "https://api.myclickfunnels.com/api/v2/workspaces/{workspace_id}/contacts?email={{10.invitee_email}}"  

This issue is preventing me from reliably fetching and processing this contact's information (and all the future ones potentially), which halts the workflow. Could you please investigate what the problem with /contacts API endpoint is?

Thank you for your assistance.