--- title: "Changes to Create Client Token to join a room." method: POST path: "/rooms/{room_id}/actions/generate_join_client_token" --- # Changes to Create Client Token to join a room. `POST /rooms/{room_id}/actions/generate_join_client_token` > Every recorded change to this operation, newest first. > 481 revisions in range; 1 not diffed. ## Timeline Changed in 68 of 481 revisions. - **2025-08-11** `0606a8c47df7`: 1 breaking - **2025-08-11** `5e703a375518`: 1 breaking - **2025-08-11** `45a854866005`: 1 breaking - **2025-08-08** `2e72aa01a5a1`: 1 breaking - **2025-08-08** `7952080be8f8`: 1 breaking - **2025-08-08** `144abaf03f62`: 1 breaking - **2025-08-08** `10aa5bc09ecc`: 1 breaking - **2025-08-07** `d7484a0a7768`: 1 breaking - **2025-08-07** `8e5f0d46ddd6`: 1 breaking - **2025-08-07** `676a368c011d`: 1 breaking - **2025-08-05** `f618a1006b1a`: 1 breaking - **2025-08-05** `51b123d64141`: 1 breaking - **2025-08-04** `5ea2f9679014`: 1 breaking - **2025-08-04** `b027d7073c5b`: 1 breaking - **2025-08-04** `44161174fc15`: 1 breaking - **2025-08-04** `d0bb8be24d5a`: 1 breaking - **2025-08-04** `f60b6a1dffb2`: 1 breaking - **2025-08-04** `b09d804e3ff3`: 4 breaking - **2025-08-04** `441e11d27bba`: 2 breaking - **2025-08-04** `ddc1a62684d2`: 1 breaking - **2025-08-04** `ae0258dceac3`: 2 breaking - **2025-08-04** `9092c0625f49`: 1 breaking - **2025-08-04** `b9a59c2da231`: 3 breaking - **2025-08-01** `9922dcb29641`: 2 breaking - **2025-08-01** `f87271113641`: 2 breaking - **2025-08-01** `61d945742de3`: 2 breaking - **2025-08-01** `99020e181f1c`: 2 breaking - **2025-08-01** `3614a68dc607`: 2 breaking - **2025-07-31** `47ead24182c8`: 2 breaking - **2025-07-30** `13eaae046af7`: 2 breaking - **2025-07-25** `b7607afaef95`: 2 breaking - **2025-07-25** `dd0dfcd94701`: 2 breaking - **2025-07-24** `6ad7361a2335`: 2 breaking - **2025-07-24** `253d9a1bba97`: 2 breaking - **2025-07-23** `1083e5c24d8f`: 2 breaking - **2025-07-16** `b5433e9b6e42`: 2 breaking - **2025-07-15** `34fed4d6b28d`: 2 breaking - **2025-07-15** `67c9fa18d5ef`: 2 breaking - **2025-07-15** `99b0d0af53c6`: 2 breaking - **2025-07-10** `98029c9ccdd5`: 2 breaking - **2025-07-08** `1059b083160b`: 2 breaking - **2025-07-08** `d49a13e1ec17`: 2 breaking - **2025-07-07** `657402475201`: 2 breaking - **2025-07-07** `d671264e7ab5`: 2 breaking - **2025-07-03** `18c5992ca257`: 2 breaking - **2025-07-02** `b443330a00cd`: 2 breaking - **2025-06-23** `0119581e33a2`: 2 breaking - **2025-06-18** `7226f437ab8f`: 2 breaking - **2025-06-16** `8b1f140752a8`: 2 breaking - **2025-06-13** `aa349b5e4339`: 2 breaking - **2025-06-11** `ddadf923b6ba`: 2 breaking - **2025-06-11** `aa66f7810563`: 2 breaking - **2025-06-10** `62260d173b5c`: 2 breaking - **2025-06-06** `9b438170c3e3`: 2 breaking - **2025-06-05** `fec78497a29c`: 2 breaking - **2025-05-30** `327879eacdce`: 2 breaking - **2025-05-30** `90828937296e`: 2 breaking - **2025-05-29** `17abfd3dff7f`: 2 breaking - **2025-05-28** `791d7881f441`: 2 breaking - **2025-05-19** `bc6f864ef109`: 2 breaking - **2025-05-16** `3e6a843c2384`: 2 breaking - **2025-05-15** `9208fd474108`: 2 breaking - **2025-05-15** `c88d7bf12b55`: 2 breaking - **2025-05-15** `37b02053ba34`: 2 breaking - **2025-05-12** `6b24ee9b38e0`: 2 breaking - **2025-05-12** `8176ac23b7da`: 2 breaking - **2025-05-12** `2e524bf22313`: 2 breaking - **2025-05-09** `97c980038c87`: 2 breaking ## Changes - **2025-08-11** `0606a8c47df7`: 1 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - **2025-08-11** `5e703a375518`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-11** `45a854866005`: 1 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - **2025-08-08** `2e72aa01a5a1`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-08** `7952080be8f8`: 1 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - **2025-08-08** `144abaf03f62`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-08** `10aa5bc09ecc`: 1 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - **2025-08-07** `d7484a0a7768`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-07** `8e5f0d46ddd6`: 1 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - **2025-08-07** `676a368c011d`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-05** `f618a1006b1a`: 1 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - **2025-08-05** `51b123d64141`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-04** `5ea2f9679014`: 1 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - **2025-08-04** `b027d7073c5b`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-04** `44161174fc15`: 1 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - **2025-08-04** `d0bb8be24d5a`: 1 breaking - the `source/pointer` response's property format changed from `json-pointer` to no format for status `403` - **2025-08-04** `f60b6a1dffb2`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-04** `b09d804e3ff3`: 4 breaking - the `data/refresh_token` response's property format changed from `jwt` to no format for status `201` - the `data/refresh_token_expires_at` response's property format changed from `datetime` to `date-time` for status `201` - the `data/token` response's property format changed from `jwt` to no format for status `201` - the `data/token_expires_at` response's property format changed from `datetime` to `date-time` for status `201` - **2025-08-04** `441e11d27bba`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `403` - **2025-08-04** `ddc1a62684d2`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-04** `ae0258dceac3`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `403` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `403` - **2025-08-04** `9092c0625f49`: 1 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `403` - **2025-08-04** `b9a59c2da231`: 3 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property format changed from `int` to no format for status `403` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `403` - **2025-08-01** `9922dcb29641`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-08-01** `f87271113641`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-08-01** `61d945742de3`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-08-01** `99020e181f1c`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-08-01** `3614a68dc607`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-07-31** `47ead24182c8`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-07-30** `13eaae046af7`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-07-25** `b7607afaef95`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-07-25** `dd0dfcd94701`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-07-24** `6ad7361a2335`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-07-24** `253d9a1bba97`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-07-23** `1083e5c24d8f`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-07-16** `b5433e9b6e42`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-07-15** `34fed4d6b28d`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-07-15** `67c9fa18d5ef`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-07-15** `99b0d0af53c6`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-07-10** `98029c9ccdd5`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-07-08** `1059b083160b`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-07-08** `d49a13e1ec17`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-07-07** `657402475201`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-07-07** `d671264e7ab5`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-07-03** `18c5992ca257`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-07-02** `b443330a00cd`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-06-23** `0119581e33a2`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-06-18** `7226f437ab8f`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - **2025-06-16** `8b1f140752a8`: 2 breaking - the response's body type changed from no type to `object` for status `403` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `403` - **2025-06-13** `aa349b5e4339`: 2 breaking - the response's body type changed from `object` to no type for status `403` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `403` - …earlier changes are on the page: https://skmtc.dev/team-telnyx/apis/telnyx-api-2/changes/rooms/:room_id/actions/generate_join_client_token/post --- [Operation](https://skmtc.dev/team-telnyx/apis/telnyx-api-2/docs/rooms/:room_id/actions/generate_join_client_token/post.md) - [API](https://skmtc.dev/team-telnyx/apis/telnyx-api-2.md) - [Page](https://skmtc.dev/team-telnyx/apis/telnyx-api-2/changes/rooms/:room_id/actions/generate_join_client_token/post)