Svix Changelog February 2025

Punxsutawney Phil saw his shadow, though a few extra weeks of winter won't slow us down. Here are some of the things we launched in February.

Overhauled the Svix SDKs

We overhauled all of the Svix SDKs this month! Before this change, our SDKs were 90% automatically generated, and 10% manually written. This meant that some SDKs got new functionality a bit later than others, but also that some parts of the SDK weren't fully consistent. Both within the same programming language, and across languages.

We also replaced the underlying SDK generator we were using with our custom build one. This fixed issues we had with some of the API endpoints (e.g. patch endpoints), but also enables us to add some new functionality that we will be launching soon that wasn't possible with the previous code generators.

With this change the API part of the SDKs is now 100% automatically generated which ensures that all of the SDKs will remain equally up to date and consistent.

I want to thank all our beta testers for the feedback and bug reports as we were making this transition!

One unfortunate side-effect of this is that some of the SDKs had to include minor breaking changes. We made sure to only limit ourselves to breaking changes that (1) can be caught statically at compile time, type checking, or import (for dynamic languages) so that changes are caught before hitting production, and (2) require only minor changes to the code (e.g. renaming option structures, adding a parameter, etc.).

We decided to pull the band-aid and just make this change now, so that going forward the SDKs can be of the quality and consistency that we require.

For the full list of changes please refer to the SDKs' changelog.

FIFO Endpoints

In case you missed it, earlier this month we publicly released FIFO Endpoints. FIFO endpoints let your webhook consumers receive webhooks in strict FIFO ordering (first in first out), unlike regular webhooks which are delivered independently and order is on a best effort basis.

FIFO Endpoints utilizes the same infrastructure we built for for Polling Endpoints, and we will be launching more things utilizing this in the coming weeks!

Please read the announcement post for more information.

Ingest Cron sources

We have added Cron as a source type for Svix Ingest! This means that you can now use Svix Ingest to send you webhooks based on a Cron schedule. You can do it to run batch tasks on a schedule, send daily emails, and other workflows based on a schedule of your choice.

To create a Cron Ingest Source go to the Sources view, click "Add Source", choose Cron, and set the Cron schedule, the payload, and the payload content type. Then you will be able to add webhook endpoints like with any other Ingest Source.

Ingest source type selector

We have made a few improvements to the Svix Ingest UI, including a brand new source type selector. We added a few additional source types this month (AdobeSign, Docusign, and others), and with the long list of supported types, selecting the right one became a bit difficult.

The new selector includes the service icons, as well as the ability to type to filter the list!

Added a UI for configuring OAuth 2.0 and mTLS webhook authentication

The Svix Enterprise tier has supports a variety of advanced authentication types including OAuth 2.0 token refreshes and mTLS. However, until recently these configurations were only supported through the API.

Not anymore! Both OAuth and mTLS can now be configured through the app portal (for customers on the Enterprise tier).

Set endpoint headers when creating an endpoint

We now support setting the custom endpoint headers when creating endpoints through the API. Before this change, you'd need to first create the endpoint and then make a separate call to set the headers, with every webhooks sent between these calls potentially not including the required headers.

This is a smaller change than we usually include on this list, but we had multiple people ask for it in the last few weeks so we figured it's time to add it!

Closing words

As always, please let us know if you have any feedback on the product, or anything else we can add or build to make your lives easier. Both Ingest and Polling Endpoints came from customer feedback, and we are sure ${next_big_thing} will come from feedback as well. No feedback is too small!

For more content like this, make sure to follow us on Twitter, Github, RSS, or our newsletter for the latest updates for the Svix webhook service, or join the discussion on our community Slack.