Hi.
Couple questions about REST API "merge".
Thank you for your help.
Solved! Go to Solution.
Also, I'd recommend you to play around a bit using test records first, before trying this API call on your prod leads, you might not want to select wring lead as winning record in Marketo, as in case of conflicting values, the ones in the winning record always take precendence and is persisted. Hope this is helpful. Let us know if you have any questions.
1. Yes, you must use the ID. (It’s the only identifier that makes sense.)
2. The numeric Lead ID.
3a. I wouldn’t use the word “file” as we usually reserve that for downloadable assets. “Person record” would be more widely understood.
3b. Only one Marketo lead will have a given Lead ID. So no, it’s not merging records with the same Lead ID. It’s merging all records that have the losing Lead IDs into the one record that has the winning Lead ID. Much as you can do in the Marketo UI by selecting 2 people in the database.
4. No, I don’t think you quite understand what the API endpoint is doing. It’s merging entire records, where filled fields win over empty fields.
5. A date range doesn’t make sense in this context. What would it be filtering?
6. If you’re prohibited from using Postman, you should not be using this endpoint as it’s clear that your company doesn’t want you using the API, period.
I think using the URL bar will always result in a GET. To send POST requests from a browser, set up an HTML <form> with method="POST", use the action attribute for the REST-URL and input tags for other parameters.
That won’t work, because the REST API (correctly) won’t accept cross-origin requests. You’d have to launch your browser in relaxed CORS mode.
Like we both said, if you’re not allowed to use Postman, it doesn’t make sense that you can use a browser. Surely if IT says “no API use” they don’t want you working around that. (Though not clear how why you would have access to API credentials but not be allowed to use them.)
Thanks for confirming, Sandy! Appreciate it. Also, yes, if OP’s org doesn't allow using API platforms like Postman, then instead of thinking of workarounds for making API calls using browser, etc., they should get the permission the right way from their IT. 🙂
Also, I'd recommend you to play around a bit using test records first, before trying this API call on your prod leads, you might not want to select wring lead as winning record in Marketo, as in case of conflicting values, the ones in the winning record always take precendence and is persisted. Hope this is helpful. Let us know if you have any questions.
I think using the URL bar will always result in a GET. To send POST requests from a browser, set up an HTML <form> with method="POST", use the action attribute for the REST-URL and input tags for other parameters.
That won’t work, because the REST API (correctly) won’t accept cross-origin requests. You’d have to launch your browser in relaxed CORS mode.
Like we both said, if you’re not allowed to use Postman, it doesn’t make sense that you can use a browser. Surely if IT says “no API use” they don’t want you working around that. (Though not clear how why you would have access to API credentials but not be allowed to use them.)
Thanks for confirming, Sandy! Appreciate it. Also, yes, if OP’s org doesn't allow using API platforms like Postman, then instead of thinking of workarounds for making API calls using browser, etc., they should get the permission the right way from their IT. 🙂
1. Yes, you must use the ID. (It’s the only identifier that makes sense.)
2. The numeric Lead ID.
3a. I wouldn’t use the word “file” as we usually reserve that for downloadable assets. “Person record” would be more widely understood.
3b. Only one Marketo lead will have a given Lead ID. So no, it’s not merging records with the same Lead ID. It’s merging all records that have the losing Lead IDs into the one record that has the winning Lead ID. Much as you can do in the Marketo UI by selecting 2 people in the database.
4. No, I don’t think you quite understand what the API endpoint is doing. It’s merging entire records, where filled fields win over empty fields.
5. A date range doesn’t make sense in this context. What would it be filtering?
6. If you’re prohibited from using Postman, you should not be using this endpoint as it’s clear that your company doesn’t want you using the API, period.