Oracle WebCenter Content REST API Swagger (OpenAPI) Specification

If you’ve ever worked with Oracle WebCenter Content, you know how robust (and sometimes daunting) its REST APIs can be. While Oracle provides detailed documentation on it's REST APIs there are no swagger files as Oracle Content Management had for their APIs.

To make life easier - I've created one which I'll try to keep upto date:

Why a Swagger File Matters

Swagger aka the OpenAPI Specification, has become the standard for describing RESTful APIs.

You can:

• Visualize endpoints and see available methods, parameters, and responses.
• Quickly try out API calls in tools like Swagger UI, Postman, or Insomnia.
• Generate client SDKs or server stubs in a variety of languages.
• Onboard developers faster with interactive documentation instead of endless scrolling through static docs.

Keep an eye out for my new MCP Server for Oracle WebCenter Content.

...Coming soon..

I've used this swagger file to help enable MCP Tools for:

• Document Management: Search, download, upload, update, delete documents and revisions
• Folder Operations: Create, delete folders, manage files within folders, create file links
• Metadata Operations: Get and update document metadata with versioning support
• Workflow Management: Create, update, approve, reject workflows; checkout/reverse checkout documents
• Public & Application Links: Create and manage public links and application links for files and folders
• Background Jobs: Start and monitor bulk operations (delete, download, category management)
• Taxonomies: Create, update, and manage taxonomies for document categorization
• System Operations: Query data sources, manage document types, get system configuration
• Attachments: Add, download, list, and delete document attachments
• Storage Management: Update storage tiers and restore documents from archive
• Capabilities: Test document and folder permissions and capabilities
• Conversion Management: Resubmit failed document conversions