portal_not_found

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "Portal not found.",
    "status": 404,
    "title": "Not Found",
    "type": "/errors/unkey/data/portal_not_found"
  }
}

​

Likely causes

• The slug or ID is wrong.
• You addressed the portal by an app or keyspace from another workspace.
• Your root key doesn’t have permission to read the portal. On portal.createSession, it needs create_portal_session. The message is the same either way.

​

How to fix

1. Check the slug or ID in the dashboard’s portal settings.
2. If you address the portal by app or keyspace, use one from this workspace.
3. For portal.createSession, make sure the root key has the create_portal_session permission on the portal.

​

Related errors

• err:unkey:data:portal_already_exists: a portal collides on create or update.
• err:unkey:authentication:portal_session_not_found: a session token, not the portal, is invalid.
• err:unkey:authorization:forbidden: the portal exists but is disabled or can’t serve sessions.