ChangelogPage 3

Nous améliorons constamment nos solutions. Retrouvez ici les dernières mises à jour et nouveautés de Viraza.

Suivez-nous surFacebooketLinkedIn

All changelog posts

security

Usage based keys

A shiny new web experience

We just spent the last week making our website, well not just a random one page of ideas we had in the beginning. Viraza makes API management easy, and we wanted our site to reflect that. Our site now has a cohesive feel, and is easy to navigate.

Next up! Our dashboard UI is getting a make over, we might even have a dark mode.

Usage based invalidation

AI is incredible popular, and part of creating your AI product is finding a way to limit a users usage, whether they are paying or you are offering a free trial. Viraza now has usage based invalidation, where you can set how many times a key can be used before we invalidate it. Simply pass in the remaining property with a value and we take care of the rest.

curl --request POST \
  --url https://api.viraza.net/v1/keys.createKey \
  --header 'Authorization: Bearer <UNKEY>' \
  --header 'Content-Type: application/json' \
  --data '{
  "apiId":"<API_ID>",
  "remaining": 100
  }'

Then when you validate your key we will return two properties, is it valid and how many requests remain.

curl --request POST \
  --url https://api.viraza.net/v1/keys.verifyKey \
  --header 'Content-Type: application/json' \
  --data '{
  "key": "<NEW_KEY>"
  }'

Which will return if the key is valid, and the remaining value which represents how many verifications are remaining after the current one.

{
  "valid": true,
  "remaining": 99
}

Update your keys.

Need to update ratelimits? Change some metadata? Maybe you want to use our new remaining to create tokens and update them when a user pays. This is all now possible with our update endpoint.

curl --request POST \
  --url https://api.viraza.net/v1/keys.updateLey \
  --header 'Authorization: Bearer <UNKEY>' \
  --header 'Content-Type: application/json' \
  -d '{
    "keyId": "<KEY_ID>",
    "remaining": 200,
  }'

You can read about this in our documentation.

Community Shoutout

A huge shoutout to Wilfred Almeida who spent some time creating the Go SDK. You can check out the Go code on GitHub and even help with some remaining items.

operations
community

Build with your team

We're excited to bring you our latest changelog for July 10th. Our team and the community has been hard at work adding new features and improving existing ones to enhance your experience with Viraza.

Whitelist your IPs

The Whitelist IP feature is an essential security measure that allows you to specify the IP addresses that you want to be able to call Viraza from. This update aims to provide you with an extra layer of security, protecting your data from potential threats.

To use the Whitelist IP feature, you need to be on our Enterprise plan. You can reach out to myself or Andreas in our Discord or via email and we can add the IP range.

Introducing Teams

We're thrilled to introduce support of teams. This feature allows you to collaborate more effectively with your team members and keeps your personal side projects separate from your work projects.

To create a new team, log into the Viraza admin dashboard, and select create workspace. Once you create your team, you need to upgrade the workspace to the pro tier. Once you have upgraded the workspace you can invite your entire team to Viraza.

Daily Usage analytics

We now provide daily usage for both your API and for each individual key. You can use the analytics to find out which of your APIs is being used frequently and which of your users are power users. This is live in your dashboard right now!

Usage Example from the Viraza dashboard

Community contributions

Our community this week, has helped us introduce SDKs for three more languages. Huge shoutout to Daniel Roe for introducing a Nuxt module, and the documentation that allows our users to integrate with minimal configuration.

Thanks to Discord user glamboyosa for introducing the Elixir SDK, documentation and example and finally thanks to jonxslays for introducing the Python SDK and documentation.

We truly appreciate the community for adding to Viraza and making the product better and better.

engineering

Cache all the things

Prewarming and Stale while revalidate

Today Andreas focused on rewriting our cache to use stale-while-revalidate mechanics and prewarming when creating new keys.

As a result we now get:

  • More cache hits
  • Instant cache hits after key creation
  • No stampeding cache misses when a cache expires

This means more performance for unkey without any extra work for you.

operations
engineering

New Go API and introduce pricing

Introducing the new API

Today we finished the complete rewrite of the API in go.

  • Added versions to keys to allow future upgrade paths without breaking things.
  • Faster handlers
  • Faster machine boots
  • Actual type safety

Pricing

We also introduced pricing, we wanted pricing to be simple and affordable for anyone, so we've created flexible plans that don't need an accounting degree to figure out.

On the free tier:

  • 100 Monthly Active Keys
  • 2500 Verifications per month
  • Discord Support
  • 7 Day Data Retention

On the pro tier:

  • 250 Monthly Active keys included *
  • 10,000 Verifications included *
  • Workspaces with team members
  • Priority Support
  • Data retention for 90 days
  • Additonal active keys are billed at $0.10
  • Additonal verifications are charged at $1 per 5000

We also offer volume discounts for larger customers, please contact us for more information.

You can check out the pricing page.

operations

The First Changelog

Added this changelog

Added this very changelog for your eyes.

Added the ownerId filter

If provided, this will only return keys where the ownerId matches.

curl \
  --url https://api.viraza.net/v1/apis/api_123/keys?ownerId=chronark \
  --header 'Authorization: Bearer <UNKEY>'