If not otherwise stated, OctoPrint’s API expects request bodies and issues response bodies as
OctoPrint uses UTF-8 as charset.
That also includes headers in
multipart/form-data requests, in order to allow the full UTF-8 range of characters
for uploaded filenames. If a
multipart/form-data sub header cannot be decoded as UTF-8, OctoPrint will also attempt
to decode it as ISO-8859-1.
Additionally, OctoPrint supports replacing the
filename field in the
Content-Disposition header of a
multipart field with a
filename* field following RFC 5987, Section 3.2,
which allows defining the charset used for encoding the filename. If both
filename* fields are
present, following the recommendation of the RFC
filename* will be used.
For an example on how to send a request utilizing RFC 5987 for the
filename* attribute, see the second example
in Upload file.
To make use of the OctoPrint API from websites other than the OctoPrint web interface, cross-origin resource sharing (CORS) must be enabled. This is the case even when the website in question is served from a different port on the same machine and on localhost.
To enable this feature, set the
allowCrossOrigin key of the
api section in
check the corresponding checkbox in the API settings dialog.
api: enabled: true key: ... allowCrossOrigin: true
This means any browser page can send requests to the OctoPrint API. Authorization is still required however.
If CORS is not enabled you will get errors like the following:
XMLHttpRequest cannot load http://localhost:8081/api/files. No 'Access-Control-Allow-Origin' header is present on the requested resource.