zonelessdev/zoneless

Add Webhook Delivery module Parent: #172 Blocked by: #173 Goal Add an internal API module that can create, persist and retrieve WebhookDelivery records using the types introduced in #173 This establishes the persistence layer without changing existing webhook dispatch behaviour. Proposed solution Create apps/api/src/modules/WebhookDelivery.ts containing a WebhookDeliveryModule. The module should initially support: Creating and persisting a WebhookDelivery. Retrieving a WebhookDelivery by ID. Returning null when a delivery does not exist. New deliveries should: Use a generated ID with the whd_z prefix. Reference one Event and one Webhook Endpoint. Start with pending status. Have delivered_at and claim_until set to null. Have an empty attempts array. Set next_attempt_at so the initial attempt is eligible for processing. Add WebhookDeliveries to the collections initialized by Database.EnsureCollections(). Follow the structure and dependency-injection patterns used by existing API modu

WebhookDelivery and WebhookDeliveryAttempt objects Goal Define the WebhookDelivery and WebhookDeliveryAttempt objects within the shared-types folder. Proposed Solution Add WebhookDeliveryAttempts. WebhookDelivery objects as a first step for #[ISSUE] The objects would roughly look like this - however it is okay for the implemetation to differ if there are any other ideas. We should add comments similar to other types in the shared-types folder: export interface WebhookDelivery { id: string; event_id: string; webhook_endpoint_id: string; status: 'pending' | 'retrying' | 'succeeded' | 'failed'; next_attempt_at: number | null; delivered_at: number | null; claim_until: number | null; attempts: WebhookDeliveryAttempt[]; } export interface WebhookDeliveryAttempt { attempt_number: number; attempted_at: number; completed_at: number; result: 'succeeded' | 'http_error' | 'timed_out' | 'network_error'; http_status: number | null; duration_ms: number; error: string | n

Webhook retries Goal Currently webhooks on Zoneless are fire and forget, if the webhook fails to deliver, then we don't retry it. This is bad behaviour, as the platform using Zoneless might miss critical events due to being temporarily down. Proposed Solution We create a new initial simple system within Zoneless for retrying failed webhooks. Webhooks essentially deliver Event objects, however we would need a new system to track Webhook Delivery Attempts. The proposed solution would be to create a new WebhookDelivery system, that acts as a parent object for tracking WebhookDeliveryAttempts. WebhookDelivery objects are linked to the Event they are trying to send and the WebhookEndpoint they are being sent to. The objects would roughly look like this - however it is okay for the implemetation to differ based on the findings by the implementation: export interface WebhookDelivery { id: string; event_id: string; webhook_endpoint_id: string; status: 'pending' | 'retrying' | 'succeede

Add Subscription Items API documentation Context Zoneless is adding Subscription Item support through #159, with corresponding Node SDK support tracked separately. The public API reference should document the Subscription Item object and every public endpoint Zoneless supports. Blocked by: #159 and #160 What to build Add Subscription Items to the Zoneless API documentation. Use Stripe's Subscription Items documentation as the structural reference: https://docs.stripe.com/api/subscription_items Follow the API docs conventions in AGENTS.md. Acceptance criteria Add a Subscription Items section to the API reference Document the Subscription Item object and its supported fields Document every public Subscription Item endpoint implemented by Zoneless Include parameters, response examples, and Node SDK examples Node examples use the real zoneless.subscriptionItems.* SDK methods Add the resource to the appropriate docs navigation/catalog npx nx test docs passes Out of scope Documenting Stri

Add Subscription Items to the Node SDK Context Zoneless is adding support for Subscription Item API endpoints in #159. Once those endpoints are available, they should also be exposed through the Node SDK using Stripe-compatible naming and structure. Blocked by: #159 What to build Add Node SDK support for every public Subscription Item endpoint introduced by #159. Use Stripe's Subscription Items API as the reference: https://docs.stripe.com/api/subscription_items Follow the Node SDK conventions in AGENTS.md. Acceptance criteria Add a subscriptionItems resource to the Node SDK Support every public Subscription Item route added in #159 Match Stripe's SDK method names and structure where applicable Use existing shared types and generated input types Wire the resource into the SDK exports Add focused tests npx nx build node-sdk passes Out of scope Adding or changing Subscription Item API endpoints Supporting Stripe functionality that Zoneless does not implement Documentation changes Ple