Dots Api

Dots focuses specifically on the payout side of payments — disbursing money from a platform to its users, sellers, or contractors. For agents managing payouts: create a Dots user (with KYC via Dots-hosted flow), that user links their preferred payout method (bank account, PayPal, Venmo, crypto), and the platform initiates payouts via the API. Dots handles the payout routing complexity (ACH, PayPal API, Venmo API, check printing) behind a single API. Strong fit for marketplace agents, creator economy platforms, and gig economy apps. Confidence is docs-derived.

REST API at api.dots.dev/v2. Resources: users, payouts, flows, transactions, apps. POST /users creates a Dots user ({firstName, lastName, email, phoneNumber}). POST /flows creates an onboarding flow (KYC, payout account linking) — returns a flow_id and URL to redirect the user to. POST /payouts sends funds to a user ({userId, amount, platform: 'bank'|'paypal'|'venmo'|'ach'}). GET /users/{id}/transactions lists all transactions for a user. GET /apps/{id}/balance returns the platform's available balance. POST /payouts/batch initiates multiple payouts. Response: JSON.

API key auth: client_id + api_key — passed as HTTP Basic credentials (client_id as username, api_key as password). Keys from Dots Console → Settings → API Keys. Separate sandbox and production keys. HTTPS enforced. No OAuth2. Onboarding flows use Dots-hosted KYC UI (user redirected to Dots, returns to platform with KYC complete). Webhook signatures for payout status events.

Standard HTTP status codes with JSON error bodies. 401 for invalid credentials, 422 for validation failures (user not KYC'd, insufficient balance). Payout status: initiated → processing → completed/failed. Failed payouts: reason returned in transaction object. Balance insufficient: 422 with balance_insufficient error. Dots service uptime at status.dots.dev. Sandbox mirrors production payout flows. Webhook delivery for real-time payout status updates.

docs.dots.dev provides REST API reference, quickstart guides (user creation, onboarding flow, payout), and webhook integration guide. Getting started: create Dots account (free trial), generate sandbox credentials, onboard a test user, initiate a test payout in under 30 minutes. No official SDK beyond direct HTTP; clients available for Node.js and Python in community. Support via Dots Slack community and support email.