Creating a new API session

To begin using the API, request the system to create a session object. In this request, supply your credentials in an authorization header of the form prescribed by the identity provider that your organization uses. The response includes an authorization token, which you must include in subsequent requests.
 

Every version of the vCloud API supported by VMware Cloud Director has a login URL that a client can obtain by making an unauthenticated GET request to the API/versions URL. See example: Retrieve the Login URL and List of Supported API Versions. Because all other vCloud API requests must be authenticated, any vCloud API workflow must begin with a login request that creates a session and returns an authorization token in the value of the x-vcloud-authorization header. The token must be included in subsequent vCloud API requests.
 

To create a session object, supply your credentials in an authorization header of the form prescribed by the identity provider that your organization uses, then POST a request to the vCloud API login URL. This request does not have a body. All the information required to create a session is included in the authorization header.

• Create a new session with the vCD endpoint, using the following:
  
  
  • Header: Authorization = Basic (username: username@org)
  • Header: Accept = application/vnd.vmware.vcloud.session+xml;version=27.0 (your version # will vary)
  • Method: POST
  • URL: https://yourLPCurl/api/sessions
     

Response: The response header includes a re-usable x-vcloud-authorization authorization token and a session element whose link elements reference the vCloud API objects to which you have access rights.
 

• Be sure to note the return header with key name x-vcloud-authorization. This will include a unique session hex number for this header, e.g. 117a0c919f9f4fa5975306d2a7831d95.
• This header, including the token, must be included in each subsequent vCloud API request.
• If the authorization header is missing from the request, the server returns HTTP response code 403.
• If the credentials supplied in the authorization header are invalid, the server returns HTTP response code 401.