Skip to main content
KeyPort is organized around two surfaces: a public validation API your application calls at runtime, and a developer dashboard where you manage everything.
When you are ready to test the public API itself, use the live playground on Validate or License Lookup.

​
Domains

DomainPurpose
app.keyport.sbsDeveloper dashboard
api.keyport.sbsPublic validation API
customer.keyport.sbsCustomer portal
docs.keyport.sbsDocumentation
status.keyport.sbsStatus page

​
Validation flow

When your application validates a license, this is what happens:
1

Your app sends a request

Your application calls POST https://api.keyport.sbs/api/v1/validate with the product API key as a bearer token and the license key in the request body.
2

KeyPort authenticates the product

The API verifies the product API key and identifies which product and organization the request belongs to.
3

KeyPort evaluates the license

KeyPort runs plan-aware usage counting, business-state checks, license checks, and IP policy evaluation against the request.
4

KeyPort returns a structured result

The API returns a JSON response with valid, status, and related fields. Your application enforces access based on the result.

​
Dashboard workflows

Use the dashboard at app.keyport.sbs to manage all of the objects your validation flow depends on:
  • Create and manage organizations and products
  • Issue, revoke, and inspect licenses
  • Rotate product API keys
  • Configure IP settings, versions, and custom response templates
  • Manage team members with custom roles
  • Set up billing and webhook endpoints

​
Key sections

Quick Start

Get a working validation call running in about five minutes.

Core Concepts

Understand the objects and relationships that make up KeyPort.

Validate API

Full reference for POST /api/v1/validate.

Webhooks

Receive signed license lifecycle events in your own systems.