Stay organized with collections
Save and categorize content based on your preferences.
This page is intended for customers who are currently using the V2 Alpha version
of the Cloud Support API and would like to migrate to V2 Beta.
Getting started with V2 Beta
If you are already using V2 Alpha then you don't need to do any additional setup
to start using V2 Beta. You can use the same service accounts/credentials and
the API will already be enabled for you.
To call the V2 Beta endpoints, simply replace the /v2alpha/ portion of the
request URL to /v2beta/. For example here's how you would upgrade a
cases.get call from V2 Alpha to V2 Beta:
V2 Alpha:
GET https://cloudsupport.googleapis.com/v2alpha/projects/123/cases/abc
V2 Beta:
GET https://cloudsupport.googleapis.com/v2beta/projects/123/cases/abc
Breaking Changes to Case Classifications
The only behavior that has changed from V2 Alpha to V2 Beta is the
Case Classification
type.
V2 Alpha CaseClassification
Field
Required for case creation
Description
productType
Yes
string The product type
the classification corresponds
to.
value
Yes
string
The classification to be used
when creating a case, e.g.
"Technical Issue > Compute >
Compute Engine"
V2 Beta CaseClassification
Field
Required for case creation
Description
id
Yes
string
The unique ID for a
classification. Must be specified
for case creation.
displayName
No
string The display name
of the classification.
Why did we make these changes?
Removing the productType field
An early design of the API required us to add this field but as the API
evolved it became obsolete.
This field is required but the only valid value is GOOGLE_CLOUD. That
adds boilerplate to every case creation request.
Separating value into id and displayName
The value field in V2 Alpha must be human readable (so that a human
can choose from the list of options) and machine readable (so that our
API can tell what type of case is being created).
V2 Beta separates these concerns into two fields. id is the machine
readable part of the classification, displayName is the human readable
part.
This gives us the flexibility to make changes to the display name without
breaking API integrations. For example, we may want to have multiple
translations of the displayName in the future but the id would stay
the same for all translations since they represent the same case
classification.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Migrating From V2 Alpha\n\nThis page is intended for customers who are currently using the V2 Alpha version\nof the Cloud Support API and would like to migrate to V2 Beta.\n\nGetting started with V2 Beta\n----------------------------\n\nIf you are already using V2 Alpha then you don't need to do any additional setup\nto start using V2 Beta. You can use the same service accounts/credentials and\nthe API will already be enabled for you.\n\nTo call the V2 Beta endpoints, simply replace the `/v2alpha/` portion of the\nrequest URL to `/v2beta/`. For example here's how you would upgrade a\n`cases.get` call from V2 Alpha to V2 Beta:\n\nV2 Alpha:\n`GET https://cloudsupport.googleapis.com/v2alpha/projects/123/cases/abc`\n\nV2 Beta:\n`GET https://cloudsupport.googleapis.com/v2beta/projects/123/cases/abc`\n\nBreaking Changes to Case Classifications\n----------------------------------------\n\n| **Important:** This is the only breaking change between V2 Alpha and V2 Beta. Any endpoints that are not mentioned in this section can safely be migrated to V2 Beta without any changes to the business logic or the request/response format.\n\nThe only behavior that has changed from V2 Alpha to V2 Beta is the\n[Case Classification](/support/docs/reference/rest/v2beta/caseClassifications)\ntype.\n\n### V2 Alpha CaseClassification\n\n### V2 Beta CaseClassification\n\nWhy did we make these changes?\n------------------------------\n\n- Removing the `productType` field\n\n - An early design of the API required us to add this field but as the API evolved it became obsolete.\n - This field is required but the only valid value is `GOOGLE_CLOUD`. That adds boilerplate to every case creation request.\n- Separating `value` into `id` and `displayName`\n\n - The `value` field in V2 Alpha must be human readable (so that a human can choose from the list of options) *and* machine readable (so that our API can tell what type of case is being created).\n - V2 Beta separates these concerns into two fields. `id` is the machine readable part of the classification, `displayName` is the human readable part.\n - This gives us the flexibility to make changes to the display name without breaking API integrations. For example, we may want to have multiple translations of the `displayName` in the future but the `id` would stay the same for all translations since they represent the same case classification."]]
