Tropo is part of CiscoLearn More

Hosting Files with Tropo

Do you need a place to store audio files, JSON catalog files, XML address books and so on for reference and use in your applications? Tropo hosting is for you! Yay!

With Tropo hosting, you can host your resource files for free and access them directly from Tropo when you need to edit them.

When referencing a file hosted on Tropo's servers, it is necessary to use a fully-qualified URL, and not just the file name. See Using hosted resource files below for an example.

Tropo’s File Manager

Working with your hosted files is simple. Once you're logged into your account, click on the “Your Hosted Files” link from the menu. Here you will be presented with a file manager where you can access your files, rename them, or upload new ones.


You can also use your favorite FTP client to manage your files. You can access them by connecting to, then just use your regular Tropo Username and Password to log in.

Using hosted resource files

If you wanted to reference a file that you hosted with Tropo in a script, maybe an audio file to be used in a 'say', you would use a path that begins with:

Replace 12345 with your account ID (which can be found by examining the path for any application that uses a Tropo hosted script); if you have the file in a sub-directory, like the already provided 'audio' folder, just append the sub-directory to the end of the path followed by the file's name. Your path might look like this in your script:


Files hosted at are only available within our network, so any files you place on our servers will not be publicly accessible. This is done for security purposes, however this also means hosted audio files will only be accessible within a Tropo application, you couldn't link the file on a website or any other external app.

One other note on security - the tokens you use to launch an application should be kept private and guarded like a password, otherwise it's possible for other people to launch your application without your permission.

Recorded Audio Files

Note that we do not keep any recorded audio files (those created via record or startRecording/stopRecording) on These are sent to an S3 bucket of your choice, or via FTP or HTTP to the server you define in the recordURI parameter.