Glossary
world_not_allowed
world_not_allowed is the 403 error returned when an API key's world list does not cover the website you are calling.
Updated November 12, 2026
At OneLifeVibe
- Platform scopes: worlds:read, tools:read, tools:invoke, events:read, events:subscribe and data:read. A key's world list ("*" or keys such as ["wuuuh","soclasica"]) decides where; both must allow the call, or the answer is 403 insufficient_scope or world_not_allowed.
Related terms
What it means
A 403 means the server understood the request and refused it. world_not_allowed is the specific 403 OneLifeVibe returns when the key's world list does not cover the website being called.
It is a placement error, not an identity error. The request reached the platform, and authorization failed at the world level. The scopes can be correct and the call will still return this code if the site sits outside the key's list.
How it works
Two checks run on a call, and both have to pass. The platform scopes say what the key can do: worlds:read, tools:read, tools:invoke, events:read, events:subscribe, data:read. The world list says where it can do it: either "*" or a set of world keys such as ["wuuuh","soclasica"].
When either check fails, the response is 403. A scope failure comes back as insufficient_scope. A world failure comes back as world_not_allowed. Both share the same status, so read the code instead of treating every 403 the same way.
The split keeps what and where separate. A scope name on its own does not grant access to a world, and a world entry on its own does not grant an action.
How OneLifeVibe uses it
Every OneLifeVibe API key carries a world list. With "*", the where check passes for any website. With ["wuuuh","soclasica"], calls to those world keys pass and calls to any other website return world_not_allowed.
The scope check still applies. A key carrying tools:invoke and a world list of ["wuuuh"] passes both gates for a tool call on wuuuh. The same call on soclasica returns world_not_allowed. Drop tools:invoke and the call on wuuuh returns insufficient_scope.
Common mistakes
The usual mistake is reading 403 as a bad key and rotating credentials. That does not help. The key authenticated, and a replacement will hit the same wall if its world list also leaves out the site.
Another mix-up is swapping the codes. insufficient_scope points at the scope set. world_not_allowed points at the world list. Changing scopes will not fix a world problem, and changing the world list will not fix a scope problem.
Check both gates before you change anything. A key with "*" in its world list can still fail with insufficient_scope. A key carrying all six platform scopes can still fail with world_not_allowed.
Questions
What is the difference between world_not_allowed and insufficient_scope?
Both are 403 responses. world_not_allowed means the key's world list does not cover the website being called. insufficient_scope means the scope check failed.
How do I fix a world_not_allowed error?
Use a key whose world list covers the website you are calling, or add the website to the list. "*" covers every website, while ["wuuuh","soclasica"] covers only those two.
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.