Open Xdrive: JSON API Version 1.2 Change Notes

The primary focus of this revision is on supporting different types of requests, where the information necessary to invoke methods can be provided using HTTP headers, JSON messages, Cookies, the URL, form data, multipart data, etc.
If you are currently using version 1.1 of the XDSP JSON API and would like to migrate to the new version, please check out the Version Migration section in the Getting Started Guide.

Improved Authentication



• AOL ®/AIM Screen Name or email address Support
  The member.login method now supports all users, so you can authenticate to the service with an AOL ®/AIM Screen Name or your email address. Because you are passing credentials over the wire, this method requires HTTPS now.
  
  
• OpenAuth Support
  The API now supports OpenAuth open identification system. member.aollogin accepts an OpenAuth token as a credential, allowing you to login your already authenticated users to the Xdrive JSON API.

New Functions



• Publishing
  New functions file.publish and file.unpublish allow developers to create and remove permalink URLs for assets stored in Xdrive.
  
  
• AOL Address Book Access
  contact.getaollisting allows developers to fetch contact information from the AOL address book. These addresses can be used for share and permission management. If AOL doesn't have the contact you need? Add it via contact.newaolcontact.
  
  
• Zipped File Transfers
  Use io.zipdownload and io.zipupload to transfer files in a compressed zip stream to save bandwidth and time.

Expanded HTTP Support



• Request IDs
  You can now optionally pass in a pass-back ID with each request, using the id field. This id will be returned with the response to the request. This simplifies client-side tracking, especially when dealing with multiple requests.
  
  
• Command Chaining
  With command chaining, multiple method invocations can be sent using a single HTTP POST. Command chaining is implemented using multipart requests.

Expanded Options



• quota
  If true, include the quota (UserQuotaObject) in the response.
  
  
• sparse
  If true, only the sparse version of the object is sent in the response. Basically, this means only the "id" field is populated, instead of including the rest of the object's variables.
  
  
• onlydata
  If true, do not send back a response or exceptions, just data. If the call fails, a 500 status code will be set in the response. Defaults to false, except for downloads.
  
  
• failonerror
  If true, abort the entire request if a part fails. Otherwise, continue processing the request when an error occurs.
  
  
• quiet
  If true, do not send back a response. Exceptions will be sent.