diff --git a/docs/api/backends.rst b/docs/api/backends.rst
deleted file mode 100644
index 617bcb94..00000000
--- a/docs/api/backends.rst
+++ /dev/null
@@ -1,132 +0,0 @@
-**********************
-:mod:`mopidy.backends`
-**********************
-
-.. automodule:: mopidy.backends
-    :synopsis: Backend APIs
-
-
-The backend, controller, and provider concepts
-==============================================
-
-Backend:
-    The backend is mostly for convenience. It is a container that holds
-    references to all the controllers.
-Controllers:
-    Each controller has responsibility for a given part of the backend
-    functionality. Most, but not all, controllers delegates some work to one or
-    more providers. The controllers are responsible for choosing the right
-    provider for any given task based upon i.e. the track's URI.
-Providers:
-    Anything specific to i.e. Spotify integration or local storage is contained
-    in the providers. To integrate with new music sources, you just add new
-    providers.
-
-.. digraph:: backend_relations
-
-    Backend -> "Current\nplaylist\ncontroller"
-    Backend -> "Library\ncontroller"
-    "Library\ncontroller" -> "Library\nproviders"
-    Backend -> "Playback\ncontroller"
-    "Playback\ncontroller" -> "Playback\nproviders"
-    Backend -> "Stored\nplaylists\ncontroller"
-    "Stored\nplaylists\ncontroller" -> "Stored\nplaylist\nproviders"
-    Backend -> Mixer
-
-.. _backend-controller-api:
-
-Backend controller API
-======================
-
-.. note::
-
-    The backend controller API is the interface that is used by frontends like
-    :mod:`mopidy.frontends.mpd`. If you want to implement your own backend, see
-    the :ref:`backend-provider-api`.
-
-.. autoclass:: mopidy.backends.base.BaseBackend
-    :members:
-    :undoc-members:
-
-
-Playback controller
--------------------
-
-Manages playback, with actions like play, pause, stop, next, previous, and
-seek.
-
-.. autoclass:: mopidy.backends.base.BasePlaybackController
-    :members:
-    :undoc-members:
-
-
-Mixer controller
-----------------
-
-Manages volume. See :class:`mopidy.mixers.BaseMixer`.
-
-
-Current playlist controller
----------------------------
-
-Manages everything related to the currently loaded playlist.
-
-.. autoclass:: mopidy.backends.base.BaseCurrentPlaylistController
-    :members:
-    :undoc-members:
-
-
-Stored playlists controller
----------------------------
-
-Manages stored playlist.
-
-.. autoclass:: mopidy.backends.base.BaseStoredPlaylistsController
-    :members:
-    :undoc-members:
-
-
-Library controller
-------------------
-
-Manages the music library, e.g. searching for tracks to be added to a playlist.
-
-.. autoclass:: mopidy.backends.base.BaseLibraryController
-    :members:
-    :undoc-members:
-
-
-.. _backend-provider-api:
-
-Backend provider API
-====================
-
-.. note::
-
-    The backend provider API is the interface that must be implemented when you
-    create a backend. If you are working on a frontend and need to access the
-    backend, see the :ref:`backend-controller-api`.
-
-
-Playback provider
------------------
-
-.. autoclass:: mopidy.backends.base.BasePlaybackProvider
-    :members:
-    :undoc-members:
-
-
-Stored playlists provider
--------------------------
-
-.. autoclass:: mopidy.backends.base.BaseStoredPlaylistsProvider
-    :members:
-    :undoc-members:
-
-
-Backend provider implementations
-================================
-
-* :mod:`mopidy.backends.dummy`
-* :mod:`mopidy.backends.libspotify`
-* :mod:`mopidy.backends.local`
diff --git a/docs/api/backends/concepts.rst b/docs/api/backends/concepts.rst
new file mode 100644
index 00000000..fd7b4d13
--- /dev/null
+++ b/docs/api/backends/concepts.rst
@@ -0,0 +1,28 @@
+**********************************************
+The backend, controller, and provider concepts
+**********************************************
+
+Backend:
+    The backend is mostly for convenience. It is a container that holds
+    references to all the controllers.
+Controllers:
+    Each controller has responsibility for a given part of the backend
+    functionality. Most, but not all, controllers delegates some work to one or
+    more providers. The controllers are responsible for choosing the right
+    provider for any given task based upon i.e. the track's URI. See
+    :ref:`backend-controller-api` for more details.
+Providers:
+    Anything specific to i.e. Spotify integration or local storage is contained
+    in the providers. To integrate with new music sources, you just add new
+    providers. See :ref:`backend-provider-api` for more details.
+
+.. digraph:: backend_relations
+
+    Backend -> "Current\nplaylist\ncontroller"
+    Backend -> "Library\ncontroller"
+    "Library\ncontroller" -> "Library\nproviders"
+    Backend -> "Playback\ncontroller"
+    "Playback\ncontroller" -> "Playback\nproviders"
+    Backend -> "Stored\nplaylists\ncontroller"
+    "Stored\nplaylists\ncontroller" -> "Stored\nplaylist\nproviders"
+    Backend -> Mixer
diff --git a/docs/api/backends/controllers.rst b/docs/api/backends/controllers.rst
new file mode 100644
index 00000000..a9d54504
--- /dev/null
+++ b/docs/api/backends/controllers.rst
@@ -0,0 +1,65 @@
+.. _backend-controller-api:
+
+**********************
+Backend controller API
+**********************
+
+
+The backend controller API is the interface that is used by frontends like
+:mod:`mopidy.frontends.mpd`. If you want to implement your own backend, see the
+:ref:`backend-provider-api`.
+
+
+The backend
+===========
+
+.. autoclass:: mopidy.backends.base.BaseBackend
+    :members:
+    :undoc-members:
+
+
+Playback controller
+===================
+
+Manages playback, with actions like play, pause, stop, next, previous, and
+seek.
+
+.. autoclass:: mopidy.backends.base.BasePlaybackController
+    :members:
+    :undoc-members:
+
+
+Mixer controller
+================
+
+Manages volume. See :class:`mopidy.mixers.BaseMixer`.
+
+
+Current playlist controller
+===========================
+
+Manages everything related to the currently loaded playlist.
+
+.. autoclass:: mopidy.backends.base.BaseCurrentPlaylistController
+    :members:
+    :undoc-members:
+
+
+Stored playlists controller
+===========================
+
+Manages stored playlist.
+
+.. autoclass:: mopidy.backends.base.BaseStoredPlaylistsController
+    :members:
+    :undoc-members:
+
+
+Library controller
+==================
+
+Manages the music library, e.g. searching for tracks to be added to a playlist.
+
+.. autoclass:: mopidy.backends.base.BaseLibraryController
+    :members:
+    :undoc-members:
diff --git a/docs/api/backends/providers.rst b/docs/api/backends/providers.rst
new file mode 100644
index 00000000..0b042241
--- /dev/null
+++ b/docs/api/backends/providers.rst
@@ -0,0 +1,33 @@
+.. _backend-provider-api:
+
+********************
+Backend provider API
+********************
+
+The backend provider API is the interface that must be implemented when you
+create a backend. If you are working on a frontend and need to access the
+backend, see the :ref:`backend-controller-api`.
+
+
+Playback provider
+=================
+
+.. autoclass:: mopidy.backends.base.BasePlaybackProvider
+    :members:
+    :undoc-members:
+
+
+Stored playlists provider
+=========================
+
+.. autoclass:: mopidy.backends.base.BaseStoredPlaylistsProvider
+    :members:
+    :undoc-members:
+
+
+Backend provider implementations
+================================
+
+* :mod:`mopidy.backends.dummy`
+* :mod:`mopidy.backends.libspotify`
+* :mod:`mopidy.backends.local`
diff --git a/docs/api/index.rst b/docs/api/index.rst
index 87ec9bb3..1f37e9ff 100644
--- a/docs/api/index.rst
+++ b/docs/api/index.rst
@@ -5,4 +5,7 @@ API reference
 .. toctree::
     :glob:
 
-    **
+    backends/concepts
+    backends/controllers
+    backends/providers
+    *