/v1/* → version retirement
Dyte API
Deprecated, no date
Dyte has deprecated its v1 REST API endpoints without a shutdown date. Calls made to /v1/* will eventually fail once the provider discontinues the version. Support for v1 continues for the near future, but the provider advises moving to the new version.
Calls it hits
/v1/*
What to use instead of these calls
Migrate your integration to the v2 REST API using Basic authentication with your organization id as username and API key as password. In v2, presets are configured per participant.
In Dyte API's words
We highly recommend that you start migrating to v2, as v1 will eventually be discontinued. However, rest assured that support for v1 will still be provided for the near future.
Facts
- API
- Dyte API
api.dyte.io - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Dyte API's own pages
Questions
When does this change take effect?
Dyte API deprecated /v1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Dyte 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.