Oystehr v1.29 — Oystehr & Ottehr

Oystehr v1.29 - September 18, 2025

Zambda Functions can now be assigned a Role to grant them permissions to access Oystehr services. Previously, accessing Oystehr services from a Zambda function either required using a caller's token, or using an M2M Client inside the Zambda Function. By specifying a Role, when your Zambda is invoked, you get an access token handed to you with the permissions of the Role.

When you request a token for an M2M Client, this token is now cached for one hour. This means that if you request a token for the same client multiple times within an hour, you will receive the same token. This reduces the number of tokens created and improves performance when using M2M Clients in high-throughput scenarios. This is a meaningful cost savings as it cuts down on the number of M2M Client tokens you need to pay for.
You can now specify a FHIR Profile for an M2M Client when creating it. We had previously introduced the ability to update the FHIR Profile of an M2M Client, but now you can set it at creation time as well.