Skip to main content
Notable, developer-facing changes to the Phosra API, the platform conventions, and the published SDKs — newest first. API version v1 is additive: entries here add capability or documentation, they do not break existing v1 calls.
Version and date facts on this page are drawn from the public npm registry and the live sandbox census. For how versions pin together, see Versioning. For the SDK packages, see the SDK overview.
​
2026-07-06
Platform-conventions reference
New reference pages for the cross-cutting platform contracts, each verified against the live sandbox:
  • Rate limits — the 100 req/min default, the X-RateLimit-* + Retry-After headers, and copy-paste backoff in four languages.
  • Pagination — the two list shapes (offset arrays on the product plane, next_cursor envelopes on the census rails) and how to walk each.
  • Idempotency — where the key lives (there is no Idempotency-Key header), the 200 + OCSS-Replay: original faithful-replay contract, and the 409 replay pitfall.
  • Versioning — the API path, OCSS-v1.0-pre, dated Annex B editions, ETag/If-None-Match, and exact SDK pinning.
​
2026-07-04
SDK releases
  • @openchildsafety/ocss 0.1.3 — the OCSS protocol + RFC 9421 request signer (signRequest) used across the signed examples in these docs.
  • @phosra/link 0.1.2 — parent-facing connect flow.
  • @phosra/gatekeeper 0.2.2 — tighten-only enforcement overlay.
Pin exact (0.x minors may break) — see SDK versioning.
​
2026-06-28
Developer platform + first SDK line
  • Self-serve developer orgs — sign up, auto-provision a dev org, and mint a phosra_test_ key with no sales call. See Create an account.
  • @phosra/sdk 0.1.0 — the first published server SDK line.
  • @phosra/cli 0.2.0 and @phosra/mcp 0.4.0 published.
  • Free-tier orgs default to 100 requests/minute (Rate limits).
​
2026-05-15
MCP server
  • First release of the @phosra/mcp MCP server, exposing Phosra tools to agents. See the MCP server SDK.

​
Current platform conventions

These are the standing contracts of the v1 surface, not point-in-time releases. They are documented and verified on their own pages:
ConventionValueReference
API version/api/v1 (in the path)Versioning
OCSS spec versionOCSS-v1.0-preVersioning
Default rate limit100 req / 60 s (free tier)Rate limits
Idempotency markerOCSS-Replay: original on faithful replaysIdempotency
Error classesclosed set of sevenErrors
Looking for infrastructure status and incidents rather than API changes? That lives on the status page.