--- title: "#fetchsandbox articles | Hashnode" description: "Explore 11 articles tagged #fetchsandbox on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/fetchsandbox" --- Tag # #fetchsandbox 11 posts · 0 followers [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [Sep 12](https://hashnode.com/posts/your-paddle-webhook-is-signed-the-seat-count-is-not/6aa54b002225ea69fed183a2) ### [Your Paddle Webhook Is Signed. The Seat Count Is Not.](https://fetchsandbox.hashnode.dev/your-paddle-webhook-is-signed-the-seat-count-is-not?utm_source=hashnode&utm_medium=feed) Paddle custom\_data can come from browser checkout code. Verify the signature, then grant seats from paid line items, not client metadata. 5 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/your-paddle-webhook-is-signed-the-seat-count-is-not?utm_source=hashnode&utm_medium=feed) [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [Sep 7](https://hashnode.com/posts/your-paypal-refund-worked-your-lovable-app-says-it-failed/6a9ebd34eaa722f491c635b9) ### [Your PayPal Refund Worked. Your Lovable App Says It Failed.](https://fetchsandbox.hashnode.dev/your-paypal-refund-worked-your-lovable-app-says-it-failed?utm_source=hashnode&utm_medium=feed) A timeout makes your app retry a PayPal refund. The second call returns 422, even though the money is already back. Test that branch before launch. 5 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/your-paypal-refund-worked-your-lovable-app-says-it-failed?utm_source=hashnode&utm_medium=feed) [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [Aug 11](https://hashnode.com/posts/green-passed-the-fix-granted-zero-seats/6a7b326fa40b28f8db7fa82a) ### [Green passed. The fix granted zero seats.](https://fetchsandbox.hashnode.dev/green-passed-the-fix-granted-zero-seats?utm_source=hashnode&utm_medium=feed) An AI agent "fixed" a Stripe webhook that double-granted seats. CI went green. Paying customers got nothing. The check only asked whether the count stopped growing 6 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/green-passed-the-fix-granted-zero-seats?utm_source=hashnode&utm_medium=feed) [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [Jul 30](https://hashnode.com/posts/why-paddle-s-subscription-activated-arrives-before-subscription-created/6a6b5a8f41672ee011185ef1) ### [Why Paddle's subscription.activated arrives before subscription.created](https://fetchsandbox.hashnode.dev/why-paddle-s-subscription-activated-arrives-before-subscription-created?utm_source=hashnode&utm_medium=feed) You'd think webhook events fire in order. Paddle disagrees. Here's what happens and how to handle it. 3 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/why-paddle-s-subscription-activated-arrives-before-subscription-created?utm_source=hashnode&utm_medium=feed) [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [Jun 12](https://hashnode.com/posts/workos-directory-sync-webhooks-need-reconciliation-after-okta-group-renames/6a2b87c4ec12ea605ce4b6b8) ### [WorkOS directory sync webhooks need reconciliation after Okta group renames](https://fetchsandbox.hashnode.dev/workos-directory-sync-webhooks-need-reconciliation-after-okta-group-renames?utm_source=hashnode&utm_medium=feed) Okta group renames can arrive through WorkOS directory sync as partial webhook events. If feature gates trust the payload, users split by cache state. Re-fetch the group and users before gating. 4 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/workos-directory-sync-webhooks-need-reconciliation-after-okta-group-renames?utm_source=hashnode&utm_medium=feed) [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [Jun 9](https://hashnode.com/posts/clerk-jwt-401-on-the-server-check-these-3-env-vars-first/6a283f3125e2d48cbde3e770) ### [Clerk JWT 401 on the server? Check these 3 env vars first](https://fetchsandbox.hashnode.dev/clerk-jwt-401-on-the-server-check-these-3-env-vars-first?utm_source=hashnode&utm_medium=feed) A narrow Clerk auth bug: server-side JWT verification can fail with 401 when your publishable key, secret key, and issuer come from different Clerk instances. 2 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/clerk-jwt-401-on-the-server-check-these-3-env-vars-first?utm_source=hashnode&utm_medium=feed) [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [May 27](https://hashnode.com/posts/brownfield-slack-alerts-a-6-minute-guided-mcp-run-on-stripe-resend-webhooks/6a1704cbbadcd8afcbff4f0c) ### [Brownfield Slack alerts: a 6-minute guided MCP run on Stripe + Resend webhooks](https://fetchsandbox.hashnode.dev/brownfield-slack-alerts-a-6-minute-guided-mcp-run-on-stripe-resend-webhooks?utm_source=hashnode&utm_medium=feed) Raw walkthrough of adding Slack notifications for failed payments in a repo that already had Stripe, Clerk, and Resend — introspect, route, prove upstream events, and name honest limits. 3 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/brownfield-slack-alerts-a-6-minute-guided-mcp-run-on-stripe-resend-webhooks?utm_source=hashnode&utm_medium=feed) [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [May 23](https://hashnode.com/posts/test-resend-webhook-reconciliation-before-production/6a11c28a1a3cf7bffc2fde72) ### [Test Resend webhook reconciliation before production](https://fetchsandbox.hashnode.dev/test-resend-webhook-reconciliation-before-production?utm_source=hashnode&utm_medium=feed) Sending an email gives you an ID. The harder part is proving your app can reconcile delivered, bounced, and opened events back to the right record. 4 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/test-resend-webhook-reconciliation-before-production?utm_source=hashnode&utm_medium=feed) [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [May 19](https://hashnode.com/posts/testing-resend-is-not-just-post-emails/6a0c657588372774115403b4) ### [Testing Resend is not just POST /emails](https://fetchsandbox.hashnode.dev/testing-resend-is-not-just-post-emails?utm_source=hashnode&utm_medium=feed) Sending an email is easy. The integration pain starts when you need delivery status, webhooks, and app state you can trust 3 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/testing-resend-is-not-just-post-emails?utm_source=hashnode&utm_medium=feed) [Raj Nagulapalle](https://hashnode.com/@fetchsandbox) · [May 12](https://hashnode.com/posts/test-cal-com-booking-flows-without-calendar-chaos/6a033564937b84f7798c2bf7) ### [Test Cal.com booking flows without calendar chaos](https://fetchsandbox.hashnode.dev/test-cal-com-booking-flows-without-calendar-chaos?utm_source=hashnode&utm_medium=feed) A narrow Cal.com API testing note: create, fetch, reschedule, cancel, and verify the calendar identity before users see duplicate events. 4 min read · [fetchsandbox.hashnode.dev](https://fetchsandbox.hashnode.dev/test-cal-com-booking-flows-without-calendar-chaos?utm_source=hashnode&utm_medium=feed)