API

Versioned endpoints. Predictable JSON. Sanctum auth.

Manage API keys and read usage over JSON with personal access tokens—same v1 surface your console uses under the hood.

Base URL

https://ironstack.highoctanebrands.com/api/v1

Authentication

  • Bearer Sanctum personal access token for user context (CLIs, internal services, automation).
  • isk_live_* Org-scoped keys created in the console—hashed at rest, revocable, with configurable scopes.
Examples

GET /api/v1/me

Current user + active organization (Sanctum).

GET /api/v1/api-keys

List organization API keys (no secrets returned).

GET /api/v1/usage

Read metering records for the active organization.

Designed for client SDKs and codegen

Consistent envelopes reduce integration drag: your partners get clear errors, stable fields, and room to evolve without breaking older clients.

OpenAPI publishing and SDK generation are natural extensions of this foundation—ship the control plane first, then widen the surface area as your ecosystem grows.
Developer experience
JSON-first, predictable HTTP semantics, and route names that read well in docs and incident channels.
Operational safety
Keys are revocable, attributable, and auditable—so security teams can reason about blast radius.

Photography Dimitris Chapsoulas, Compare Fibre, Abu Saeid, Domaintechnik Ledl.net on Unsplash.