onelifevibe

OneLifeVibe Platform

One integration for 9 worlds.

Approved clients reach every OneLifeVibe website through one credential, one versioned REST API and signed webhooks in both directions. Keys are scoped per world, every call is rate-limited and counted, and the event log is the same one the webhooks deliver, so polling and push never disagree.

9 worlds 36 invocable tools HMAC-signed webhooks OpenAPI 3.1 Approval-gated

Read the developer documentation OpenAPI document API discovery

Get a platform client

Applying takes a minute. The operator reviews every client before its keys work; you keep console access while you wait.

Bot check

Checking your browser…

Sign in to the console

Client

—

—

0API calls today

0events delivered today

0daily event allowance

Quick start

  1. Create an API key on the API keys tab. Copy it: it is shown once.
  2. Use it as Authorization: Bearer … against https://onelifevibe.com/api/platform/v1.
  3. Add a webhook endpoint so changes reach you without polling.
curl -s https://onelifevibe.com/api/platform/v1/worlds \
  -H "Authorization: Bearer $OLV_KEY"

Full parameter reference, error codes and webhook verification code: developer documentation.

Create a key

Scopes

Start with read-only. tools:invoke lets the key change data inside a world.

Keys

NameScopesWorldsLast used

Add an endpoint

Every delivery carries webhook-signature, webhook-timestamp and webhook-id. Verify with the snippet in the documentation; consumers should dedupe on the event id.

Endpoints

URLStateHealth

Last 30 days

DayCallsEvents deliveredBytes in / out

Recent deliveries

StatusEventAttemptsHTTPError

Recent network events

TypeWorldWhen

Subscription

StatusPlan—Mode

Payments are handled by Stripe. A paid plan only takes effect while Stripe reports the subscription as active, so a failed payment falls back to Community limits rather than leaving an unbilled overrun.