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 tech_spec API

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

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

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 21 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 21 schemas 4 GET1 PATCH3 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 tech_spec 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 — 4 GET, 1 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

tech_spec 8
GET
/api/projects/{project_id}/tech-specdeprecated
Get the project's Tech Spec (not base PRD) sections data.
get_tech_spec 2 params → 200default
GET
/api/projects/{project_id}/tech-spec/statusdeprecated
Get the project's tech-spec generation status.
get_tech_spec_status 1 param → 200default
POST
/api/projects/{project_id}/tech-spec/generatedeprecated
Generate the Tech Spec sections (no base PRD sections) for the project.
generate_tech_spec 4 params body → 200default
POST
/api/projects/{project_id}/prd/generate-alldeprecated
Generate all PRD and tech spec sections for the project.
generate_all_prd_sections 1 param body → 200default
GET
/api/projects/{project_id}/tech-spec/tech-user-stories/catalogdeprecated
Get a catalog of user stories items for UI faceted browsing.
get_tech_user_stories_catalog 1 param → 200default
POST
/api/projects/{project_id}/tech-spec/{section_name}/generatedeprecated
Generate a specific Tech Spec section
generate_tech_spec_section 2 params body → 200default
PATCH
/api/projects/{project_id}/tech-spec/{section_name}deprecated
Update the specified Tech Spec section.
update_tech_spec_section 3 params body → 200default
GET
/api/projects/{project_id}/tech-spec/{section_name}deprecated
Get the specified Tech Spec section.
get_tech_spec_section 10 params → 200default

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are TechSpecSingleSectionResponse (19 properties), TechSpecSectionsResponse (19 properties), UserStory (8 properties), JobStatusSummary (5 properties). Each schema is shown below with its type and property counts.

Feature-Input
object
Model for a feature in the technical specification.
3 properties 2 required
GeneratePRDSectionRequest
object
2 properties
JobStatusSummary
object
Lightweight status + progress for a single job type (ingestion, PRD generation, etc.).
5 properties 1 required
NewReference
object
3 properties 1 required
LanguageInfo
object
Language information with code and native display name.
2 properties 2 required
TechSpecStepsDashedEnum
string
All tech spec steps with dashed values.
TechSpecSectionsResponse
object
19 properties 2 required
GenerateTechSpecRequest
object
3 properties
GenerateAllRequest
object
1 property
Reference
object
4 properties 1 required
GenerateTechSpecCustomPromptItem
object
3 properties 2 required
ErrorSchema
object
1 property 1 required
PRDGenerateResponse
object
Response model for PRD generation
3 properties 3 required
TechnicalSpecContext
object
Context model for technical specification generation.
2 properties
PRDCustomPromptRequest
object
2 properties 2 required
UserStory
object
8 properties 7 required
PaginationMeta
object
4 properties 4 required
BasicSuccessResponse
object
Use this for returns for deletes and patches. UI ALWAYS needs some payload return. This just standarizes it.
1 property
TechnicalRequirements
object
4 properties 2 required
ErrorBody
object
3 properties 2 required
TechSpecSingleSectionResponse
object
Used for endpoint to get a single section of a tech spec. Only 1 section is ever output, endpoint sets "don't output None". AKA: Only output the property if it…
19 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

corestory-tech-spec-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 tech_spec 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.