![]()
api.close.com · Marketing
Close API breaking changes
The breaking changes Close API announced that Okapi tracks: 9 in all.
Deprecated, no date yet 7
- No date applies_to on POST /api/v1/outcome/ is deprecated Deprecated, no date
- No date applies_to on PUT /api/v1/outcome/{} is deprecated Deprecated, no date
- No date is_group_number on GET /api/v1/phone_number/ is deprecated Deprecated, no date
- No date record_calls on PUT /api/v1/membership/ is deprecated Deprecated, no date
- No date record_calls on PUT /api/v1/membership/{} is deprecated Deprecated, no date
- No date sharing on POST /api/v1/phone_number/request/internal/ is deprecated Deprecated, no date
- No date user_id on GET /api/v1/phone_number/ is deprecated Deprecated, no date
Already in effect 2
- schedule_id on POST /api/v1/sequence/ stops working Stopped working
- schedule_id on PUT /api/v1/sequence/{} stops working Stopped working
Where Okapi reads it
- Changelog developer.close.com/changelog
- OpenAPI spec api.close.com/api/openapi.json
- Announcement developer.close.com/api/overview/changelog/2023/8/29
- Announcement developer.close.com/api/overview/changelog/2024/12/2
- Announcement developer.close.com/api/overview/changelog/2026/3/6
- Announcement developer.close.com/api/overview/changelog/2026/7/21
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub