To retrieve, with admin access using only the task ID (which I obtain from a webhook for completed tasks), the details of a task belonging to any user. However, the API call using Service Account Keys doesn’t seem to yield any results. On the other hand, using personal authorization doesn’t allow me to access all users’ tasks.
Additionally, it doesn’t seem possible to fetch custom fields, which is crucial for me! I’d rather not waste time creating systems with XML, which are being phased out.
The XML-RPC API has the flexibility to do what you want, but we do not know when they plan to sunset it. Keap need to be do a lot more work with the REST API, including being able to query Custom Fields. Otherwise there is going to be gaps with the REST API that will make it difficult to transition across in the future.
Based on the tests I ran, there doesn’t appear to be a way to manipulate values on custom fields for Tasks in the REST V1 API endpoint, and as @Pav said, the REST V2 API endpoints haven’t been implemented.
The only way I can see doing this is by using the XML-RPC API. I tested using the dsLoad() and dsUpdate() methods in the iSDK on the ContactAction table, to pull and update the custom fields.
I agree that it would be nice to start updating code to use the newest API endpoints, but since they’re so limited, it’s just not possible.
My initial reply was to mention about another conversation regarding the ability to query Custom Fields via the REST API. If you were planning to do that with your integration then you would be disappointed.
You mention about not wasting time in using the XML-RPC API. As Marion pointed out the REST API is not comparable with XML-RPC, so you have to go down the XML-RPC API route to do specific things.
We do not have any idea what is going on with the REST API. Version 1 failed to match the XML-RPC API, and from what I am seeing Version 2 is heading down the same route as well. Now that Thryv has acquired Keap, we do not know what is going to happen next. The REST API rollout has turned out to be a mess.
The “ContactAction” XML-RPC API Table contains the Tasks, but also contains the Appointments and Notes as well.
Ah, now I understand what you mean. I am use to setting up Tasks in the My Day section. I see in the Automations that the Create Task has a Task Outcome Options field, which is not present in the regular Tasks section.
Checking the API Documentation, there is nothing currently available that can handle it. Apparently REST V2 will have significant updates for 2025, so I would guess that in a few months time the Task Endpoint will be exposed with the ability to update the Task Outcomes.
