Knit API Documentation

Managed Signing API (Merchants)

The Managed Signing API provides merchant endpoints for creating and managing wallets with secure signing capabilities. These endpoints are used by merchants integrating managed signing via API keys.

Base URL

{{baseUrl}}/api/v1/managed-signing

Authentication

• Header: X-API-KEY: <api-key>
• IP Whitelist: Requests must originate from a whitelisted IP.
• Forwarded IP Header: x-forwarded-for should contain the client IP.

Conventions

• All IDs returned are local DB UUIDs (not Knit Core IDs).
• You must use local IDs in requests (path params and body filters like walletId).
• businessId is included in responses; Knit Core IDs and userId are never returned.
• All request bodies use camelCase.
• All response keys are camelCase.

Supported Networks

Production Networks

• ETHEREUM_MAINNET
• MATIC_MAINNET
• BSC_MAINNET
• BASE_MAINNET

Testnet Networks (Sandbox/Dev only)

• MATIC_AMOY - Polygon Amoy testnet (commonly used for CPN testing)

Available Endpoints

Wallets

• POST /wallets - Create a managed signing wallet
• GET /wallets - List all managed signing wallets
• GET /wallets/{walletId} - Get a specific wallet

Policies

• POST /policies - Create a policy
• PATCH /policies/{policyId} - Update a policy
• GET /policies - List all policies
• GET /policies/{policyId} - Get a specific policy

Signing Requests

• POST /requests - Create a signing request
• POST /requests/{requestId}/approve - Approve a signing request
• GET /requests/{requestId} - Get a signing request
• GET /requests - List signing requests

Audit

• GET /audit - List audit events

Common Errors

Notes

• All IDs used in requests and responses are local DB UUIDs.
• Knit Core identifiers are stored internally and are not exposed.
• If you need to filter requests by wallet or policy, always use the local IDs returned by this API.