Liferay DXP REST API

Liferay Digital Experience Platform (DXP) REST API for enterprises to build, manage, and deliver digital portals — intranets, customer portals, partner portals, and commerce sites — enabling AI agents to manage content, user accounts, documents, workflows, and digital experiences through Liferay's open-source Java-based DXP REST and GraphQL headless APIs. Enables AI agents to manage content management for structured content and blog post creation and publishing automation, handle document management for file upload, folder organization, and asset retrieval automation, access user management for portal user account creation and group assignment automation, retrieve workflow management for content approval workflow initiation and status automation, manage forms management for dynamic form submission collection and processing automation, handle site management for portal site configuration and page management automation, access message boards for community forum and discussion thread management automation, retrieve commerce management for product catalog and order management automation, manage taxonomy management for content category and tag organization automation, and integrate Liferay DXP with enterprise identity providers, CRM, and ERP systems for digital portal automation.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Other liferay DXP portal intranet open-source headless-CMS
⚙ Agent Friendliness
53
/ 100
Can an agent use this?
🔒 Security
72
/ 100
Is it safe for agents?
⚡ Reliability
64
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
10
Documentation
72
Error Messages
66
Auth Simplicity
68
Rate Limits
58

🔒 Security

TLS Enforcement
92
Auth Strength
68
Scope Granularity
64
Dep. Hygiene
70
Secret Handling
66

Enterprise portal. GDPR, SOC2. OAuth2. Self-hosted/cloud. Portal content and user data.

⚡ Reliability

Uptime/SLA
60
Version Stability
68
Breaking Changes
62
Error Recovery
64
AF Security Reliability

Best When

An enterprise IT team wanting AI agents to automate content management, user provisioning, and digital experience delivery through Liferay DXP's headless REST and GraphQL APIs on self-hosted or Liferay Cloud infrastructure.

Avoid When

JAVA/ENTERPRISE DEPLOYMENT REQUIRED: Liferay DXP is a Java enterprise application requiring significant infrastructure; automated SaaS assumption creates deployment_complexity for teams expecting cloud-native simplicity; automated must deploy and manage Liferay infrastructure (or use Liferay Cloud). HEADLESS API REQUIRES MODERN DXP VERSION: Liferay's modern REST APIs (headless delivery) are available in Liferay DXP 7.2+; automated version-agnostic assumption creates api_not_found for integrations against older Liferay portal versions; automated must verify Liferay version supports headless REST API. OAUTH2 CLIENT REQUIRES CONFIGURATION: Liferay OAuth2 clients must be configured in Liferay's admin console; automated instant-oauth assumption creates unauthorized for API calls without pre-configured OAuth2 application; automated must create OAuth2 application in Liferay admin before API integration. SITE AND SCOPE CONTEXT IS REQUIRED: Liferay API calls require correct site/group scope context; automated global-context assumption creates wrong_site_content for content operations not scoped to correct Liferay site; automated must include site key or group ID for site-scoped operations.

Use Cases

  • Managing intranet content and employee portal pages for internal communications automation agents
  • Publishing and updating customer-facing portal content through headless API for CMS automation agents
  • Managing user accounts and group memberships in enterprise digital portals for identity automation agents
  • Orchestrating content approval workflows and publishing lifecycle for digital experience agents

Not For

  • Lightweight blog and marketing website CMS (Liferay DXP is enterprise portal; WordPress and Webflow serve simpler CMS needs)
  • Real-time collaborative document editing (Liferay manages documents but not real-time co-authoring; Google Workspace serves real-time collaboration)
  • E-commerce-primary platforms without portal context (Liferay Commerce is portal-native; Shopify and Magento serve e-commerce-first needs)

Interface

REST API
Yes
GraphQL
Yes
gRPC
No
MCP Server
No
SDK
No
Webhooks
Yes

Authentication

Methods: oauth2 basic
OAuth: Yes Scopes: Yes

Liferay DXP uses OAuth2 for headless REST API. REST API + GraphQL with JSON. Los Angeles, CA HQ. Founded 2000 by Bryan Cheung. Products: Liferay DXP (enterprise portal), Liferay Cloud (PaaS), Liferay Commerce. Open-source Community Edition + commercial Enterprise Edition. 1,200+ enterprise customers. Industries: financial services, insurance, government, manufacturing. GitHub: liferay/liferay-portal. Competes with Adobe Experience Manager, Salesforce Experience Cloud, and Sitecore for enterprise DXP.

Pricing

Model: freemium
Free tier: Yes
Requires CC: No

Los Angeles CA. Open-source community free. 1,200+ enterprise customers. Subscription for Enterprise Edition.

Agent Metadata

Pagination
page
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • SITE KEY IS REQUIRED FOR CONTENT OPERATIONS: Liferay content APIs require site key to scope content to correct site; automated global-content assumption creates wrong_site_scope for content operations not including site key parameter; automated must include siteKey or siteId for all site-scoped content operations
  • WORKFLOW SUBMISSION DOESN'T PUBLISH: Submitting content to workflow doesn't publish it; automated submit-equals-publish assumption creates unpublished_content for content submitted to approval workflow but not yet approved and published; automated must track workflow state and publish after approval
  • OAUTH2 SCOPES ARE LIFERAY-SPECIFIC: Liferay OAuth2 uses custom scopes defined per portal; automated standard-scopes assumption creates insufficient_permissions for OAuth tokens without Liferay-specific scope configuration; automated must configure and request correct Liferay-specific OAuth scopes
  • DOCUMENT UPLOAD REQUIRES SEPARATE ENDPOINT: Documents use multipart upload endpoint separate from JSON content APIs; automated JSON-upload assumption creates upload_rejected for file uploads not using multipart/form-data; automated must use Liferay's document upload endpoint for binary file operations
  • VERSION DIFFERENCES IN API: Liferay DXP 7.2, 7.3, 7.4 have evolving headless API structures; automated version-agnostic assumption creates endpoint_not_found for APIs available in newer versions not yet deployed; automated must verify API availability against specific DXP version

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Liferay DXP REST API.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6470
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered