Notable updates to the Gooclaim API and partner-facing docs


This changelog tracks user-visible changes to the Gooclaim API, webhook events, and these docs. Subscribe via RSS to get notified when new entries are published.

Entries are tagged by area (api, docs, webhooks, auth, knowledge, breaking-change) so you can filter to what’s relevant to your integration.

May 21, 2026

May 21, 2026

Docs updates

Knowledge Sources pages added

New Quickstart and Advanced Search pages for the Knowledge Layer have been added to the docs, covering how partners can ingest sources and query the Gooclaim knowledge base.

Branding

Replaced the default Fern favicon with the Gooclaim logo across the docs site.

Corrected several broken in-page links that were using shorthand paths. All internal links now use the full /<tab>/<section>/<page> form so they resolve correctly on the live site.

Removed

SDK section

The “SDKs” section on the API Reference Overview has been removed for now. Generated SDKs (Python, Node.js, Go) will be announced here once they are actually published. Until then, integrate directly against the REST API documented in this reference.


May 20, 2026

May 20, 2026

Initial release

The Gooclaim v1.0 API reference is now live at api.docs.gooclaim.com.

What’s documented

  • Auth Service — JWT issuance via POST /v1/auth/token, token introspection, and the Authorization: Bearer pattern used on every other endpoint.
  • Workflow Engine — three workflows for the v1.0 pilot: Claim Status, Pending Documents, and Query Reason.
  • Audit Ledger — tenant-scoped read API for retrieving immutable audit events.
  • Webhooks — AsyncAPI schemas for outbound events partners can subscribe to.

Conventions

  • All business endpoints are mounted under /v1/*. Health, readiness, metrics, and OpenAPI live at root.
  • PHI fields (claim IDs, phone numbers, names) are SHA-256 hashed in any returned payload. Plaintext correlation stays in your system.
  • Errors follow RFC 7807 problem-detail JSON with a stable error_code.
  • Mutating endpoints accept an Idempotency-Key header.