February 2025 Summaries

Svix has overhauled its SDKs, ensuring they are now 100% automatically generated and consistent across languages. This change was made to improve consistency and reduce the time it takes for new functionality to be added. Additionally, Svix has released FIFO Endpoints, which allow webhook consumers to receive webhooks in strict first-in-first-out ordering, and added Cron as a source type for its Ingest service, enabling users to send webhooks on a schedule. The company has also improved the source type selector for its Ingest UI and added a user interface for configuring OAuth 2.0 and mTLS webhook authentication through the app portal. These changes aim to enhance the overall quality and consistency of Svix's services.

Svix is an enterprise-ready webhooks sending service that allows developers to build a secure and scalable webhook platform in minutes. The company has recently introduced FIFO Endpoints, which offer strict First-In-First-Out ordering for webhooks, providing a reliable and predictable delivery mechanism. However, this approach comes with tradeoffs, such as reduced throughput due to waiting for successful deliveries before sending the next one. Svix now supports both FIFO and regular endpoints, allowing customers to choose between these two options depending on their use case. The FIFO endpoint view is designed to provide more visibility into the delivery process, including batching configuration and retry policies. With this new feature, developers can build webhooks that meet specific ordering requirements, while also ensuring high throughput and reliability.

Svix is an enterprise-ready webhooks sending service that allows users to build a secure, reliable, and scalable webhook platform in minutes. Webhooks were created for asynchronous server-to-server communications, but they pose challenges when the recipient endpoint is not internet-facing or available. Svix provides durable webhook deliveries behind firewalls and to unreliable endpoints using its Ingest and Polling Endpoints. This approach solves the problems of making endpoints internet-facing and dealing with server downtime, enabling reliable webhook delivery in various scenarios.

This article discusses the benefits of using OpenAPI (formerly known as Swagger) to describe and generate APIs. Svix, a webhooks sending service, uses OpenAPI to ensure its API is robust, secure, reliable, and scalable. By generating an OpenAPI spec from code, Svix can maintain consistency and quality across its API and automatically enforce global rules and conventions. The company's workflow involves writing code, adding annotations and documentation as needed, and having the OpenAPI spec generated automatically. This approach allows for seamless integration with CI/CD pipelines, reducing the risk of accidental API changes. Additionally, utilizing OpenAPI enables Svix to run linting on its specification, generate examples for its SDKs and CLI tool, and keep its API reference docs up-to-date. By adopting this process, Svix aims to improve the quality of its APIs and provide a better experience for its customers.

Svix is a webhooks sending service that enables developers to build secure, reliable, and scalable webhook platforms in minutes. While webhooks are ideal for real-time API notifications, polling may be more suitable in certain situations such as testing webhooks locally or when storing events for compliance reasons. To transform webhooks from any provider into a polling endpoint, developers can use Svix Ingest and Polling Endpoints. The process involves sending webhooks to Svix Ingest, creating a new source, setting up a polling endpoint, and using an API key to poll the endpoint. This allows developers to retrieve events in batches at once, making it more cost-efficient and easier for compliance purposes.