Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

legacy api deprecation notice #2461

Merged
merged 4 commits into from
Jan 15, 2025
+1 −1
Merged

legacy api deprecation notice #2461

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3eb4223
legacy api deprecation notice
aakashbajaj Jan 6, 2025
a2b5804
Revert "legacy api deprecation notice"
aakashbajaj Jan 9, 2025
820ec8d
deprecate room API
aakashbajaj Jan 9, 2025
8b980c1
Merge branch 'main' into legacy-api-deprecation
sandeep-100ms Jan 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Revert "legacy api deprecation notice" 
This reverts commit 3eb4223.
@aakashbajaj
aakashbajaj committed Jan 9, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode
commit a2b580448c96c2475a1e3d3bd4afad3e0412964a
2 changes: 1 addition & 1 deletion docs/server-side/v2/api-reference/legacy-api-v1/room.mdx
View file
Original file line number Diff line number Diff line change
@@ -3,7 +3,7 @@ title: Room
nav: 4.1
---

> **Note**: The Legacy API (V1) will remain functional until June 30, 2025, after which it will be deprecated. We strongly recommend migrating to our [new API](/server-side/v2/Rooms/overview) to leverage new functionalities and features and stay up to date with future releases. You can continue to check the docs for the Legacy API (V1) [here](</server-side/v2/legacy-api%20(v1)/templates-and-roles>) until the deprecation date.
> **Note**: The Legacy API (V1) will remain fully functional. However, we recommend you use our [new API](/server-side/v2/Rooms/overview) to leverage the new functionalities and features and stay up to date with future releases; you can continue to check the docs for the Legacy API (V1)s [here](</server-side/v2/legacy-api%20(v1)/templates-and-roles>).

## Create Room using API

2 changes: 1 addition & 1 deletion docs/server-side/v2/api-reference/legacy-api-v1/session.mdx
View file
Original file line number Diff line number Diff line change
@@ -3,7 +3,7 @@ title: Session
nav: 4.2
---

> **Note**: The Legacy API (V1) will remain functional until June 30, 2025, after which it will be deprecated. We strongly recommend migrating to our [new API](/server-side/v2/Sessions/object) to leverage new functionalities and features and stay up to date with future releases. You can continue to check the docs for the Legacy API (V1) [here](</server-side/v2/legacy-api%20(v1)/templates-and-roles>) until the deprecation date.
> **Note**: The Legacy API (V1) will remain fully functional. However, we recommend you use our [new API](/server-side/v2/Sessions/object) to leverage the new functionalities and features and stay up to date with future releases; you can continue to check the docs for the Legacy API (V1)s [here](</server-side/v2/legacy-api%20(v1)/templates-and-roles>).

## Overview

2 changes: 1 addition & 1 deletion docs/server-side/v2/api-reference/legacy-api-v1/templates-and-roles.mdx
View file
Original file line number Diff line number Diff line change
@@ -3,7 +3,7 @@ title: Templates and Roles
nav: 4.3
---

> **Note**: The Legacy API (V1) will remain functional until June 30, 2025, after which it will be deprecated. We strongly recommend migrating to our [new API](/server-side/v2/policy/template-object) to leverage new functionalities and features and stay up to date with future releases. You can continue to check the docs for the Legacy API (V1) [here](</server-side/v2/legacy-api%20(v1)/templates-and-roles>) until the deprecation date.
> **Note**: The Legacy API (V1) will remain fully functional. However, we recommend you use our [new API](/server-side/v2/policy/template-object) to leverage the new functionalities and features and stay up to date with future releases; you can continue to check the docs for the Legacy API (V1)s [here](/server-side/v2/api-reference/legacy-api-v1/templates-and-roles).

## Create Template API