Knit API Overview

Knit provides a unified API for managing on-chain treasury tooling—collecting payments, provisioning reusable wallets, distributing payouts, and keeping web2 systems in sync through reliable webhooks. Every endpoint lives under {{baseUrl}}/api/v1 and is guarded by the same dual-authentication middleware, so you can start with legacy API keys and migrate to OAuth 2.0 client credentials when you are ready.

Platform Pillars

• Collections: one-time deposit addresses for invoice-like flows. Each request creates a single-use address and forwards status events via webhooks.
• API Wallets: reusable, labelled wallets (per chain) for recurring deposits or customer-specific ledgers. Wallet transactions are queryable with filters for status, token, range, and pagination.
• Business API Services Wallet (API Account): holds funds that power payout requests. Transfer crypto from the core business wallet into this account before initiating disbursements.
• Payouts: programmatic, on-chain withdrawals. Knit validates balances, enforces IP whitelists, and pushes final statuses via PAYOUT_SUCCESSFUL events.
• Webhooks & Dashboards: every critical state change is persisted and can be replayed; business stakeholders can also review activity via dashboard APIs.

Quick Start

1. Create or onboard a business in the Knit dashboard.
2. Configure authentication — generate an API key or create an OAuth client (see the Authentication page).
3. Whitelist your server IPs in the dashboard so authenticated requests are allowed through to the API.
4. Set the webhook URL + secret under Business → Developer → Webhooks to receive collection/payout events.
5. Call the service endpoints documented in the navigation (Collections, Wallets, Payouts, Webhooks, Networks, etc.).

Request/Response Conventions

• JSON only. The request/response examples in this documentation match exactly what the API expects and returns.
• Responses always include the shared envelope (success, statusCode, message, data, and optional pagination metadata) so you can rely on a consistent structure across endpoints.
• Where relevant we show both X-API-KEY and Authorization: Bearer header options so you can choose the auth strategy that fits your rollout plan.

Need more detail on a particular workflow? Jump straight into the section that matches your use case or reach out via the support channel linked from the dashboard.