· By Elena Rostova · Developer Experience

Automating QA Release Distribution from GitHub Actions & Fastlane with Signed Webhooks

Shipping signed Ad-Hoc IPAs and Android APKs straight from CI pipelines with SHA-256 hashed tokens, README SVG badges, and HMAC-SHA256 outbox callbacks.

Manual drag-and-drop uploads are ideal for quick local fixes, while release engineering teams want every merged pull request on release/* to publish an over-the-air link and post the QR code into Slack or Linear automatically.

Stateless CI upload & polling workflow

From /dashboard/api-access, generate a personal API token (BuildDrop stores only its SHA-256 digest and displays the plaintext secret once). Your CI pipeline uploads in two calls:

# 1. Push the signed build artifact
JOB_JSON=$(curl -sS -X POST https://yourdomain.com/api/upload \
  -F "token=${BUILDDROP_TOKEN}" \
  -F "file=@build/OrbitDispatch-rc1.ipa" \
  -F "comment=Commit ${GITHUB_SHA::7} — QA Release Candidate")

# 2. Poll /api/status every 2 seconds until status == 2000

Once processing finishes, /api/status returns status: 2000 with the canonical hash, link, qrcode PNG URL, and—when custom domains are attached—full links and qrcodes arrays for your branded hostname.

Verified X-Signature HMAC-SHA256 webhooks

Instead of polling in downstream chatbots, configure a Callback URL in /dashboard/preferences/notifications:

  • Saving a callback endpoint sends a synchronous {"type": "verification", "token": "…"} POST that requires an HTTP 200 acknowledgement before activating.
  • Every subsequent upload, installation, availability, and entitlement event is written to the transactional outbox table and signed with X-Signature: sha256=<hmac> using your account's secret key, with automatic exponential backoff (1 min, 5 min, 30 min, 2 h) if your receiver is temporarily deploying.