/backstage/api/1.0/{}/campaigns/{}/performance-video/* → endpoint removal
Taboola Backstage API
Deprecated, no date
Taboola deprecated the motion-specific /backstage/api/1.0/{}/campaigns/{}/performance-video/* endpoints without announcing a shutdown date. Calls made to these endpoints fail as part of this removal. The change affects integrations relying on these performance video paths rather than the standard unified endpoints.
Calls it hits
/backstage/api/1.0/{}/campaigns/{}/performance-video/*
What to use instead of these calls
Use the unified campaign item endpoints instead, specifically /backstage/api/1.0/{account_id}/campaigns/{campaign_id}/items/ for get, update, and delete actions, or the bulk and mass create items endpoints.
In Taboola Backstage API's words
The following motion-specific endpoints have been deprecated. Use the unified endpoints instead.
Facts
- API
- Taboola Backstage API
backstage.taboola.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Taboola Backstage API's own pages
Questions
When does this change take effect?
Taboola Backstage API deprecated /backstage/api/1.0/{}/campaigns/{}/performance-video/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Taboola Backstage API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.