When the Web Clipper service is enabled, Joplin exposes a REST API which allows third-party applications to access Joplin's data and to create, modify or delete notes, notebooks, resources or tags.
In order to use it, you'll first need to find on which port the service is running. To do so, open the Web Clipper Options in Joplin and if the service is running it should tell you on which port. Normally it runs on port 41184. If you want to find it programmatically, you may follow this kind of algorithm:
let port = null;
@@ -262,13 +280,13 @@ for (let portToTest = 41184; portToTest <= 41194; portToTest++) {
}
}
To prevent unauthorised applications from accessing the API, the calls must be authentified. To do so, you must provide a token as a query parameter for each API call. You can get this token from the Joplin desktop application, on the Web Clipper Options screen.
This would be an example of valid cURL call using a token:
curl http://localhost:41184/notes?token=ABCD123ABCD123ABCD123ABCD123ABCD123
In the documentation below, the token will not be specified every time however you will need to include it.
-All the calls, unless noted otherwise, receives and send JSON data. For example to create a new note:
curl --data '{ "title": "My note", "body": "Some note in **Markdown**"}' http://localhost:41184/notes
You can change the fields that will be returned by the API using the fields= query parameter, which takes a list of comma separated fields. For example, to get the longitude and latitude of a note, use this:
curl http://localhost:41184/notes/ABCD123?fields=longitude,latitude
To get the IDs only of all the tags:
curl http://localhost:41184/tags?fields=id
In case of an error, an HTTP status code >= 400 will be returned along with a JSON object that provides more info about the error. The JSON object is in the format { "error": "description of error" }.
Call GET /ping to check if the service is available. It should return "JoplinClipperServer" if it works.
-Call GET /search?query=YOUR_QUERY to search for notes. This end-point supports the field parameter which is recommended to use so that you only get the data that you need. The query syntax is as described in the main documentation: https://joplinapp.org/#searching
Gets all notes
-Gets note with ID :id
-Gets all the tags attached to this note.
-Creates a new note
You can either specify the note body as Markdown by setting the body parameter, or in HTML by setting the body_html.
Examples:
@@ -477,17 +495,17 @@ for (let portToTest = 41184; portToTest <= 41194; portToTest++) { -When a new note is created, it is automatically assigned a new unique ID so normally you do not need to set the ID. However, if for some reason you want to set it, you can supply it as the id property. It needs to be a 32 characters long hexadecimal string. Make sure it is unique, for example by generating it using whatever GUID function is available in your programming language.
curl --data '{ "id": "00a87474082744c1a8515da6aa5792d2", "title": "My note with custom ID"}' http://127.0.0.1:41184/notes
Sets the properties of the note with ID :id
-Deletes the note with ID :id
-This is actually a notebook. Internally notebooks are called "folders".
-Gets all folders
The folders are returned as a tree. The sub-notebooks of a notebook, if any, are under the children key.
Gets folder with ID :id
-Gets all the notes inside this folder.
-Creates a new folder
-Sets the properties of the folder with ID :id
-Deletes the folder with ID :id
-Gets all resources
-Gets resource with ID :id
-Gets the actual file associated with this resource.
-Creates a new resource
Creating a new resource is special because you also need to upload the file. Unlike other API calls, this one must have the "multipart/form-data" Content-Type. The file data must be passed to the "data" form field, and the other properties to the "props" form field. An example of a valid call with cURL would be:
curl -F 'data=@/path/to/file.jpg' -F 'props={"title":"my resource title"}' http://localhost:41184/resources
The "data" field is required, while the "props" one is not. If not specified, default values will be used.
-Sets the properties of the resource with ID :id
-Deletes the resource with ID :id
-Gets all tags
-Gets tag with ID :id
-Gets all the notes with this tag.
-Creates a new tag
-Post a note to this endpoint to add the tag to the note. The note data must at least contain an ID property (all other properties will be ignored).
-Sets the properties of the tag with ID :id
-Deletes the tag with ID :id
-Remove the tag from the note.