Elocuenti · Schema
KnowledgeEntryCreateBody
The entry to create. `title` and `content` are required. Send `external_id` to find the entry later by your own identifier (and to keep it in sync with `PUT /api/v1/kb/entries`).
CompanyArtificial IntelligenceConversational AIOmnichannelAutomationIntegration
Properties
| Name | Type | Description |
|---|---|---|
| title | string | The title of the entry, from 1 to 200 characters. The AI reads it as the heading of the entry. |
| content | string | What the AI can say about the topic, in plain text: from 10 to 20000 characters. Write it the way you would explain it to a customer. |
| category | object | A label to group entries in the dashboard (up to 100 characters). Send `null` to remove it. If you leave it out, the current one stays. |
| type | string | `faq` for a question with its answer, `general` for any other piece of information. If you leave it out, a new entry is `general` and an existing one keeps its type. |
| status | string | `published`: the AI uses the entry. `archived`: it stays in your business, unused, and can be published again. Left out, a new entry is `published` and an existing one keeps its status, except one tha |
| external_id | string | The identifier the entry has in your own system (a post of your CMS, an article of your help center): from 1 to 200 printable characters, with no spaces. It is unique in your business: one identifier |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/elocuenti-com/json-schema/elocuenti-com-knowledge-entry-create-body-schema.json",
"title": "KnowledgeEntryCreateBody",
"description": "The entry to create. `title` and `content` are required. Send `external_id` to find the entry later by your own identifier (and to keep it in sync with `PUT /api/v1/kb/entries`).",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/elocuenti-com-knowledge-api-openapi.yml#/components/schemas/KnowledgeEntryCreateBody",
"type": "object",
"properties": {
"title": {
"type": "string",
"minLength": 1,
"maxLength": 200,
"description": "The title of the entry, from 1 to 200 characters. The AI reads it as the heading of the entry.",
"title": "Title"
},
"content": {
"type": "string",
"minLength": 10,
"maxLength": 20000,
"description": "What the AI can say about the topic, in plain text: from 10 to 20000 characters. Write it the way you would explain it to a customer.",
"title": "Content"
},
"category": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"maxLength": 100
},
{
"type": "null"
}
],
"description": "A label to group entries in the dashboard (up to 100 characters). Send `null` to remove it. If you leave it out, the current one stays.",
"title": "Category"
},
"type": {
"type": "string",
"enum": [
"general",
"faq"
],
"description": "`faq` for a question with its answer, `general` for any other piece of information. If you leave it out, a new entry is `general` and an existing one keeps its type.",
"title": "Type"
},
"status": {
"type": "string",
"enum": [
"published",
"archived"
],
"description": "`published`: the AI uses the entry. `archived`: it stays in your business, unused, and can be published again. Left out, a new entry is `published` and an existing one keeps its status, except one that a `prune` archived and nobody has changed in the dashboard, published or archived by hand since: sending it brings it back to `published`. Archiving an existing entry (or keeping archived one that a `prune` archived) needs the `knowledge:delete` permission too.",
"title": "Status"
},
"external_id": {
"type": "string",
"minLength": 1,
"maxLength": 200,
"pattern": "^[\\x21-\\x7e]+$",
"description": "The identifier the entry has in your own system (a post of your CMS, an article of your help center): from 1 to 200 printable characters, with no spaces. It is unique in your business: one identifier is one entry.",
"title": "External Id"
}
},
"required": [
"title",
"content"
],
"additionalProperties": false
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/elocuenti-com-knowledge-entry-create-body"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.