Skip to content


Paperless makes use of the Django REST Framework standard API interface. It provides a browsable API for most of its endpoints, which you can inspect at http://<paperless-host>:<port>/api/. This also documents most of the available filters and ordering fields.

The API provides the following main endpoints:

  • /api/correspondents/: Full CRUD support.
  • /api/custom_fields/: Full CRUD support.
  • /api/documents/: Full CRUD support, except POSTing new documents. See below.
  • /api/document_types/: Full CRUD support.
  • /api/groups/: Full CRUD support.
  • /api/logs/: Read-Only.
  • /api/mail_accounts/: Full CRUD support.
  • /api/mail_rules/: Full CRUD support.
  • /api/profile/: GET, PATCH
  • /api/share_links/: Full CRUD support.
  • /api/storage_paths/: Full CRUD support.
  • /api/tags/: Full CRUD support.
  • /api/tasks/: Read-only.
  • /api/users/: Full CRUD support.
  • /api/workflows/: Full CRUD support.
  • /api/search/ GET, see below.

All of these endpoints except for the logging endpoint allow you to fetch (and edit and delete where appropriate) individual objects by appending their primary key to the path, e.g. /api/documents/454/.

The objects served by the document endpoint contain the following fields:

  • id: ID of the document. Read-only.
  • title: Title of the document.
  • content: Plain text content of the document.
  • tags: List of IDs of tags assigned to this document, or empty list.
  • document_type: Document type of this document, or null.
  • correspondent: Correspondent of this document or null.
  • created: The date time at which this document was created.
  • created_date: The date (YYYY-MM-DD) at which this document was created. Optional. If also passed with created, this is ignored.
  • modified: The date at which this document was last edited in paperless. Read-only.
  • added: The date at which this document was added to paperless. Read-only.
  • archive_serial_number: The identifier of this document in a physical document archive.
  • original_file_name: Verbose filename of the original document. Read-only.
  • archived_file_name: Verbose filename of the archived document. Read-only. Null if no archived document is available.
  • notes: Array of notes associated with the document.
  • set_permissions: Allows setting document permissions. Optional, write-only. See below.
  • custom_fields: Array of custom fields & values, specified as { field: CUSTOM_FIELD_ID, value: VALUE }


Note that all endpoint URLs must end with a /slash.

Downloading documents

In addition to that, the document endpoint offers these additional actions on individual documents:

  • /api/documents/<pk>/download/: Download the document.
  • /api/documents/<pk>/preview/: Display the document inline, without downloading it.
  • /api/documents/<pk>/thumb/: Download the PNG thumbnail of a document.

Paperless generates archived PDF/A documents from consumed files and stores both the original files as well as the archived files. By default, the endpoints for previews and downloads serve the archived file, if it is available. Otherwise, the original file is served. Some document cannot be archived.

The endpoints correctly serve the response header fields Content-Disposition and Content-Type to indicate the filename for download and the type of content of the document.

In order to download or preview the original document when an archived document is available, supply the query parameter original=true.


Paperless used to provide these functionality at /fetch/<pk>/preview, /fetch/<pk>/thumb and /fetch/<pk>/doc. Redirects to the new URLs are in place. However, if you use these old URLs to access documents, you should update your app or script to use the new URLs.

Getting document metadata

The api also has an endpoint to retrieve read-only metadata about specific documents. this information is not served along with the document objects, since it requires reading files and would therefore slow down document lists considerably.

Access the metadata of a document with an ID id at /api/documents/<id>/metadata/.

The endpoint reports the following data:

  • original_checksum: MD5 checksum of the original document.
  • original_size: Size of the original document, in bytes.
  • original_mime_type: Mime type of the original document.
  • media_filename: Current filename of the document, under which it is stored inside the media directory.
  • has_archive_version: True, if this document is archived, false otherwise.
  • original_metadata: A list of metadata associated with the original document. See below.
  • archive_checksum: MD5 checksum of the archived document, or null.
  • archive_size: Size of the archived document in bytes, or null.
  • archive_metadata: Metadata associated with the archived document, or null. See below.

File metadata is reported as a list of objects in the following form:

    "namespace": "",
    "prefix": "pdf",
    "key": "Producer",
    "value": "SparklePDF, Fancy edition"

namespace and prefix can be null. The actual metadata reported depends on the file type and the metadata available in that specific document. Paperless only reports PDF metadata at this point.

Documents additional endpoints

  • /api/documents/<id>/notes/: Retrieve notes for a document.
  • /api/documents/<id>/share_links/: Retrieve share links for a document.
  • /api/documents/<id>/history/: Retrieve history of changes for a document.


