API & webhooks

Pro and above projects can pull their published releases from a REST endpoint, or get a signed webhook posted to their own server the moment a release goes out — useful for wiring Buoylog into Zapier, Make, or your own internal tools.

Pulling releases

Create an API key from your dashboard, then request your project's published releases:

curl https://buoylog.com/api/v1/projects/{projectId}/releases \
  -H "Authorization: Bearer blk_..."

Returns your last 50 published releases, most recent first, with each release's version, one-line summary, and its public entries. Internal-only entries are never included.

Webhooks

Add a webhook URL from your dashboard and Buoylog will send a signedPOSTrequest there every time you publish a release:

{
  "event": "release.published",
  "project": "your-org/your-repo",
  "version": "v1.2.0",
  "url": "https://buoylog.com/your-slug",
  "summary": "This release speeds up exports and fixes a billing bug.",
  "entries": [{ "category": "FIXED", "title": "..." }]
}

Each request carries an X-Buoylog-Signature header — an HMAC-SHA256 of the raw request body, signed with the signing secret shown when you added the webhook. Verify it before trusting the payload:

const expected = "sha256=" + crypto
  .createHmac("sha256", secret)
  .update(rawBody)
  .digest("hex");

Current limitation: there's no Zapier or Make App Directory listing yet — this API and webhook is what a custom integration (or a Zapier "Webhooks by Zapier" trigger) would use in the meantime.