/partners/publisher/instances/* → version retirement
ironSource LevelPlay API
Deprecated, no date
Legacy versions 3 and below are deprecated as of March 2025 without a specified shutdown date. The deprecation applies to calls targeting /partners/publisher/instances/* endpoints. Once retired, requests sent to these legacy endpoints fail.
Calls it hits
/partners/publisher/instances/*
What to use instead of these calls
Switch to Instances API v4 using GET, POST, PUT, and DELETE operations on the new network instances v4 endpoints.
In ironSource LevelPlay API's words
API versions 3 and below are deprecated as of March 2025
Facts
- API
- ironSource LevelPlay API
platform.ironsrc.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against ironSource LevelPlay API's own pages
Questions
When does this change take effect?
ironSource LevelPlay API deprecated /partners/publisher/instances/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: ironSource LevelPlay 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.