Simplifies interactions with Rapidshare API by providing a set of handy features
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Makes your interactions with the Rapidshare API more pleasant by providing new handy features: creating/moving/deleting files/folders in a user friendly way, upload files, etc.

Until Jan 2013 this gem has extended the existing one -, so it has all features have been implemented by the authors of the original gem at the moment. From Jan 2013 Rapidshare-Ext gem has branched out and ships as a standalone library.


Add this line to your Gemfile:

gem 'rapidshare-ext'

And then execute:

$ bundle

Or install it yourself as:

$ gem install rapidshare-ext


First, create an instance:

api = => 'my_login', :password => 'my_password')
api = => 'cookie_here') # More preferable way


Now you can perform file download in two ways: by HTTP/HTTPS url or by absolute path.

First, by the HTTP url, as it has worked before: '',
  :downloads_dir => '/tmp',
  :save_as => 'file2.txt' # This doesn't work in the original gem at the moment because of Rapidshare API changes

  # With a default local file name '',
    :downloads_dir => '/tmp'

Download by absolute path from account you owned: '/foo/bar/baz/upload_file_1.txt',
  :downloads_dir => '/tmp'

In both the first and second samples the result will be the same.

It's possible to implement a custom progress bar functionality by providing a codeblock to #download method '/foo/bar.txt', :downloads_dir => '/tmp'
do |chunk_size, downloaded, total, progress|
  # chunk_size has the default value of 16384 bytes for Ruby 1.9
  # downloaded is a aggregated size of file part has already been downloaded at the moment
  # total represents a file total size
  # progress is a progress bar value in percents
  # Example: While user downloading a 102598 bytes file the valuse will be as follows:
  # Iter 1: chunk_size=0,     downloaded=0, total=102598, progress=0
  # Iter 2: chunk_size=16384, downloaded=0, total=102598, progress=15.97
  # Iter 3: chunk_size=16384, downloaded=0, total=102598, progress=31.94
  # Iter 4: chunk_size=16384, downloaded=0, total=102598, progress=47.91
  # Iter 5: chunk_size=16384, downloaded=0, total=102598, progress=63.88
  # Iter 6: chunk_size=16384, downloaded=0, total=102598, progress=79.85
  # Iter 7: chunk_size=16384, downloaded=0, total=102598, progress=95.81
  # Iter 8: chunk_size=4294,  downloaded=0, total=102598, progress=100.00

File uploading is also became very simple:

api.upload('/home/odiszapc/', :to => '/gallery/video', :as => '')
# => {
#  :id         => 1,
#  :size       => 12345, # File size in bytes
#  :checksum   => <MD5>,
#  :url        => <DOWNLOAD_URL>, # https://rapidshare/.......
#  :already_exists? => true/false # Does the file already exists within a specific folder, real uploading will not being performed in this case

Destination folder will be created automatically. After uploading has been completed the file will be stored in a Rapidshare as '/gallery/video/' You can easily get a download url after uploading:

result = api.upload('/home/odiszapc/', :to => '/gallery/video', :as => '')

By default, file is uploaded into the root folder:


Rapidshare allows to store multiple files having equal names under the same folder. I believe this behaviour is absolutely wrong. Therefore, each time upload performed it checks if the file with the given name already exists in a folder. If it's true, the upload() just returns info about the existing file with the :already_exists? flag is set to true without any real upload being performed. To force file being overwritten set the :overwrite parameter to true:

api.upload '/home/odiszapc/',
    :to => '/gallery/video',
    :as => ''

# No upload will be performed
api.upload '/home/odiszapc/',
    :to => '/gallery/video',
    :as => ''

# With the following notation file will be uploaded with overwriting the existing one
api.upload '/home/odiszapc/',
    :to => '/gallery/video',
    :as => '',
    :overwrite => true

Deleting files:


Renaming files:

api.rename_file('/foo/bar.rar', 'baz.rar')

Moving files:

api.move_file('/foo/bar/baz.rar', :to => '/foo') # new file path: '/foo/baz.rar'
api.move_file('/foo/bar/baz.rar') # move to a root folder

Get the file ID:

api.file_id('/foo/bar/baz.rar') # => <ID>


As you note it's possible having a hierarchy of folders in your account.

Creating folder hierarchy:

folder_id = api.add_folder 'a/b/c' # => <FOLDER ID>

Deleting folders:


Moving folders:

api.move_folder('/a/b/c', :to => '/a')

This moves the folder 'c' from the directory '/a/b/' and places it under the directory '/a'

You can get hierarchy of all the folders in account:

# => {
#   <folder ID> => {
#     :parent => <parent folder ID>,
#     :name => <folder name>,
#     :path => <folder absolute path>
#   },
#   ...
# }

Note, that after the folder hierarchy is generated first time it's cached permanently to improve performance.

So, if you want to invalidate the cache just call the above method with trailing '!':


If folder tree is inconsistent (orphans are found, see next paragraph for details) the Exception will be thrown when you perform #folders_hierarchy. To automatically normalize the tree, call the method with the :consistent flag:

api.folders_hierarchy :consistent => true

Be careful with the tree consistency, orphan folders may contain a critical data.

A more secure way to deal with folder consistency is to fix all orphans first and then generate folder tree:

api.add_folder '/garbage'
api.move_orphans :to => '/garbage' # Collect all orphans and place them under the /garbage folder
tree = api.folders_hierarchy

Get the folder ID or path:

id = api.folder_id('/foo/bar') # <ID>
api.folder_path(id) # '/foo/bar'


As mentioned earlier, the Rapidshare has its common problem: the chance of orphan folders to be appeared. What does it mean? When you delete parent folder by its ID the folder will be deleted without any of its child folders being deleted. For example, let we have the basic directory tree:

`-a  <- Raw Rapidshare API allows you to delete JUST THIS folder, so hierarchy relation between folders will be lost and the folders 'c' and 'b' will became orphans

Know-how: orphan folders become invisible in your File Manager on the Rapidshare web site, so you may want to hide all the data in this way (stupid idea)

So, the best way to delete a directory tree without washing away consistency of account folder hierarchy is the following:

api.remove_folder '/a' # This will delete all the child directories correctly

However, if you already have orphans in your account there is possible to fix them. So ,the next method detects all orphan folders in your account and moves them into a specific folder:

api.move_orphans :to => '/'

Or we can just delete all of them (be careful):



You can null your account by deleting all the data stored inside:


Be careful with it, because you stake losing all your data


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request
  6. Open beer