Welcome to the Taboola Backstage API documentation. You'll find comprehensive guides and examples to help you get started with Taboola Backstage API quickly.
When trying to submit PATCH operation to add 20 publisher blocks (for example), we receive an error response if one publisher is already blocked. That means in order to avoid an error, we need to request the current block list, check it against the new batch of publisher blocks, and only submit unique publishers. In that case, it does not seem helpful to use PATCH. We might as well just GET the blocks and POST the entire list. Am I missing something here? Why would Taboola's practice be to error, instead of simply skipping over duplicates?
Posted by Mike 8 months ago
Some sites cannot be blocked through API: 1317418 caras.com.mx 1316462 levante-emv.com 1316357 dailystar.co.uk 1315252 musicmundial.com We are using the PATCH endpoint: https://backstage.taboola.com/backstage/api/1.0/{account}/campaigns/{campaign} API response is (404): { "http_status": 404, "message": "account" } Can you help checking why this happens?
Posted by Pirouzn Nilforoush 9 months ago
I want to use the patch modify bids endpoint to change bids and strategies on certain sites, and I would want to change the bid occusainly, how could I know when to use `ADD` and when to use `REPLACE` as a `patch_operation`? I would usually patch multiple sites at once so I don't want to send a GET request for every site.
Posted by Abdallah AlHalees 9 months ago