LogoMkSaaS Docs
LogoMkSaaS Docs
HomepageTikomni Quick StartAuthenticationu1 APIu2 APIBillingError EnvelopeAPI ReferenceDeploy Runbook
X (Twitter)

Authentication

API key authentication and request headers

Header

All gateway requests must include:

Authorization: Bearer <platform_api_key>

If missing or invalid, the platform returns 401 UNAUTHORIZED.

Request ID

You can optionally pass a stable request id for idempotent tracing:

x-tikomni-request-id: <your_request_id>

If omitted, the gateway generates one automatically.

API Key Scope

Current release allows API key calls to:

  • u1 routes
  • u2 routes

API Key Verification Endpoint

curl -X POST "https://api.tikomni.com/api/test/apikey" \
  -H "Content-Type: application/json" \
  -d '{"key":"<platform_api_key>"}'

Table of Contents

Header
Request ID
API Key Scope
API Key Verification Endpoint