Kreya 1.18 brings powerful new ways to visualize and validate your API workflows: Data Previews and Snapshot Tests. These features make it easier than ever to understand your API responses and ensure your integrations remain stable over time.

API clients hold sensitive data, from auth tokens to proprietary endpoints. But much control do users retain over their data? And is their privacy respected?

In our previous post, we explored the basics of the protocol buffers (protobuf) wire format. Now, let's take a closer look at some advanced features: packed repeated fields, maps and negative numbers.

Kreya has introduced a powerful new feature: HAR file import! This update makes analysing, replaying and debugging HTTP and gRPC-Web requests directly in Kreya easier than ever. In this post, we’ll show you how to export HAR files from browsers and import them into Kreya. We will also explain why this is a secure and essential workflow for developers, particularly those working with gRPC-Web APIs.

Kreya 1.17 comes with the new Kreya Script, which can control operation invocation with JavaScript. Support has been added for importing HAR files, the JWT auth provider, exporting operations as cURL and gRPCurl commands and many more features have been implemented.

Kreya 1.16 comes with support for WebSocket calls and an updated look and feel for the project settings. Faker is added to the scripting API, cookie management is added and many more features are implemented.

4 million invoked operations, over 4,700 monthly active users and 4 releases. These are some key facts about the past year.

Kreya 1.15 comes with support for protobuf editions. Operation, directory and collection paths can be viewed and copied from the tab's context menu. Comments imported with a proto file are now visible in the declaration tab.

Protocol buffers transform data into a compact binary stream for storage or transmission. In this blog post, we will use a proto definition of a sample message and serialize it to binary data.

Protobuf Editions bring a major change in the way Protocol Buffer versions are handled. Currently there are two versions, "proto2" and "proto3", and the differences between them aren't always obvious. Migrating from proto2 to proto3 isn't easy either. In this blog post we will explore how Protobuf Editions are going to improve this.