GET /skadnetwork/conversion-bit-config/v4 → endpoint removal
Airbridge API
Deprecated, no date
The Airbridge API deprecated the endpoint GET /skadnetwork/conversion-bit-config/v4 without a shutdown date. This change affects calls retrieving the SKAN 3.0 Conversion Value Schema. When removed, requests to this endpoint fail.
Calls it hits
GET /skadnetwork/conversion-bit-config/v4
What to use instead of these calls
Call GET /skadnetwork/v1/conversion-value-schema instead to receive the schema response for all versions of SKAN.
In Airbridge API's words
Get SKAN 3.0 Conversion Value Schema (Deprecated)
Facts
- API
- Airbridge API
api.airbridge.io - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Airbridge API's own pages
Questions
When does this change take effect?
Airbridge API deprecated GET /skadnetwork/conversion-bit-config/v4 without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Airbridge 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.