Getting Started with the Klau API

Welcome to the Klau Developer Platform. This guide will help you understand the core concepts of integrating with Klau, whether you are building internal tools for a single hauler or a multi-tenant platform for many.

1. Authentication

Klau uses **API Keys** for authentication. All API requests must include your key in the `Authorization` header.

Authorization: Bearer kl_live_your_api_key_here

Key Types

  • Direct Keys: Issued to a specific hauler (Company). These keys automatically scope all requests to that hauler's data.
  • Vendor Keys: Issued to platform integrators. These keys can access multiple haulers, but require an explicit Klau-Tenant-Id header.

2. Multi-Tenancy (For Vendors)

If you are a platform integrator, act on behalf of a hauler by passing their unique ID in the headers.

Authorization: Bearer kl_live_vendor_key
Klau-Tenant-Id: company_cuid_123

3. Core API Concepts

Idempotency

Use the Idempotency-Key header to safely retry requests without creating duplicate data.

Rate Limiting

We apply tiered limits per-developer, per-tenant, and per-endpoint to ensure platform stability.

Response Attribution

Every response includes metrics that help you showcase value (e.g., minutes saved, yard returns avoided). We encourage displaying "Optimized by Klau" in your product.