Close API
schedule_id body parameter removal on POST /api/v1/sequence
Stopped workingSubscribe to Close APIShare
On August 29, 2023, the schedule_id body parameter was removed from POST /api/v1/sequence. Requests including this parameter fail after that date. The change took effect immediately upon its announcement.
Calls it hits
POST /api/v1/sequencebody parameter schedule_id
What to use instead of these calls
Send the sequence's sending hours in the schedule object, defining ranges of weekday, start, and end, instead of schedule_id.
In Close API's words
We have added a new schedule field and removed the existing schedule_id field in the Sequence API.
Facts
- API
- Close API
api.close.com - Kind
- Parameter removal
- Announced
- August 29, 2023
- Takes effect
- August 29, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Close API's own pages
Questions
When does this change take effect?
Calls to POST /api/v1/sequence, body parameter schedule_id on Close API stopped working on August 29, 2023.
What happens to calls after August 29, 2023?
They have failed since August 29, 2023.
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
-
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/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
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.