Beam Accounts SDK
The recommended way to interact with the Beam API is by using one of our official SDKs. All of the provided SDKs are meant to be used server side, as it's crucial to not expose any of the api keys we provided publicly.
At the time of writing, the SDKs we're shipping are all automatically generated after every service release. We're currently using OpenAPI generator (opens in a new tab) and OpenAPI Typescript Codegen (opens in a new tab).
It's of the utmost importance that your API key never gets exposed. If your API key is / has been at risk of being exposed, please contact email@example.com. Alternatively: re-create your API keys yourself using the provided regenerate-key, the old ones will automatically be invalidated.
In order to get started, we currently provide the following SDKs. Note that if there's no available SDK available for your preferred language, there's always the possibility of directly connecting to the RESTful endpoints by passing your API key in the
If you're interested in how we generate the SDK, have a look at the Github repository (opens in a new tab). If you don't want to use our provided SDKs, it might still be of inspiration.
If you are interested in more granular changelogs for SDK releases, have a look at our Github releases (opens in a new tab)
Every deployment of the Beam API leads to a new patch version of the SDK being released. With every release, the release description in the Github release contains a description that explains the difference between the previous and new version based on the REStful endpoints.
In the future, we hope to automatically assess major, minor and patch versions, but we currently rely on patch incrementals only.
Beam OpenAPI specification empowers you with a broad set of developer tooling, starting with Postman collections and generating your own SDK. It also serves as the basis for our generated release changelogs and SDKs.