Merge pull request #790 from teamleadercrm/feature/ticket_cloud_platf…

…orm_url

Add ticket as a supported type for the cloudPlatforms.url endpoint.

apiary.apib

@@ -428,6 +428,7 @@ We list all backwards-compatible additions here. These are currently available i
 
 #### February 2024
 - We added the `tickets.importMessage`, `tickets.addReply` and `tickets.addInternalMessage` endpoints.
+- We now support `ticket` as a valid `type` on the `cloudPlatforms.url` endpoint.
 
 #### January 2024
 - We renamed `task_type` and `task_type_id` to `work_type` and `work_type_id` in `projects-v2/tasks.list`, `projects-v2/tasks.info`, `projects-v2/tasks.create` and `projects-v2/tasks.update`. The old names are still supported, but deprecated.
@@ -8787,6 +8788,7 @@ Fetch cloudPlatform url for type and id
             + Members
                 + invoice
                 + quotation
+                + ticket
         + id: `b7023c11-455e-4fa5-bb96-87f37dbc7d07` (string, required)
 
 + Response 200 (application/json)

src/99-other/cloud-platforms.apib

@@ -12,6 +12,7 @@ Fetch cloudPlatform url for type and id
             + Members
                 + invoice
                 + quotation
+                + ticket
         + id: `b7023c11-455e-4fa5-bb96-87f37dbc7d07` (string, required)
 
 + Response 200 (application/json)

src/changes-backwards-compatible.apib

@@ -6,6 +6,7 @@ We list all backwards-compatible additions here. These are currently available i
 
 #### February 2024
 - We added the `tickets.importMessage`, `tickets.addReply` and `tickets.addInternalMessage` endpoints.
+- We now support `ticket` as a valid `type` on the `cloudPlatforms.url` endpoint.
 
 #### January 2024
 - We renamed `task_type` and `task_type_id` to `work_type` and `work_type_id` in `projects-v2/tasks.list`, `projects-v2/tasks.info`, `projects-v2/tasks.create` and `projects-v2/tasks.update`. The old names are still supported, but deprecated.