Close API
record_calls body parameter removal on PUT /api/v1/membership
Deprecated, no dateSubscribe to Close APIShare
The boolean record_calls body parameter on PUT /api/v1/membership has been deprecated without a shutdown date. Calls that rely on this parameter will eventually fail once it is removed.
Calls it hits
PUT /api/v1/membershipbody parameter record_calls
What to use instead of these calls
Send auto_record_calls with a value of 'enabled' or 'disabled' instead of record_calls.
In Close API's words
The boolean record_calls field on the Membership API has been deprecated in favor of auto_record_calls
Facts
- API
- Close API
api.close.com - Kind
- Parameter removal
- Announced
- December 2, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Close API's own pages
Questions
When does this change take effect?
Close API deprecated PUT /api/v1/membership, body parameter record_calls without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Close 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 Close API 8
-
POST /api/v1/sequenceParameter removal Stopped working -
PUT /api/v1/sequence/{id}Parameter removal Stopped working -
No date
POST /api/v1/outcomeParameter removal Deprecated, no date -
No date
PUT /api/v1/outcome/{id}Parameter removal Deprecated, no date -
No date
GET /api/v1/phone_numberParameter removal Deprecated, no date -
No date
PUT /api/v1/membership/{id}Parameter removal Deprecated, no date -
No date
POST /api/v1/phone_number/request/internalParameter removal Deprecated, no date -
No date
GET /api/v1/phone_numberParameter 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.