POST /v2/connections/{} → endpoint removal
IFTTT Connect API
Deprecated, no date
The provider deprecated the POST /v2/connections/{} endpoint without a shutdown date. Calls made to this route are marked for removal and will fail. Affected requests should be transitioned away from this path to avoid disruptions.
Calls it hits
POST /v2/connections/{}
What to use instead of these calls
Update the user's connection with PUT /v2/connections/{connection_id}/user_connection instead.
In IFTTT Connect API's words
Endpoint has been deprecated. Please use the new Update a Connection endpoint
Facts
- API
- IFTTT Connect API
connect.ifttt.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against IFTTT Connect API's own pages
Questions
When does this change take effect?
IFTTT Connect API deprecated POST /v2/connections/{} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: IFTTT Connect 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.