Skip to main content
POST
/
authors
/
create
Create author
curl --request POST \
  --url https://api.octaviatech.app/cms/authors/create \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "name": {
    "en": "John Carter",
    "es": "Juan Carter"
  },
  "slug": "john-carter",
  "bio": {
    "en": "<p>Editor and writer focused on AI topics.</p>",
    "es": "<p>Editor y escritor enfocado en temas de IA.</p>"
  },
  "avatar": "https://cdn.example.com/avatars/john.jpg",
  "role": "Editor",
  "socials": {
    "website": "https://john.example.com",
    "twitter": "https://twitter.com/john",
    "linkedin": "https://www.linkedin.com/in/john"
  },
  "email": "john@example.com",
  "isActive": true,
  "order": 1
}
'
{
  "success": true,
  "statusCode": 201,
  "message": "Created",
  "data": {
    "id": "{{objectId}}",
    "slug": "john-carter"
  }
}
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: 
"name": {
  "en": "John Doe",
  "es": "Juan Pérez",
  ...
}

​
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 in multiple languages

​
slug
string

URL-friendly unique identifier

​
bio
object

Author bio in multiple languages (HTML allowed)

​
avatar
string<uri>

Avatar image URL

​
role
string

Public title/role of the author (e.g., Editor)

​
socials
object

Social and website links

​
email
string<email>

Optional public contact email

​
isActive
boolean

Whether author is active

​
order
integer

Optional ordering index

Required range: x >= 0

Response

Created