Community Discussion
404 calling campaigns/base
I'm currently developing an api loader and following these 3 api calls to gather daily campaign stats for our account.
1. https://backstage.taboola.com/backstage/api/1.0/users/current/allowed-accounts
2. https://backstage.taboola.com/backstage/api/1.0/<account id from 2>/campaigns/base?start
3. https://backstage.taboola.com/backstage/api/1.0/<network-account-id>/reports/campaign-summary/dimensions/day?start_date=<start date>&end_date=<end date>&campaign=<campaginID from 3>
I'm currently getting 404 errors making a call to campaigns/base for some of the "type": "PARTNER" accounts but not for others.
Can you please give any insights as to how an account has to be setup for the campaigns/base url to function correctly?
Posted by John B almost 2 years ago
Filtering Inactive subaccounts
Hello,
We are currently pulling campaign data using the backstage api and are receiving a 403 response for specific accounts.
Our current process is the following:
1. Get the account_ids by making the GET request to https://backstage.taboola.com/backstage/api/1.0/users/current/allowed-accounts
2. Get the campaigns by making the GET request to
https://backstage.taboola.com/backstage/api/1.0/{account_id}/campaigns/
After some troubleshooting on our end, we see that the accounts that are giving us the 403 error, are actually inactive in the backstage ui. We would like to know if there is a way to filter out the inactive accounts via the API?
Posted by Rene over 2 years ago
why isn't fetching user allowed accounts documented in the online docs?
I see it in the retired documntation on github https://github.com/taboola/Backstage-API/blob/master/Backstage%20API%20-%20Users.pdf but it's not documented here, is it deprecated?
Posted by Abdallah AlHalees over 3 years ago