Glossary
World keys
World keys are the short names OneLifeVibe gives its network websites, and a key's world list records which of them that key allows.
Updated November 13, 2026
- Also called
world,world list
At OneLifeVibe
- POST /api/platform/v1/subscriptions with a worlds entry that is not "*" or one of the world keys (wuuuh, aisenatus, helpbless, taskfamily, sixonseven, introworth, soclasica, storychoose, astrodios).
Related terms
What it means
A world key is one of the short names OneLifeVibe uses for a website in its network, such as wuuuh or soclasica. You will also see world on its own, and world list for the set of worlds attached to a key.
A world list is an allowlist. It records which of the network sites a key covers, so one key can be tied to the sites you name rather than to all of them. That keeps a key built for one site from reaching another, and it makes the reach of a key readable without opening anything else.
World keys are identifiers, not display names. They go into API calls as short lowercase strings, so copy them exactly as written.
How it works
Where a request takes a worlds entry, the value is either the wildcard "*" or a world key. The wildcard stands for the whole set; a world key names one site.
Treat it as two checks. The value has to be a real world key, and that world has to appear in the key's world list. A key whose list holds soclasica can name soclasica there. Naming a different world is a different grant, and the list is what decides it.
The world list belongs to the credential, not to the call. It is set with the key, and every request that names a world is read against it.
How OneLifeVibe uses it
Developers meet world keys at POST /api/platform/v1/subscriptions. The request carries a worlds entry, and that entry has to be "*" or one of the nine world keys: wuuuh, aisenatus, helpbless, taskfamily, sixonseven, introworth, soclasica, storychoose, astrodios.
If you send a display name, a URL or a short name that is not on that list, you have not sent a world key. So take the value from the list, spell it as written, and use "*" when the subscription should cover the network instead of a single site.
The subscription's own name does not matter here. What counts is the value in worlds and whether the calling key's world list allows it.
Common mistakes
Sending a site's display name or URL instead of its world key. The names are short and fixed, and the key is soclasica, not whatever the site is called on the page.
Treating "*" as a tenth world key. It is the wildcard accepted in the worlds entry, not a name you add to a list next to the others.
Fixing the spelling and stopping there. A correct world key only gets you halfway; the key's world list decides what that key allows, so check both.
Questions
Where do world keys go in a request?
In the worlds entry of POST /api/platform/v1/subscriptions. That entry takes a world key or the wildcard "*". A display name or a URL does not count as a world key.
What does a key's world list control?
It decides which worlds that key allows. A world key can be spelled correctly and still sit outside the key's list. Set the list to the sites the key actually works with.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.