![]()
api.close.com · MarketingSubscribeShare
Close API breaking changes
The breaking changes Close API announced that Okapi tracks: 9 in all.
Do you run the Close API? Make sure your users call it right →
At a glance
- API host
api.close.com- Kind
- Marketing
- Versions with breaking changes
- v1 (9)
- Breaking changes tracked
- 7 breaking changes with no date yet and 2 already in effect
- Last updated
Deprecated, no date yet 7
-
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/membershipParameter 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
Already in effect 2
-
POST /api/v1/sequenceParameter removal Stopped working -
PUT /api/v1/sequence/{id}Parameter removal 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