API upload servlet: Difference between revisions
		
		
		
		Jump to navigation
		Jump to search
		
| w>Jguillo No edit summary | w>Jguillo No edit summary | ||
| Line 21: | Line 21: | ||
| REQUEST: | REQUEST: | ||
|   <nowiki>http://upload01.safecreative.org/api-upload</nowiki> | |||
| <pre> | <pre> | ||
| Content-Type: multipart/form-data; boundary=AaB03x | |||
| --AaB03x | --AaB03x | ||
| Content-Disposition: form-data; name="uploadid" | Content-Disposition: form-data; name="uploadid" | ||
| Line 28: | Line 29: | ||
| 3c33a96c-7743-43d0-9614-db70fa46d3ad | 3c33a96c-7743-43d0-9614-db70fa46d3ad | ||
| --AaB03x | --AaB03x | ||
| Content-Disposition:  | Content-Disposition: file; name="file"; filename="file1.txt" | ||
| Content-Type: text/plain | Content-Type: text/plain | ||
Revision as of 14:13, 5 May 2010
You can upload works using standard HTTP upload via POST multipart request.
The upload URL must be retrieved using [work.upload.lookup]
Info
HTTP request must be configured with header:
Content-Type: multipart/form-data
Parameters
- uploadid*: Upload ID returned by [work.upload.lookup].
- Can be included in the POST body or as a querystring argument in the URL
 
- file*: File contents as a file parameter in the POST body
Returns
The servlet returns the upload ticket directly (with no XML enclosure)
Sample
REQUEST:
http://upload01.safecreative.org/api-upload
Content-Type: multipart/form-data; boundary=AaB03x --AaB03x Content-Disposition: form-data; name="uploadid" 3c33a96c-7743-43d0-9614-db70fa46d3ad --AaB03x Content-Disposition: file; name="file"; filename="file1.txt" Content-Type: text/plain These are the file contents --AaB03x--
RESPONSE
HvWIbGj7anDefJK3tQHdPze8ekYaVUQJgKw_N6t0Wd_UblANNOjyVfkyK0fgPXRPgiR8SyVr7HmS4Uiiediu6MlFVYIcjUD0zc4Kc8m3e2Irr14iQi-A215pEaqlvOSZ6WUIbWvY-GD2e8akWxhESdnFG088_nUHEsAjkOvnF-ogK144M4vLuIj4Ylc6inW-80LNnqH10kh7zMJcxsv0lZzTMGrXa2pN