Our new REST APIs

[Walt Giroir]

We recently released the new version of our REST APIs and I think they really bring the value of REST to Cloud Storage. We have a number of significant enhancements planned but we are looking for more. If you have any suggestions, please let us know.

Here's a quick link to the reference documentation.
http://developer.mezeo.com/mezeo-developer-center/documentation/api-documentation/

Another quick way to understand the APIs is to leverage curl.
http://developer.mezeo.com/mezeo-developer-center/documentation/howto-using-curl-to-access-api/

--Walt

[newbee]

Please give me a link to the examples written using your API's. I am not able to understand how to make use of them. I want to login, upload and download the file to my mezeo account. Please Help.

[Travis McLane]

The command line program 'curl' found on most Linux distributions, and also available for Windows and OS X can be used to interact with the Mezeo API as shown on the curl "HOWTO: Using Curl to access the API" found at the following url:
 http://developer.mezeo.com/mezeo-developer-center/documentation/howto-using-curl-to-access-api/

You can download curl for Windows at the following url:
http://curl.haxx.se/download.html#Win32

Unfortunately, at this time examples are not available but your input would be invaluable for prioritizing creation of api example code.
Which programming language would be most helpful for you?

[Fergus Neff]

Hi guys,

Some initial questions about the API and documentation (which we have been reading through).

1) Are the schemas published as XSD for download?

2) What data validation rules are in place? - for example character restrictions on names for Files and Containers.

3) Does the "bytes" property on a Container resource show the recursive total of all contents (nested Containers and Files)?

4) Is there a preferred way of cancelling an upload that is in progress?

Many thanks,

Fergus.
OpSource.

[Travis McLane]

Fergus,

Thank you for your inquiry.

1)
The schemas are not currently available to download directly as XSD files.
Preparation for making the xsd schema files available for download is in process at this time.

They are currently published in the API Documentation however they are currently being revised.
I would be happy to inform you when the documentation has been updated.

2)
XML representations are validated using the resource schema as defined in the API Documentation.
Note: The schemas are in the process of being revalidated and will be updated soon.

The API does not allow names that include the following characters:
  '\\', '/', '\r', '\n', ':', '*', '?', '"', '<', '>', '|'

3)
The "bytes" property on a Container resource is a total of the immediate contents of that particular container.
It is not recursive.

4)
There is no preferred method to cancel an upload.
Stopping the upload process in the client will terminate the upload.
This will leave behind an unfinished file that consists of all completed *partial file transfers that is up to the client to remove if so desired.  (Partial file transfers are those carried out by specifying the "Content-Range" header.)
The unfinished object will contain all successfully completed requests transferred up to the point of cancellation.
If no requests are successfully completed before the client terminates transmission then the partial http request received up to that point will be discarded.  This is in accordance with the HTTP specification.

[Fergus Neff]

Thanks Travis,

Fergus.

[Travis McLane]

David,

I split your Provisioning question off into the newly created Provisioning Sub-forum and answer it there.
You have been granted access to this forum.

Please let me know if you have any difficulty viewing the new forum.