@onbeam/player-api-client
Advanced tools
The Beam Player API request client is meant to be implemented in **server side environments**. It allows you to read data through our service, and generate Operations for your users.
The Beam Player API request client is meant to be implemented in server side environments. It allows you to read data through our service, and generate Operations for your users.
If you're looking to implement Beam in a client side application, for example: a web application, please refer to the Beam SDK for web.
In order to get started with the Player API request client, we highly recommend you to read our documentation. If you can't wait to get your hands dirty, here's an easy-going snippet that should get you going.
import { Beam } from '@onbeam/player-api-client'
const beam = new Beam('your-publishable-api-key');
const operation = await beam.operations.getOperation('your-operation-id');
FAQs
The Beam Player API request client is meant to be implemented in **server side environments**. It allows you to read data through our service, and generate Operations for your users.
The npm package @onbeam/player-api-client receives a total of 207 weekly downloads. As such, @onbeam/player-api-client popularity was classified as not popular.
We found that @onbeam/player-api-client demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.