GET /api/v1/typed_custom_fields → endpoint removal
Apollo API
Deprecated, no date
The provider has deprecated the GET /api/v1/typed_custom_fields endpoint without announcing a shutdown date. Calls made to this route will eventually fail. The provider notes that this endpoint is deprecated and instructs callers to use an alternative endpoint instead.
Calls it hits
GET /api/v1/typed_custom_fields
What to use instead of these calls
Call GET /api/v1/fields with source: custom to list the custom fields.
In Apollo API's words
This endpoint is deprecated. To achieve the same result, use the fields endpoint
Facts
- API
- Apollo API
api.apollo.io - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Apollo API's own pages
Questions
When does this change take effect?
Apollo API deprecated GET /api/v1/typed_custom_fields without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Apollo 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.