SDK Overview
Use the SDK path when you want to add Beav3r approval control to your own product instead of starting from a specific integration.
What this path gives you
The SDK path is the generic Beav3r setup:
- create a project
- generate an API key
- define the policy shape for test
- pair a signer device
- send a test approval through the platform
Step 1: Create a project and API key
Start in the hosted Beav3r app.
You need:
- a project for your application or environment
- an API key that the SDK or runtime will use
See:
Step 2: Set a simple policy for test
For first setup, keep the policy scope simple.
The goal is not to model every edge case. The goal is to confirm that a risky action can be sent into Beav3r and blocked until a signer decides.
See:
Step 3: Pair a signer
Pair the Beav3r mobile signer so approvals can be reviewed from a real device.
For MVP:
- one signer device is active at a time
- you can revoke and replace the active device later
See:
Step 4: Send a test approval
Run a simple approval-triggering action from your app, test harness, or integration surface.
Expected result:
- the request reaches Beav3r
- the paired signer receives a notification
- approve or reject resolves back to the caller
What success looks like
Your SDK setup is working when:
- the API key is accepted
- the project policy allows the test flow to be evaluated
- the signer receives notifications
- the final decision comes back to the requesting system