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

CoreStory sections API

The sections API from CoreStory — 7 operation(s) for sections.

CoreStory sections API is one of 47 APIs that CoreStory publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sections. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 8 operations across 7 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.26.2.

Requests are made against a single base URL, /.

8 operations 7 paths 12 schemas 5 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.26.2
Base URL
https://c2s.corestory.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

CoreStory sections API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Enter the Bearer token from Clerk authentication

Paths & Operations 8

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

sections 8
POST
/api/projects/{project_id}/sections/{section_name}/generate
Generate a specific section.
generate_section 2 params body → 200default
POST
/api/projects/{project_id}/sections/generate-all
Generate all sections (PRD + Tech Spec) in background.
generate_all_sections 1 param body → 200default
GET
/api/projects/{project_id}/sections/tech-user-stories/catalog
Get a catalog of tech-user-story facets for UI browsing.
get_tech_user_stories_section_catalog 1 param → 200default
GET
/api/projects/{project_id}/sections/user-stories/catalog
Get a catalog of user-story facets for UI browsing.
get_user_stories_section_catalog 1 param → 200default
GET
/api/projects/{project_id}/sections
Get all sections (PRD + Tech Spec) for the project.
get_all_sections 2 params → 200default
GET
/api/projects/{project_id}/sections/{section_name}
Get a single section by name.
get_section 10 params → 200default
PATCH
/api/projects/{project_id}/sections/{section_name}
Update a section.
update_section 3 params body → 200default
GET
/api/sections/catalog
List all document section names (PRD + Tech Spec).
get_section_catalog → 200default

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are AllSectionsResponse (24 properties), SectionResponse (13 properties), PaginationMeta (4 properties), ErrorBody (3 properties). Each schema is shown below with its type and property counts.

AllSectionsResponse
object
Combined PRD + Tech-Spec sections response for unified /sections/ endpoint.
24 properties 2 required
PaginationMeta
object
4 properties 4 required
GeneratePRDSectionRequest
object
2 properties
BasicSuccessResponse
object
Use this for returns for deletes and patches. UI ALWAYS needs some payload return. This just standarizes it.
1 property
GenerateAllRequest
object
1 property
DocumentSectionsDashedEnum
string
PRD + tech-spec sections only (no retriever). Use for user-facing endpoints.
PRDCustomPromptRequest
object
2 properties 2 required
SectionResponse
object
Single-section response for GET /sections/{sectionname}. Content is always in the content field regardless of which section was requested. The sectionname fiel…
13 properties 4 required
SpecFormat
string
Self-documenting label for the format a generated spec is in. Derived from contentversion and surfaced on API responses so the viewer (and any API consumer) re…
ErrorBody
object
3 properties 2 required
ErrorSchema
object
1 property 1 required
LanguageInfo
object
Language information with code and native display name.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

corestory-sections-api-openapi.yml Raw ↑

Other APIs CoreStory publishes across the network.

CoreStory admin API
CoreStory api_debugging API
CoreStory api_key_management API
CoreStory artifacts API
CoreStory billing API
CoreStory cache API
CoreStory ciu API
CoreStory clerk_authentication API
CoreStory context API
CoreStory conversations API
CoreStory discovery API
CoreStory document_formatters API
Where this information came from

This is an independent, third-party profile of CoreStory sections 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.