The following are the REST API Enhancements we as a user are expecting to see it in near future.
- Asset creator details to be included in the API (Email, Files, Campaigns etc.,)
- Flow ID is returned in campaign API, however there is no endpoint to utilize and get the flow details
- SmartList Cloning option is there, however there is no SmartList Update option (PUT method for updating the rules/criteria/conditions) via API. Likewise for Files, images can be created via API but there isn't an API option to update (PUT method) it. How come your product team ended up with just providing endpoints for reading and updating the meta data? Why should a development team in a company should create lines of code just to update a file name. I completely don't understand.
- Final member count in a smartlist is not able to be pulled via API, again I'm not sure why this not considered as a meta information.
- Worst pagination technique followed for returning records. While trying to pull the Activities (form submission alone) your document clearly states 300 records will be pulled in one single call. Whereas in reality just for 26 records, 10+ calls were used by Marketo API moreResults is set to true but the response will not have any result. What kind of logic is this and the worst part is when we raised a support request they simply said "it's a usual behavior" - I don't understand what kind of behavior is this.
- API users are counted under users limit - with that of all these limitations I'm not sure why they are counted. It is atleast considerable to a certain extent for counting the license for users with UI access. Why API users?
I'm a developer and I have noticed such things, when I speak with Marketing team they are giving even more such list. Very Strange tool.
Adchoices