The REST api provides four different forms of authentication.

  1. Basic authentication

    Authorize by providing a HTTP header in the form

    Authorization: Basic <credentials>

    where credentials is a base64-encoded string of <username>:<password>

  2. Session authentication

    When you're logged into paperless in your browser, you're automatically logged into the API as well and don't need to provide any authorization headers.

  3. Token authentication

    You can create (or re-create) an API token by opening the "My Profile" link in the user dropdown found in the web UI and clicking the circular arrow button.

    Paperless also offers an endpoint to acquire authentication tokens.

    POST a username and password as a form or json string to /api/token/ and paperless will respond with a token, if the login data is correct. This token can be used to authenticate other requests with the following HTTP header:

    Authorization: Token <token>

    Tokens can also be managed in the Django admin.

  4. Remote User authentication

    If enabled (see configuration), you can authenticate against the API using Remote User auth.

A global search endpoint is available at /api/search/ and requires a search term of > 2 characters e.g. ?query=foo. This endpoint returns a maximum of 3 results across nearly all objects, e.g. documents, tags, saved views, mail rules, etc. Results are only included if the requesting user has the appropriate permissions.

Results are returned in the following format:

  total: number
  documents: []
  saved_views: []
  correspondents: []
  document_types: []
  storage_paths: []
  tags: []
  users: []
  groups: []
  mail_accounts: []
  mail_rules: []
  custom_fields: []
  workflows: []

Global search first searches objects by name (or title for documents) matching the query. If the optional db_only parameter is set, only document titles will be searched. Otherwise, if the amount of documents returned by a simple title string search is < 3, results from the search index will also be included.

Searching for documents

Full text searching is available on the /api/documents/ endpoint. Two specific query parameters cause the API to return full text search results:

  • /api/documents/?query=your%20search%20query: Search for a document using a full text query. For details on the syntax, see Basic Usage - Searching.
  • /api/documents/?more_like_id=1234: Search for documents similar to the document with id 1234.

Pagination works exactly the same as it does for normal requests on this endpoint.

Certain limitations apply to full text queries:

  • Results are always sorted by search score. The results matching the query best will show up first.
  • Only a small subset of filtering parameters are supported.

