Flintwake
Sign inStart free

Changelog

Shipped every other Tuesday, written for the person debugging.

Breaking changes first, deprecations with a date, and enough detail to tell you whether last week's problem was ours.

  1. 2026.09.215 September 2026

    Replay diffing and per-consumer limit overrides

    • AddedReplay now returns a structural diff between the original response and the replayed one, with numeric tolerance configurable per endpoint.
    • AddedRate-limit overrides can be set per consumer from the console and are written to the audit log.
    • ChangedThe request explorer keeps its filters in the URL, so a filtered view can be shared with a teammate.
    • ChangedWake retention is now set per environment rather than per account.
  2. 2026.09.11 September 2026

    Rust SDK, AP data residency

    • AddedOfficial Rust SDK (`flintwake` on crates.io) with async support and the same verification helpers as the other six clients.
    • AddedAP data residency. Projects can now be pinned to ap-southeast-2 alongside the existing US and EU regions.
    • FixedWebhook signature verification in the PHP SDK rejected payloads containing a literal `\r`. Fixed in 3.4.1.
    • FixedThe endpoint health table sorted p99 as a string when the value exceeded 1,000ms.
  3. 2026.08.218 August 2026

    Deploy markers and SLO burn-rate alerts

    • AddedDeploy markers. Post a release to `/v2/deploys` and every latency chart annotates it.
    • AddedSLO burn-rate alerts with 1-hour and 6-hour windows, routed through any connected destination.
    • ChangedError attribution now groups by deploy as well as endpoint and consumer.
    • Deprecated`GET /v1/requests` is deprecated in favour of `GET /v2/wakes`. It will be removed on 1 March 2027.
  4. 2026.08.14 August 2026

    Field-level redaction rules

    • AddedRedaction rules are now expressed as JSONPath and evaluated at the collector, before capture.
    • AddedRules can be exported and committed to Git, then applied through the API on deploy.
    • FixedCollectors under sustained memory pressure could drop the last 200ms of a response body. Fixed in collector 4.1.2.
  5. 2026.07.221 July 2026

    Consumer directory

    • AddedA consumer directory with plan, quota, error rate, p95 and an owner field per integration.
    • AddedQuota warning webhooks fire at 80% and 95% of a consumer's allowance.
    • ChangedKeys now show a last-used timestamp accurate to the second rather than the hour.
  6. 2026.07.17 July 2026

    Playground in hosted docs

    • AddedThe API playground is embedded in the hosted documentation and pre-fills the reader's own sandbox key.
    • FixedCopy buttons in Safari 17 copied the trailing newline of a snippet, breaking pasted shell commands.
    • FixedLong endpoint paths overflowed the reference sidebar below 380px.

Subscribe

A changelog nobody can subscribe to is a blog post.

Take the RSS feed, or register a webhook endpoint for the changelog.published event and let your release bot post it in the channel where your integrators live.

This page is the human version
Subscribe programmatically
# RSS
curl https://flintwake.com/changelog/feed.xml

# Or a webhook
curl -X POST https://api.flintwake.com/v2/webhooks/endpoints \
  -H "Authorization: Bearer $FLINTWAKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://hooks.acme.dev/flintwake-releases",
    "events": ["changelog.published"]
  }'

Deprecations always carry a date.

When something is going away you get the endpoint, the replacement and the removal date in the same entry. GET /v1/requests goes on 1 March 2027.

Read the referenceSee the roadmap