IBM Cloud Docs
VPC Identity API change log

VPC Identity API change log

Read the API change log to learn about updates and improvements to the IBM Cloud® Virtual Private Cloud (VPC) Identity API. Change log announcements are ordered by the date they were released. Changes to existing API versions are designed to be compatible with existing client applications.

By design, new features with backward-incompatible changes apply only to version dates on and after the feature's release. Changes that apply to older versions of the API are designed to maintain compatibility with existing applications and code. If backward-incompatible changes require non-trivial client code changes to use an API version, the API change log might provide links to instructions, tips, or best practices for updating client code.

Some changes, such as new response properties or new optional request parameters, are considered backward compatible. Other changes, such as new required request parameters, are not considered backward compatible. To avoid disruption from changes to the API, use the following best practices when you call the API:

  • Catch and log any 4xx or 5xx HTTP status code, along with the included trace property
  • Follow HTTP redirect rules for any 3xx HTTP status code
  • Consume only the resources and properties your application needs to function
  • Avoid depending on behavior that is not explicitly documented

26 August 2025

For all version dates

Bare metal server support. You can now access the VPC Identity API from bare metal servers. Use the new create identity token method to create an identity token for your bare metal server, and pass that token to the new create identity certificate method. Alternatively, you can pass that token to the create IAM access token method, and then use that token to access IAM-enabled services. You can also use these new methods from virtual server instances. For more information, see the VPC Identity API.

For version 2025-08-26 or later

Instance identity methods. When using a version query parameter of 2025-08-26 or later, the /instance_identity methods have been removed, and requests will fail with an HTTP response of 404. Clients will need to migrate to the new /identity methods. For more information, see the 2025-08-26 API version migration guide. The behavior remains unchanged when using a version query parameter of 2025-08-25 or earlier from virtual server instances.

For more information, see VPC Identity API known issues.