Noun Project API
GET /collection/* endpoint removal
Deprecated, no dateSubscribe to Noun Project APIShare
Noun Project API has deprecated GET /collection/* without a shutdown date. Calls to this endpoint will eventually fail as these older V1 endpoints are no longer being updated. Existing callers who previously had access can still reach them, but Noun Project API advises transitioning away.
Calls it hits
GET /collection/*
What to use instead of these calls
Use the v2 collection endpoints, GET /v2/collection/{collection_id} and GET /v2/collection?query= instead.
In Noun Project API's words
Our older V1 API endpoints are still accessible if you previously had access. However, they are no longer being updated and we recommend transitioning to using our newer V2 API endpoints instead.
Facts
- API
- Noun Project API
api.thenounproject.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Noun Project API's own pages
Questions
When does this change take effect?
Noun Project API deprecated GET /collection/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Noun Project 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 Noun Project API 3
-
No date
GET /collectionsEndpoint removal Deprecated, no date -
No date
GET /icon/{id}Endpoint removal Deprecated, no date -
No date
GET /icons/{id}Endpoint 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.