Roles versioning

Author: tomhamiltonstubber

pages/api.yml

@@ -29,9 +29,9 @@ info_sections:
     id: pagination
     layout: /pagination/pagination.yml
   -
-    title: Versioning
-    id: versioning
-    layout: /versioning/versioning.yml
+    title: Roles Versioning
+    id: roles_versioning
+    layout: /roles_versioning/roles_versioning.yml
 
 endpoint_sections:
   -

pages/versioning/versioning.md renamed to pages/roles_versioning/roles_versioning.md

@@ -2,7 +2,7 @@
 
 ### Zapier changes
 Mostly things should be just about the same, some IDs may look different inside Zapier but the data should be the same.
-This should appear as IDs being required to Update a user and the User layer in requests and responses being removed.
+This should appear as IDs being required to Update a Role and the Role layer in requests and responses being removed.
 
 For moving from V1 to V2 of API, the best practice is to follow the following steps.
 
@@ -39,4 +39,4 @@ but the data we return will be dependent on the version set on your Branch. See
 * Delete: Use a DELETE request to the detail page for an individual role (e.g. `secure.tutorcruncher.com/api/clients/<role_id>/`)
 
 Note that the rest of the docs have been updated to reflect Version 2 usage. While you can still use Version 1 until the 3rd July 2025
-we recommend that your refrain from doing so and update your integrations to use Version 2 as soon as possible.
+we recommend that your refrain from doing so and update your integrations to use Version 2 as soon as possible.

pages/versioning/versioning.py renamed to pages/roles_versioning/roles_versioning.py

@@ -0,0 +1,5 @@
+sections:
+  -
+    description: /roles_versioning/roles_versioning.md
+    code: /roles_versioning/roles_versioning.py
+    code_type: Role Versioning