REST APIs

IDrive EVS REST APIs: Development now made easy!

Events


1. Get Events:

Retrieve details of all events within a specified time period like Upload, Download, Rename, Delete etc., in your IDrive account using the getEvents API.

Quick links

Syntax for 'getEvents' API:

https://<server address>/evs/getEvents

Server address:
Use
getServerAddress API to retrieve the IDrive server address.

HTTP method: POST
Input parameters:
uid username or email address
pwd password
month month of the events
year year of the events

Output:
Below is a sample XML output generated when you call ‘getEvents’ API:
<?xml version="1.0" encoding="UTF-8"?>
<tree message="SUCCESS" eventcount="7">
<item event="Download" date="2011/08/28" id="RES20110828"/>
<item event="Upload" date="2011/08/29" id="BCK20110829"/>
<item event="Delete" date="2011/08/26" id="DEL20110826"/>
<item event="Copy n Paste" date="2011/08/29" id="CPW20110829"/>
<item event="Rename" date="2011/08/29" id="RNM20110829"/>
</tree>

Description:
  • tree
    Root node with attributes message.
  • message
    This attribute describes the operation as SUCCESS or FAIL.
  • item
    Item node with attributes event,date,id
  • event
    name of the event.
  • date
    date of the event
  • id
    event id

Following cases explain the expected outputs during INVALID operations:
  • Case 1: Empty Username or Password

    The output is as follows:
    <tree message="ERROR" desc="INVALID PARAMETERS"/>
  • Case 2: Invalid Username or Password

    The output is as follows:
    <tree message="ERROR" desc="INVALID USER"/> Or
    <tree message="ERROR" desc="INVALID PASSWORD"/>

Code snippets for Java, PHP, Python and Ruby:
Java:

PHP:

Python:

Ruby:



2. Download Event:

View / Download event details in your IDrive account using the downloadEvent API.

Quick links

Syntax for 'downloadEvent' API:

https://<server address>/evs/downloadEvent

Server address:
Use
getServerAddress API to retrieve the IDrive server address.

HTTP method: POST
Input parameters:
uid username or email address
pwd password
month month of the events
year year of the events
eventid Id of the event

Output:
Below is a sample XML output generated when you call ‘'downloadEvent'’ API:
[2011/09/13 06:35:54] [122.166.15.154] [john] [Download] [myPhotos.zip] [1.24 MB]
[2011/09/13 06:35:54] [122.166.15.154] [john] [Download] [Office.doc] [3.1 MB]
[2011/09/13 06:35:54] [122.166.15.154] [john] [Download] [machine_log.txt] [8.4 MB]
[2011/09/13 06:35:54] [122.166.15.154] [john] Number of files considered for download: 3
[2011/09/13 06:35:54] [122.166.15.154] [john] Number of files downloaded: 3
[2011/09/13 06:35:54] [122.166.15.154] [john] Number of files in sync: 0

Following cases explain the expected outputs during INVALID operations:
  • Case 1: Empty Username or Password

    The output is as follows:
    <tree message="ERROR" desc="INVALID PARAMETERS"/>
  • Case 2: Invalid Username or Password

    The output is as follows:
    <tree message="ERROR" desc="INVALID USER"/> Or
    <tree message="ERROR" desc="INVALID PASSWORD"/>

Code snippets for Java, PHP, Python and Ruby:
Java:

PHP:

Python:

Ruby:



Refer web browser design screenshots to design the browser based events page using this API.