HighLevel API
GET /contacts/ removal
Deprecated, no dateSubscribe to HighLevel APIShare
HighLevel API deprecated the GET /contacts endpoint without a shutdown date. Calls made to GET /contacts will fail. HighLevel API documentation notes this endpoint is deprecated and instructs callers to use search instead.
Calls it hits
GET /contacts
What to use instead of these calls
Search contacts with POST /contacts/search instead.
In HighLevel API's words
This API endpoint is deprecated. Please use the Search Contacts endpoint instead.
Facts
- API
- HighLevel API
services.leadconnectorhq.com - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against HighLevel API's own pages
Questions
When does this change take effect?
HighLevel API deprecated GET /contacts without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: HighLevel 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.