Skip to content

Shinobu API

4 endpoints.

GEThttp://localhost:3000/api/shinobu

Get the current status of the FileWatcher.

Responses

200Status
{
  "is_alive": 1,
  "operation": "shinobu_status",
  "pid": 1608,
  "success": 1
}

Your own instance address. Requests go from this browser straight to it.

POSThttp://localhost:3000/api/shinobu/rescan

This deletes the internal map of scanned files on your system (the “filemap”) and restarts Shinobu, effectively prompting a full rescan of your FS.

Responses

200Result
{
  "new_pid": 1727,
  "operation": "shinobu_rescan",
  "success": 1
}

This endpoint needs an administrator token — a guest (read-only) token is refused by the server.

Your own instance address. Requests go from this browser straight to it.

POSThttp://localhost:3000/api/shinobu/restart

Restart the Shinobu filewatcher

Responses

200Result
{
  "new_pid": 1727,
  "operation": "shinobu_restart",
  "success": 1
}

This endpoint needs an administrator token — a guest (read-only) token is refused by the server.

Your own instance address. Requests go from this browser straight to it.

POSThttp://localhost:3000/api/shinobu/stop

Stops the Filewatcher. Use /api/shinobu/restart to start it again.

Responses

200Result
{
  "error": "",
  "operation": "",
  "success": 0,
  "successMessage": ""
}

This endpoint needs an administrator token — a guest (read-only) token is refused by the server.

Your own instance address. Requests go from this browser straight to it.