GET /analytics → endpoint removal
Dub API
Deprecated, no date
Dub API deprecated the query parameter qr on GET /analytics without a shutdown date. Calls continuing to use this parameter will fail. The change affects requests filtering specifically for QR code scans.
Calls it hits
GET /analyticsquery parameter qr
What to use instead of these calls
Filter with trigger=qr or trigger=link instead of using qr=true or qr=false.
In Dub API's words
Deprecated: Use the trigger field instead. Filter for QR code scans.
Facts
- API
- Dub API
api.dub.co - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Dub API's own pages
Questions
When does this change take effect?
Dub API deprecated GET /analytics, query parameter qr without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Dub 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.
More from Dub API 1
-
No date
GET /analyticsEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.