How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
xavio-in

xavio-in Stories API

Publish + manage stories.

Documentation Provider Profile APIs.io OpenAPI GitHub

xavio-in Stories API is one of 9 APIs that xavio-in publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Stories. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 6 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://nafafy.com.

6 operations 4 paths 4 schemas 1 DELETE2 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://nafafy.com
Authentication
HTTP Bearer
Contact
Nafafy support
Resource Areas
1

Authentication & Security 1

xavio-in Stories API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (nf_live_<32-char> | nf_test_<64-char>) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Stories 6

Publish + manage stories.

POST
/api/v1/stories
Publish a story (or multi-slide cluster) with optional inline overlays
postApiV1Stories body → 201401402422
GET
/api/v1/stories/{id}
Fetch one story (cluster head)
getApiV1StoriesById 1 param → 200
PATCH
/api/v1/stories/{id}
Update mutable fields (caption, audience, etc)
patchApiV1StoriesById 1 param → 200
DELETE
/api/v1/stories/{id}
Soft-delete the cluster
deleteApiV1StoriesById 1 param → 204
POST
/api/v1/stories/{id}/components
Attach an overlay component to an existing story
postApiV1StoriesByIdComponents 1 param body → 201404422
GET
/api/v1/components
Catalog filtered by the caller's tier (auth-gated)
getApiV1Components → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are CreateStoryRequest (8 properties), Background (6 properties), Overlay (5 properties), AddComponentRequest (4 properties). Each schema is shown below with its type and property counts.

CreateStoryRequest
object
8 properties 2 required
Overlay
object
5 properties 2 required
AddComponentRequest
object
4 properties 2 required
Background
object
6 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xavio-in-stories-api-openapi.yml Raw ↑

Other APIs xavio-in publishes across the network.

xavio-in Bookings API
AE Profile APIs.io
xavio-in Discovery API
AE Profile APIs.io
xavio-in Leads API
AE Profile APIs.io
xavio-in MCP API
AE Profile APIs.io
xavio-in Orders API
AE Profile APIs.io
xavio-in Products API
AE Profile APIs.io
xavio-in Uploads API
AE Profile APIs.io
xavio-in Webhooks API
AE Profile APIs.io
#Stories
← Back to X APIs
API Details
ID
xavio-in:xavio-in-stories-api
Base URL
https://nafafy.com
Docs
https://nafafy.com/developers
Provider
xavio-in
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=xavio-in-stories-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/xavio-in-stories-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of xavio-in Stories API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.