OpenAPI & Custom CMS Integration Guide

Connect any headless CMS or custom content API to Septra using a standard OpenAPI 3.x specification. This allows your AI Content and Growth agents to read published articles, audit content structures, and directly publish new blog posts to your existing CMS (WordPress, Strapi, Sanity, Ghost, or bespoke backends).

---

1. Overview & Value to Your AI Team

Septra supports any content system that exposes a REST API defined by an OpenAPI (formerly Swagger) schema.

Once connected, your AI agents can:

• Read Existing Content: Inspect active blog posts, categories, authors, and metadata to maintain consistent voice and avoid duplicate topics.
• Draft & Format New Posts: Format articles in structured JSON or Markdown matching your CMS content schema.
• 1-Click Publishing: Push finished, approved articles directly to your CMS with featured images, SEO meta descriptions, and tags.

---

2. Prerequisites Before Connecting

1. Septra Workspace Role: Owner, Admin, or Editor permissions.
2. API Base URL: The public HTTPS endpoint of your CMS API (e.g. https://api.yourbrand.com or https://cms.yourdomain.com/api).
3. API Key / Secret Token: A secret authentication key (passed via x-api-key, Authorization: Bearer, etc.).
4. OpenAPI 3.x Specification: The OpenAPI specification in valid YAML or JSON format defining at least one content collection or article creation endpoint.

---

3. Step-by-Step Connection Instructions

Step 1: Open OpenAPI CMS in Septra

1. Go to your Septra Workspace → Intelligence.
2. In the Content Management section, click OpenAPI CMS.

Step 2: Enter API Configuration & Paste Spec

1. API Base URL: Enter your API root URL (e.g. https://api.digitalcontrols.org).
2. API Key: Enter the secret token or access key for your API.
3. OpenAPI Spec: Paste your complete OpenAPI 3.x specification (YAML or JSON) into the code box.
4. Click Connect.

Step 3: Schema Validation & Handshake

1. Septra will validate the schema endpoints, test authentication against your base URL, and register available content collections.
2. Once verified, you will see a green Connected confirmation badge.

---

4. Endpoints & Schema Guidelines

For best results, ensure your OpenAPI specification includes:

• GET endpoint for listing published articles / posts.
• POST endpoint for creating new articles with fields for title, content (Markdown or HTML), slug, excerpt, and featured_image.
• PATCH or PUT endpoint for updating drafts.

---

5. Security & Access Controls

• Encrypted Credential Storage: Your API keys and tokens are encrypted at rest using industry-standard AES-256 encryption.
• Approval Gates for Publishing: Agents cannot publish live articles without your review. Completed drafts are sent to your Tasks board in the In Review column for human sign-off before being dispatched to your CMS.