case studies · SDK conformance

Real SDKs, real clients, local mocks

stunt ships a conformance harness that drives official provider SDKs against its own adapters — and every page below is grounded in what those suites actually assert, in stunt's CI, on every commit. These are the runs that found the bugs: ids that arrived as strings, Link headers that pointed at production, callbacks no receiver could verify.

stripe-go + stripe-node

Stripe

stripe-go and stripe-node run against a local mock — webhooks verify through the SDKs’ own constructEvent.

Customer create + get round-trip PaymentIntent create + confirm walks the rThe SDK iterator auto-walks has_more / sta

go-github + octokit

GitHub

octokit.paginate walks the mock’s Link headers page by page — go-github drives the same CRUD in Go.

Issues.Create assigns numbers; state transgo-github parses Link headers into resp.Neoctokit.paginate follows the Link header U

twilio-go + twilio-node

Twilio

Status callbacks arrive in Twilio’s real form-param shape and verify through twilio-node’s own validateRequest.

Message create returns an SM sid; SDK fetcThe +15005550001 magic number fails like pList filters (To=) return only matching me

go-shopify

Shopify

go-shopify’s paginator follows page_info cursors, and its VerifyWebhookRequest accepts the mock’s HMAC-signed deliveries.

Webhook registration through the SDK (ordeOrder creates with line items and embeddedfinancial_status derives from the transact

want your stack here? the harness is open — each new SDK is a file in conformance/. Six SDK families run today: 63 checks, every one green in CI.