Skip to main content
POST
Go (SDK)

Authorizations

Authorization
string
header
required

Unkey uses bearer tokens for authentication. Public integrations use root keys, while the dashboard proxy uses short-lived JWTs. To authenticate, include the token in the Authorization header of each request:

Root keys have specific permissions attached to them, controlling what operations they can perform. Legacy permissions use tuple strings like api.*.create_key; resource permissions use Unkey Resource Names plus actions, like unkey:v1:ws_123:keyspaces/*#create_key. Security best practices:

  • Keep root keys secure and never expose them in client-side code
  • Use different root keys for different environments
  • Rotate keys periodically, especially after team member departures
  • Create keys with minimal necessary permissions following least privilege principle
  • Monitor key usage with audit logs.

Body

application/json
slug
string
required

URL-safe handle for this portal, unique within your workspace. Lowercase alphanumerics and single hyphens, 3-64 characters, not starting or ending with a hyphen.

Required string length: 3 - 64
Pattern: ^[a-z0-9]([a-z0-9-]*[a-z0-9])?$
Example:

"acme-portal"

displayName
string
required

Human-readable name your end users see in the portal header and page titles. Unlike slug it is not part of any URL, so it can be changed freely.

Required string length: 1 - 64
Pattern: ^\S(.*\S)?$
Example:

"Acme"

keyspaceId
string
required

The id of the keyspace this portal serves keys for. Must belong to your workspace.

A portal serves exactly one resource, so keyspaceId and appId are mutually exclusive.

Required string length: 1 - 255
Pattern: ^[a-zA-Z0-9_-]+$
Example:

"ks_1234abcd"

appId
string

The id of the app this portal serves keys for. Must belong to your workspace.

A portal serves exactly one resource, so appId and keyspaceId are mutually exclusive.

Required string length: 1 - 255
Pattern: ^[a-zA-Z0-9_-]+$
Example:

"app_1234abcd"

enabled
boolean
default:true

Whether sessions can be minted for this portal immediately. Defaults to true; send false to create it dormant and enable it later.

Example:

true

logoUrl
string<uri>

Absolute https:// URL of the logo shown in the portal header.

Loaded by your end users' browsers, so the host you name receives their IP and user agent on every page view.

Required string length: 1 - 500
Pattern: ^https://
Example:

"https://cdn.example.com/logo.svg"

primaryColor
string

Six-digit hex colour used for primary actions and accents in the portal.

Pattern: ^#[0-9a-fA-F]{6}$
Example:

"#6366f1"

Response

Portal created successfully.

meta
object
required

Metadata object included in every API response. This provides context about the request and is essential for debugging, audit trails, and support inquiries. The requestId is particularly important when troubleshooting issues with the Unkey support team.

data
object
required