You need a root key with the permissions listed on this page. Create one in the dashboard under Settings > Root Keys, and pass it as
Authorization: Bearer <root key>. See Permission reference for every permission.POST /v2/portal.getPortal. The portal management commands are unreleased and may change without notice.
Usage
Flags
string
Portal id or slug.
string
Find the portal for this keyspace.
string
Find the portal for this app.
Shared flags
Everyunkey api command takes these. See CLI output and shared flags.
string
Root key used for the request. Falls back to
UNKEY_ROOT_KEY, then to the key stored by unkey auth login.string
default:"https://api.unkey.com"
Base URL of the API. Falls back to
UNKEY_API_BASE_URL. You don’t normally need to set it.string
default:"~/.unkey/config.toml"
Path of the config file written by
unkey auth login. Falls back to UNKEY_CONFIG.string
Output format. Falls back to
UNKEY_OUTPUT. json prints the full response. Any other value prints the request ID and data.string
Send this JSON as the whole request body instead of using the command’s flags. You can’t combine it with them.
Required permissions
portal.*.read_portal or portal.<portalId>.read_portal. Without it you get a 404, so a 404 means either there’s no such portal or you don’t have permission. See Root key permissions.
Examples
By handle
By the keyspace it serves
Raw body