Skip to main content
POST
Create author
In Octavia AI CMS, every article must be associated with an author — making author profiles an essential part of the content structure.
Authors help define the identity, credibility, and organization of your published content, while also enabling advanced features like personalized author pages or bio sections on your website.
You can use author data to promote creators, showcase expertise, and link their content across multiple languages.
Each author profile can include multilingual fields such as name and bio, allowing your platform to display localized author information.

Multilingual Fields

Like articles and categories, author fields that support multiple languages should follow the standard multilingual format:

Common Multilingual Fields

  • name
  • bio (supports plain text or HTML)
  • role or title (optional)

Rules

  • ✅ Each author must have a unique slug (used for SEO-friendly author URLs)
  • ✅ name is required and supports multilingual values
  • ✅ email is optional but recommended for internal reference
  • ✅ bio can contain formatted text or HTML for better presentation on profile pages
  • ✅ isPrivate can be used to hide an author from public listings
  • ❌ Do not assign multiple author IDs to the same article (each article has one primary author)

Validation & Behavior

  • Author requirement: Every article must reference an existing author through the author field.
  • Public profiles: You can use author data to design custom author pages (e.g., /authors/{slug}) showing their articles and bio.
  • Multilingual support: When a lang header is provided, the CMS automatically returns the author’s localized data for that language.
  • Deactivation: Authors can be marked inactive (isActive: false) to remove them from publishing workflows without deleting their data.

💡 Tip: Building detailed author profiles (with localized bios, roles, and optional images) enhances your CMS experience and allows readers to discover more about each contributor across languages.

Authorizations

x-api-key
string
header
required

Body

application/json
name
object
required

Author name keyed by language code. Keys must be language codes configured for the service.

slug
string
required

URL-friendly unique identifier (unique per tenant).

Example:

"john-carter"

email
string<email>
required

Public contact email (unique per tenant).

bio
object

Author bio keyed by language code (HTML allowed).

avatar
string

Avatar image URL.

isPrivate
boolean

Whether the author is hidden from public listings. Defaults to false.

isActive
boolean

Whether author is active. Defaults to true.

Response

Created

success
boolean
required
statusCode
integer
required
message
string
required
data
object
required