How does Document Library Pro work with the REST API?
Document Library Pro stores documents as WordPress content (a custom post type) with fields like title/content, featured image, taxonomies (categories/tags), and any extra metadata the plugin adds. Because it uses WordPress’s data model, your documents and their data are retrievable via the WordPress REST API, just like posts and pages.
That means you can list documents, fetch a single document, search, filter by taxonomy, and read associated data from any external app (React/Vue site, mobile app, intranet, CRM, etc.).
What you can do with the REST API
- List documents for a custom frontend (headless WordPress)
- Fetch a single document by ID (detail page / modal view)
- Search documents by keyword
- Filter by categories/tags (taxonomies)
- Sort and paginate results
- Read document fields (title, excerpt, content, dates, author, links), and any exposed meta
Common endpoints
Document Library Pro documents are exposed through the REST API under the post type route.
- List documents
GET /wp-json/wp/v2/dlp_document - Get one document
GET /wp-json/wp/v2/dlp_document/<id> - List document categories (doc_categories) or tags (doc_tags)
GET /wp-json/wp/v2/doc_categories
Authentication and permissions
- Public data: If your document library is publicly visible, anonymous requests can read documents via REST.
- Private/restricted data (Document Library Pro Advanced): If documents are restricted (logged-in users, roles, password-protected, etc.), REST requests must be authenticated, and results will respect WordPress capabilities.
If searching the knowledge base hasn't answered your question, please contact support.