ARCore 1.33 Cloud Anchor endpoint changes

As of the August 2022 1.33.0 release, the ARCore Cloud Anchor API endpoint is deprecated. All apps built with ARCore SDK 1.33.0 and higher now target the new ARCore API, general-purpose API intended for use with all ARCore cloud services. All apps built with ARCore SDK 1.32.0 and lower will continue to target the older API.

This change will not affect existing data. Once an app is updated to use ARCore SDK 1.33.0 or later, and the new ARCore API has been enabled in the Google Cloud project used by your app, functionality should remain the same as it did when using the previous end point. To support older app versions, you may enable both APIs while making the transition.

If your app uses the Cloud Anchors API, you must update it to use ARCore SDK 1.33.0 or later before August 31, 2023. After this date, apps compiled with ARCore SDK 1.32.0 or earlier will no longer be able to host and resolve Cloud Anchors.

Naming changes

Previous New
API name ARCore Cloud Anchor API ARCore API
Domain name

Update your app to use the new endpoint

To update your app:

  1. Visit the Google Cloud Platform console.
  2. Determine which cloud project your app uses.
  3. Ensure that the ARCore API is enabled.
  4. Update your app to use the latest ARCore SDK. ARCore SDK 1.33 and later use the new ARCore API.
  5. Test these changes by using Cloud Anchor API functionality in your app.
  6. Verify that the Cloud Anchor API usage for the updated app appears under the ARCore API in the Google Cloud project, and not under the ARCore Cloud Anchor API.

Update app settings

  • If your iOS app is using signed JWTs for authorization, change the audience claim to for apps built with ARCore SDK 1.33.0 and higher.
  • If your API key is restricted, you must allow the ARCore API.
  • If you send requests to the ARCore Cloud Anchor Management API from your backend, you must enable the ARCore API and change the domain name to