analytics.eu.amplitude.com
/api/2/lookup_table* endpoint removal
Deprecated, no date
The provider has deprecated the Lookup Tables API without a shutdown date. This deprecation affects calls to /api/2/lookup_table*, noting that this version of the Lookup Tables API is deprecated. Following the change, unsupported requests to this endpoint fail.
Calls it hits
/api/2/lookup_table*
What to use instead of these calls
Call the new Lookup Tables API under /api/3/lookup_table and /api/3/lookup_table/{name} instead.
In analytics.eu.amplitude.com's words
This version of the Lookup Tables API is deprecated
Facts
- API
- analytics.eu.amplitude.com
analytics.eu.amplitude.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against analytics.eu.amplitude.com's own pages
Questions
When does this change take effect?
analytics.eu.amplitude.com deprecated /api/2/lookup_table* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: analytics.eu.amplitude.com 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.