Close API · Endpoint removal
schedule_id on POST /api/v1/sequence/ stops working
Stopped working
Calls to POST /api/v1/sequence, body parameter schedule_id on Close API stopped working on August 29, 2023.
What to use instead of these calls
Send the sequence's sending hours in the schedule object (ranges of weekday, start and end) instead of schedule_id.
Calls it hits
POST /api/v1/sequencebody parameter schedule_id
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
- Endpoint removal
- Announced
- August 29, 2023
- Takes effect
- August 29, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
More from Close API
- schedule_id on PUT /api/v1/sequence/{} stops working Stopped working
- applies_to on POST /api/v1/outcome/ is deprecated Deprecated, no date
- applies_to on PUT /api/v1/outcome/{} is deprecated Deprecated, no date
- is_group_number on GET /api/v1/phone_number/ is deprecated Deprecated, no date
- record_calls on PUT /api/v1/membership/ is deprecated Deprecated, no date
- record_calls on PUT /api/v1/membership/{} is deprecated Deprecated, no date