Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > RightScale API 1.5 > Overview > API Version 1.0 to 1.5 Differences

API Version 1.0 to 1.5 Differences

Table of Contents
No headers


If you are already familiar with the RightScale API version 1.0, see the following list  for a summary of the important differences between API version 1.0 and 1.5:

  • Basic Authentication - Basic Authentication is not supported in API 1.5.  (It was in version API 1.0.  See the Login and Headers section of this guide for more information.)
  • Improved Error Handling - Includes a more detailed and descriptive message for troubleshooting purposes (See Error Handling.)
  • Identifiers (IDs) - API 1.0 used numeric IDs to identify resources or passing them as parameters. API 1.5 uses resource hrefs. All relationships are expressed as resource hrefs. The href of a resource is its unique and immutable ID in perpetuity.  (See HREFs and IDs section.)
  • Login Semantics - An API 1.5 session is now bound to a given RightScale account and not to an authenticated RightScale user as in API 1.0. Hence the login call must specify which account to log into.  (See Login and Headers.)
  • Server, Server Array and Instance Semantics - The semantics of servers with respect to instances has been refactored and is much cleaner and precise in version 1.5. In API 1.5 a server will always have a "next instance" and (if running) a "current instance".  API 1.0 did not support the notion of a "next instance".   (See Servers and Instances.)

You must to post a comment.
Last modified
10:22, 1 May 2014



This page has no classifications.



© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.