mirror of
https://github.com/seejohnrun/haste-server.git
synced 2024-12-25 11:37:00 +00:00
Updated POST api (markdown)
parent
18c20e37a5
commit
1910bbcc64
1 changed files with 9 additions and 9 deletions
18
POST-api.md
18
POST-api.md
|
@ -4,19 +4,19 @@ There are two ways to send data up to become a paste on a haste-server:
|
|||
|
||||
#### Raw:
|
||||
|
||||
__POST__: /documents
|
||||
__Content-type__: text/plain
|
||||
__Request body__: contents of paste
|
||||
__Response__: _See below_
|
||||
* __POST__: /documents
|
||||
* __Content-type__: text/plain
|
||||
* __Request body__: contents of paste
|
||||
* __Response__: _See below_
|
||||
|
||||
#### Form Data:
|
||||
|
||||
__POST__: /documents
|
||||
__Content-type__: multipart/form-data
|
||||
__Request body__: A multipart form data encoded body, with a single key named "data" which holds the paste
|
||||
__Response__: _See below_
|
||||
* __POST__: /documents
|
||||
* __Content-type__: multipart/form-data
|
||||
* __Request body__: A multipart form data encoded body, with a single key named "data" which holds the paste
|
||||
* __Response__: _See below_
|
||||
|
||||
For more detail on the how multipart form bodies should be structured, see:
|
||||
NOTE: For more detail on the how multipart form bodies should be structured, see:
|
||||
http://www.w3.org/TR/html401/interact/forms.html#h-17.13.4
|
||||
|
||||
### What do I get back?
|
||||
|
|
Loading…
Reference in a new issue