# Migration to Confluence REST API v2 - Question about deprecated endpoints

**URL:** <https://community.developer.atlassian.com/t/migration-to-confluence-rest-api-v2-question-about-deprecated-endpoints/77323>\
**Category:** Confluence Cloud\
**Tags:** rest-api\
**Created:** [February 15, 2024, 9:32am UTC](https://community.developer.atlassian.com/t/migration-to-confluence-rest-api-v2-question-about-deprecated-endpoints/77323 "2024-02-15T09:32:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Corentin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/corentin/32/50121_2.png) [@Corentin](https://community.developer.atlassian.com/u/Corentin)\
**Post date:** [February 15, 2024, 9:52am UTC](https://community.developer.atlassian.com/t/migration-to-confluence-rest-api-v2-question-about-deprecated-endpoints/77323/2 "2024-02-15T09:52:24Z")

</div>

Hi Krystian.

1. You only need to migrate the marked deprecated endpoints. For instance, the /search and the /users endpoints are not deprecated.
2. The current deadline is (at least) June 2024, announced in [Confluence REST API v2: Update to v1 Deprecation Timeline](https://community.developer.atlassian.com/t/confluence-rest-api-v2-update-to-v1-deprecation-timeline/75126)

---

_[View the full topic](https://community.developer.atlassian.com/t/migration-to-confluence-rest-api-v2-question-about-deprecated-endpoints/77323)._
