/shortlink/v1/* → version retirement
AppsFlyer OneLink API
Deprecated, no date
AppsFlyer OneLink API deprecated the /shortlink/v1/* endpoints without a shutdown date. Calls made to these endpoints will eventually fail after the v1 sunset.
Calls it hits
/shortlink/v1/*
What to use instead of these calls
Move to OneLink API v2.0 by using POST /api/v2.0/shortlinks/{onelink-id} to create short links, alongside GET, PUT, and DELETE /api/v2.0/shortlinks/{onelink-id}/{shortlink_id}. Update your integration to read the short URL from the shortlink_url JSON field.
In AppsFlyer OneLink API's words
Dual-run is safe during migration. After v1 sunset, only the standard v2.0 quota applies.
Facts
- API
- AppsFlyer OneLink API
onelink.appsflyer.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against AppsFlyer OneLink API's own pages
Questions
When does this change take effect?
AppsFlyer OneLink API deprecated /shortlink/v1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: AppsFlyer OneLink 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.