DocumentationSDKsCLIAPI Reference
Console
Spec versions

List the specs this project has generated from

The audit trail behind a regeneration: which spec produced which SDK, and when it changed. Content is omitted from the list because specs run to megabytes.

GET
/projects/{project_id}/spec_versions

The audit trail behind a regeneration: which spec produced which SDK, and when it changed. Content is omitted from the list because specs run to megabytes.

Authorization

apiKey
AuthorizationBearer <token>

API key from the console, ak_....

In: header

Path Parameters

project_id*string

Query Parameters

limit?integer
Range1 <= value <= 100
cursor?string

Response Body

application/json

application/json

application/json

curl -X GET "https://example.com/projects/string/spec_versions"
{  "data": [    {      "id": "string",      "object": "spec_version",      "project_id": "string",      "hash": "string",      "bytes": 0,      "source": {},      "content": "string",      "content_omitted": true,      "created_at": "2019-08-24T14:15:22Z"    }  ],  "next_cursor": "string"}

Fetch one file from a generation GET

Raw file content, for generations whose output was too large to inline (files_omitted true). The generation's files_index lists valid paths.

Retrieve a spec version GET

One recorded spec, with its content. Storing every spec a project has generated from is only an audit trail if you can read one back and diff it against what shipped.