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 sync-status API

The sync-status API from CoreStory — 1 operation(s) for sync-status.

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

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

This API exposes 1 operation across 1 path, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.26.2.

Requests are made against a single base URL, /.

1 operations 1 paths 8 schemas 1 GET

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 sync-status 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 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

sync-status 1
GET
/api/organizations/projects/sync-status
List org projects with sync status
list_project_sync_status 5 params → 200default404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are SyncStatusItem (5 properties), SyncStatusSummary (4 properties), PaginationMeta (4 properties), SyncStatusResponse (3 properties). Each schema is shown below with its type and property counts.

PaginationMeta
object
4 properties 4 required
SyncStatusItem
object
A single project row in the org project sync-status list.
5 properties 4 required
SyncStatusResponse
object
Paginated project sync-status list with org-wide summary aggregates.
3 properties 3 required
SyncMode
string
Whether a project syncs manually or automatically with its repo.
ErrorBody
object
3 properties 2 required
ErrorSchema
object
1 property 1 required
SyncStatusSummary
object
Org-wide aggregates rendered as page-level chrome. Not affected by filters.
4 properties 4 required
ProjectSyncStatus
string
Sync/processing status for a project in the org roster.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

corestory-sync-status-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 sync-status 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.