Narrato API

Name: Narrato API API
Brand: Narrato API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey12 EndpointsREST

For Agents

Manage content workspaces, projects, tasks, and templates in Narrato. Read and update task content sections via Authorization token.

Connect the Narrato API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Narrato API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Narrato API API.

List the workspaces and projects accessible to the authenticated Narrato account

Create new projects and folders to organise content briefs

Read content sections and metadata for an existing task

Update task metadata and status to drive a content production workflow

GET STARTED

Start building with Narrato API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Narrato API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Narrato API, keeping it validated and agent-ready. Narrato is a content workspace platform used by marketing teams to plan, brief, write, and publish content. The API exposes 12 endpoints covering workspaces, projects, folders, tasks, content sections and metadata, workflow statuses, and reusable content templates. Authentication is by Authorization header token, and the endpoint set covers the operations marketing automations need: list available workspaces and projects, read or update task content, and create new content tasks programmatically.

Use Cases

Patterns agents use Narrato API API for, with concrete tasks.

★ Programmatic Content Brief Creation

Marketing teams generate dozens of content briefs each week from keyword research tools and editorial calendars. POST /create-task accepts brief metadata such as target keyword, word count, and instructions, and POST /projects creates the parent project on demand. This lets ops teams pipe their keyword research directly into Narrato without manual ticket creation.

Read the keyword research CSV, then POST /create-task for each row with the brief, target keyword, and word count populated.

Workflow Automation Across Status Changes

Editors and managers route tasks through statuses such as 'Brief', 'In Progress', 'Editor Review', and 'Published'. By calling GET /tasks and PUT /task/update-meta-data, automations can advance tasks based on external triggers — for example moving to 'Editor Review' when a Google Doc is marked complete or to 'Published' when a CMS webhook fires.

Watch the CMS webhook for new posts and PUT /task/update-meta-data on the matching Narrato task to set status='Published'.

Centralised Content Reporting

Marketing leaders need a roll-up of in-flight content across many projects and workspaces. By looping through GET /workspaces, GET /projects, and GET /tasks, a reporting agent assembles a single dashboard showing volume, status distribution, and SLAs. Workspace templates listed via GET /workspace/templates surface what brief types each team is producing.

Iterate over GET /workspaces and GET /projects then GET /tasks for each project to count tasks by status and email a weekly summary.

AI Agent Content Operations

An AI marketing agent invoked through Jentic can plan and create Narrato briefs in response to natural-language requests like 'spin up content tasks for next month's campaign'. Jentic stores the Narrato Authorization token in the vault, so the agent loads the create-task operation and executes it without seeing the raw token, keeping the workspace credential isolated from the model.

Search Jentic for 'create content task in narrato', load POST /create-task, and execute it for each item in the campaign plan with brief and target keyword fields populated.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for narrato api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/workspaces

List user workspaces

GET

/projects

List projects within a workspace

POST

/projects

Create a project

GET

/tasks

List tasks

GET

/task/meta-data

Read task metadata and content

PUT

/task/update-meta-data

Update task metadata

POST

/create-task

Create a content task with metadata

GET

/workspace/templates

List workspace content templates

GET

/workspaces

List user workspaces

GET

/projects

List projects within a workspace

POST

/projects

Create a project

GET

/tasks

List tasks

GET

/task/meta-data

Read task metadata and content

PUT

/task/update-meta-data

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Narrato Authorization token is stored encrypted in the Jentic vault. Agents receive scoped execution tokens, never the raw token, so workspace access cannot leak via prompts or logs.

Intent-based discovery

Agents search Jentic with intents like 'create content task in narrato' or 'list narrato projects' and Jentic returns the matching operation with its input schema, so the agent can act on the workspace without reading Narrato docs.

Time to first call

Direct integration: 1-2 days to handle auth, pagination, and the task metadata payload. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Contentful API

Headless CMS for publishing the content produced in Narrato

Pair Contentful with Narrato so an agent moves a brief from production into a publish-ready CMS entry once Narrato status is 'Published'.

Complementary

Webflow API

Website builder and CMS for publishing finalised content

Combine Webflow with Narrato so the agent ships a finished Narrato draft directly to a Webflow CMS collection.

Alternative

HubSpot CMS Blog Settings API

HubSpot blog configuration within the CMS suite

Choose HubSpot CMS when content production lives natively inside a HubSpot CMS workflow rather than a dedicated content workspace tool.

FAQs

Specific to using Narrato API API through Jentic.

Why is there no official OpenAPI spec for Narrato API?

Narrato does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Narrato API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Narrato API use?

Narrato uses an API token sent in the Authorization HTTP header. When called through Jentic the token is encrypted in the MAXsystem vault and the agent receives a scoped execution token; the raw Authorization value never enters the agent's context.

Can I create a content task with the Narrato API?

Yes. POST /create-task accepts metadata fields like brief, target keyword, word count, due date, and assignee, and creates the task in the chosen project or folder. Use POST /projects and POST /folders first if you need to scaffold the destination structure.

How do I update task status with the Narrato API?

Call PUT /task/update-meta-data with the task ID and the metadata fields you want to change, including the workflow status. Read the available statuses for the parent project first via GET /status to ensure the value you set is valid.

What are the rate limits for the Narrato API?

Narrato does not publish formal rate limits in the spec. Treat sequential project and task fetches as the heavy operations and add a small delay between requests when iterating across many workspaces. Cache GET /workspaces and GET /projects responses because they change infrequently within a session.

How do I create a Narrato content task through Jentic?

Run jentic.search('create content task in narrato'), load the POST /create-task operation, then jentic.execute with the task brief, target keyword, and project ID. Jentic injects the Authorization token from the vault and returns the created task ID for downstream automation.