Furthermore, each returned document has an additional __search_hit__ attribute with various information about the search results:

    "count": 31,
    "next": "http://localhost:8000/api/documents/?page=2&query=test",
    "previous": null,
    "results": [


            "id": 123,
            "title": "title",
            "content": "content",


            "__search_hit__": {
                "score": 0.343,
                "highlights": "text <span class="match">Test</span> text",
                "rank": 23


  • score is an indication how well this document matches the query relative to the other search results.
  • highlights is an excerpt from the document content and highlights the search terms with <span> tags as shown above.
  • rank is the index of the search results. The first result will have rank 0.


Get auto completions for a partial search term.

Query parameters:

  • term: The incomplete term.
  • limit: Amount of results. Defaults to 10.

Results returned by the endpoint are ordered by importance of the term in the document index. The first result is the term that has the highest Tf/Idf score in the index.

["term1", "term3", "term6", "term4"]

POSTing documents

The API provides a special endpoint for file uploads:


POST a multipart form to this endpoint, where the form field document contains the document that you want to upload to paperless. The filename is sanitized and then used to store the document in a temporary directory, and the consumer will be instructed to consume the document from there.

The endpoint supports the following optional form fields:

  • title: Specify a title that the consumer should use for the document.
  • created: Specify a DateTime where the document was created (e.g. "2016-04-19" or "2016-04-19 06:15:00+02:00").
  • correspondent: Specify the ID of a correspondent that the consumer should use for the document.
  • document_type: Similar to correspondent.
  • storage_path: Similar to correspondent.
  • tags: Similar to correspondent. Specify this multiple times to have multiple tags added to the document.
  • archive_serial_number: An optional archive serial number to set.
  • custom_fields: An array of custom field ids to assign (with an empty value) to the document.

The endpoint will immediately return HTTP 200 if the document consumption process was started successfully, with the UUID of the consumption task as the data. No additional status information about the consumption process itself is available immediately, since that happens in a different process. However, querying the tasks endpoint with the returned UUID e.g. /api/tasks/?task_id={uuid} will provide information on the state of the consumption including the ID of a created document if consumption succeeded.


All objects (documents, tags, etc.) allow setting object-level permissions with optional owner and / or a set_permissions parameters which are of the form:

"owner": ...,
"set_permissions": {
    "view": {
        "users": [...],
        "groups": [...],
    "change": {
        "users": [...],
        "groups": [...],


Arrays should contain user or group ID numbers.

If these parameters are supplied the object's permissions will be overwritten, assuming the authenticated user has permission to do so (the user must be the object owner or a superuser).

Retrieving full permissions

By default, the API will return a truncated version of object-level permissions, returning user_can_change indicating whether the current user can edit the object (either because they are the object owner or have permissions granted). You can pass the parameter full_perms=true to API calls to view the full permissions of objects in a format that mirrors the set_permissions parameter above.

Bulk Editing

The API supports various bulk-editing operations which are executed asynchronously.


For bulk operations on documents, use the endpoint /api/documents/bulk_edit/ which accepts a json payload of the format:

  "documents": [LIST_OF_DOCUMENT_IDS],
  "method": METHOD, // see below
  "parameters": args // see below

The following methods are supported:

  • set_correspondent
  • Requires parameters: { "correspondent": CORRESPONDENT_ID }
  • set_document_type
  • Requires parameters: { "document_type": DOCUMENT_TYPE_ID }
  • set_storage_path
  • Requires parameters: { "storage_path": STORAGE_PATH_ID }
  • add_tag
  • Requires parameters: { "tag": TAG_ID }
  • remove_tag
  • Requires parameters: { "tag": TAG_ID }
  • modify_tags
  • Requires parameters: { "add_tags": [LIST_OF_TAG_IDS] } and / or { "remove_tags": [LIST_OF_TAG_IDS] }
  • delete
  • No parameters required
  • reprocess
  • No parameters required
  • set_permissions
  • Requires parameters:
    • "set_permissions": PERMISSIONS_OBJ (see format above) and / or
    • "owner": OWNER_ID or null
    • "merge": true or false (defaults to false)
  • The merge flag determines if the supplied permissions will overwrite all existing permissions (including removing them) or be merged with existing permissions.
  • merge
  • No additional parameters required.
  • The ordering of the merged document is determined by the list of IDs.
  • Optional parameters:
    • "metadata_document_id": DOC_ID apply metadata (tags, correspondent, etc.) from this document to the merged document.
    • "delete_originals": true to delete the original documents. This requires the calling user being the owner of all documents that are merged.
  • split
  • Requires parameters:
    • "pages": [..] The list should be a list of pages and/or a ranges, separated by commas e.g. "[1,2-3,4,5-7]"
  • Optional parameters:
    • "delete_originals": true to delete the original document after consumption. This requires the calling user being the owner of the document.
  • The split operation only accepts a single document.
  • rotate
  • Requires parameters:
    • "degrees": DEGREES. Must be an integer i.e. 90, 180, 270
  • delete_pages
  • Requires parameters:
    • "pages": [..] The list should be a list of integers e.g. "[2,3,4]"
  • The delete_pages operation only accepts a single document.


Bulk editing for objects (tags, document types etc.) currently supports set permissions or delete operations, using the endpoint: /api/bulk_edit_objects/, which requires a json payload of the format:

  "objects": [LIST_OF_OBJECT_IDS],
  "object_type": "tags", "correspondents", "document_types" or "storage_paths",
  "operation": "set_permissions" or "delete",
  "owner": OWNER_ID, // optional
  "permissions": { "view": { "users": [] ... }, "change": { ... } }, // (see 'set_permissions' format above)
  "merge": true / false // defaults to false, see above

API Versioning

The REST API is versioned since Paperless-ngx 1.3.0.

  • Versioning ensures that changes to the API don't break older clients.
  • Clients specify the specific version of the API they wish to use with every request and Paperless will handle the request using the specified API version.
  • Even if the underlying data model changes, older API versions will always serve compatible data.
  • If no version is specified, Paperless will serve version 1 to ensure compatibility with older clients that do not request a specific API version.

API versions are specified by submitting an additional HTTP Accept header with every request:

Accept: application/json; version=6

If an invalid version is specified, Paperless 1.3.0 will respond with "406 Not Acceptable" and an error message in the body. Earlier versions of Paperless will serve API version 1 regardless of whether a version is specified via the Accept header.

If a client wishes to verify whether it is compatible with any given server, the following procedure should be performed:

  1. Perform an authenticated request against any API endpoint. If the server is on version 1.3.0 or newer, the server will add two custom headers to the response:

    X-Api-Version: 2
    X-Version: 1.3.0
  2. Determine whether the client is compatible with this server based on the presence/absence of these headers and their values if present.

API Changelog

Version 1

Initial API version.

Version 2

  • Added field Tag.color. This read/write string field contains a hex color such as #a6cee3.
  • Added read-only field Tag.text_color. This field contains the text color to use for a specific tag, which is either black or white depending on the brightness of Tag.color.
  • Removed field Tag.colour.

Version 3

  • Permissions endpoints have been added.
  • The format of the /api/ui_settings/ has changed.

Version 4

  • Consumption templates were refactored to workflows and API endpoints changed as such.