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

The prd_version API from CoreStory — 10 operation(s) for prd_version.

CoreStory prd_version 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 11 operations across 10 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.26.2.

Requests are made against a single base URL, /.

11 operations 10 paths 14 schemas 1 DELETE4 GET1 PATCH5 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 prd_version 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 11

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

prd_version 11
GET
/api/projects/{project_id}/prd/versions
List the versions of the given PRD (with per-version diffs vs previous)
list_prd_versions 3 params → 200default
POST
/api/projects/{project_id}/prd/import-steps
Bulk-import PRD/TechSpec step content
import_prd_steps 1 param body → 201default
POST
/api/projects/{project_id}/prd/versions/create-from-latest
Create a new PRD version from the latest steps
create_prd_version_from_latest 1 param → 201default
DELETE
/api/projects/{project_id}/prd/versions/{version_uid}
Delete a PRD Version by uid
delete_prd_version 2 params → 200default
PATCH
/api/projects/{project_id}/prd/versions/{version_uid}
Update a PRD Version (only certain allowed fields)
update_prd_version 2 params body → 200default
GET
/api/projects/{project_id}/prd/versions/diff
Get section names that changed between two PRD versions
diff_prd_versions 3 params → 200default
POST
/api/projects/{project_id}/prd/versions/{version_uid}/promote
Promote a full PRD version (PRD + tech specs) to be the current one
promote_prd_version 2 params → 200default
POST
/api/projects/{project_id}/prd/versions/{version_uid}/{section_name}/promote
Promote a single section from an old version by cloning into a new current version
promote_prd_section 3 params → 200default
POST
/api/projects/{project_id}/tech-spec/versions/{version_uid}/{section_name}/promotedeprecated
Promote a single tech-spec section from an old version by cloning into a new current version
promote_tech_spec_section 3 params → 200default
GET
/api/projects/{project_id}/prd/{section_name}/versions
List PRD versions that include the given section.
list_prd_section_versions 4 params → 200default
GET
/api/projects/{project_id}/tech-spec/{section_name}/versionsdeprecated
List PRD versions that include the given tech-spec section.
list_tech_spec_section_versions 4 params → 200default

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are PRDVersionItemWithDiffResponse (13 properties), PRDVersionItemResponse (12 properties), ErrorBody (3 properties), LanguageInfo (2 properties). Each schema is shown below with its type and property counts.

PRDVersionItemListResponse
object
Response model for paginated list of versions for a given section.
2 properties 1 required
ImportStepsRequest
object
Request body for bulk-importing PRD/TechSpec step content. Accepts a flat JSON object mapping dashed step names to content. Validates that the dict is non-empt…
TechSpecStepsDashedEnum
string
All tech spec steps with dashed values.
PRDVersionItemWithDiffResponse
object
Subclass the item fields above and add the diff'd sections from the previous version in the history of versions.
13 properties 4 required
PRDVersionItemWithDiffListResponse
object
Response model for paginated list of versions for a PRD.
2 properties 1 required
BasicSuccessResponse
object
Use this for returns for deletes and patches. UI ALWAYS needs some payload return. This just standarizes it.
1 property
DocumentSectionsDashedEnum
string
PRD + tech-spec sections only (no retriever). Use for user-facing endpoints.
ImportStepsResponse
object
Response for a successful import-steps call.
2 properties 2 required
PRDVersionDiffResponse
object
1 property
ErrorBody
object
3 properties 2 required
PRDVersionUpdateRequest
object
Allowed updatable fields on a PRD Version.
1 property
ErrorSchema
object
1 property 1 required
LanguageInfo
object
Language information with code and native display name.
2 properties 2 required
PRDVersionItemResponse
object
12 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

corestory-prd-version-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 prd_version 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.