Skip to API content
Birdor API v1

API reference · v1

Read changelog

Read API changelog entries, optionally filtered by exact type. Entries include scope, importance and a list of changes.

GET/v1/changelog

Access requirements

Health, metadata, changelog and waitlist routes are public. Catalog reads (GET /v1/tools, /v1/tools/{id}, /v1/colors/*) and POST /v1/tools/query require a tools.read credential; POST /v1/run/* requires tools.run. There is no anonymous access to these routes: send an API key (Bearer OR X-API-Key) from your server, or use the HttpOnly main-site session plus workspace selection and same-origin Origin. Never combine credentials. Every admitted call is metered. Ingress and workspace/actor minute/month limits are separate; waitlist has its own policy.

Implemented interfaces and development screens do not imply public production availability, paid access or a completed payment integration. Confirm access with Birdor before connecting an application. No paid Pro service, activation or cross-device sync is currently delivered. We are validating one repeatable task before building a paid offer.

Parameters

FieldDescription
limitintegerOptionalBetween 1 and 100; default 50.
typestringOptionalTrimmed string, 1–40 characters; exact type filter.

Request example

1. Set the base URL

Request example
curl --request GET "$BIRDOR_API_BASE_URL/v1/changelog" \
  --header "Accept: application/json"

Examples are copied only; this page does not send API requests.

Responses

Illustrative response. Values vary by environment and time.

200Success
HTTP 200
{
  "ok": true,
  "data": [
    {
      "id": "v1-api-contract-hardening",
      "date": "2026-06-01",
      "type": "infra",
      "scope": "api",
      "importance": "minor",
      "title": "Hardened v1 API contracts",
      "summary": "Aligned request tracing, route documentation, and shell-route behavior for the checked-in v1 API.",
      "changes": [
        "CORS preflight now covers every implemented mutation method.",
        "Public shell routes use the shared request id envelope."
      ]
    }
  ],
  "request_id": "req_example",
  "timestamp": "2026-09-26T00:00:00.000Z",
  "meta": {
    "count": 1
  }
}
400Invalid limit or type
414Query string exceeds4096 characters before admission
HTTP 414
{
  "ok": false,
  "code": "QUERY_TOO_LONG",
  "message": "Query string too long",
  "request_id": "req_example",
  "timestamp": "2026-09-26T00:00:00.000Z"
}
429Ingress limit exceeded before admission
HTTP 429
{
  "ok": false,
  "code": "INGRESS_RATE_LIMITED",
  "message": "Ingress request limit exceeded",
  "request_id": "req_example",
  "timestamp": "2026-09-26T00:00:00.000Z"
}
503Ingress protection or route dependency unavailable
HTTP 503
{
  "ok": false,
  "code": "INGRESS_UNAVAILABLE",
  "message": "Ingress protection unavailable",
  "request_id": "req_example",
  "timestamp": "2026-09-26T00:00:00.000Z"
}
Error handling

Example response fields

Fields shown in this example; optional fields can be omitted. Array rows describe the first example element.

okboolean
Application success flag.
dataarray
Endpoint-specific result.
data[].idstring
Resource identifier.
data[].datestring
Recorded date.
data[].typestring
Entry type.
data[].scopestring
Affected area.
data[].importancestring
Change importance.
data[].titlestring
Entry title.
data[].summarystring
Change summary.
data[].changesarray
Recorded changes.
request_idstring
Origin-response identifier matching X-Request-ID; a shared HTTP cache may replay the original trace.
timestampstring
Response creation timestamp.
metaobject
Optional response metadata.
meta.countnumber
Matching item count.