RocketReach API
api_key query parameter removal on /api/v2/*
Deprecated, no dateSubscribe to RocketReach APIShare
RocketReach API has deprecated the api_key query parameter across /api/v2/* endpoints without a shutdown date. Calls passing this query parameter instead of using headers will eventually fail. RocketReach API notes that authenticating via this query parameter is legacy behavior.
Calls it hits
/api/v2/*query parameter api_key
What to use instead of these calls
Send the key in the Api-Key request header instead of passing the api_key query parameter.
In RocketReach API's words
Requests to the API are authenticated using the Api-Key request header. Older clients may use an `api_key` query parameter, but this behavior is deprecated.
Facts
- API
- RocketReach API
api.rocketreach.co - Kind
- Parameter removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against RocketReach API's own pages
Questions
When does this change take effect?
RocketReach API deprecated /api/v2/*, query parameter api_key without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: RocketReach 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 RocketReach API 1
-
No date
GET /api/v2/person/lookupParameter 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.